Better way to set new textpack related data?

makss · 2017-11-09 21:14:15

philwareham wrote #307744:

skin_step_failure => Theme {skin} failed at {step} stage....

…then isn’t {step} hardcoded in English – such as ‘import’ and ‘edit’? That would not be desirable.

possible variant:

gTxt(
    skin_step_failure',
    array(
        '{skin}' => $this->skin,
        '{step}' => gTxt('import'),
    )
);

makss · 2017-11-09 21:55:53

Bloke wrote #307753:

The only unknown is what to do with custom/plugin strings. Installing/removing files in the filesystem is messy so maybe we need to rethink this a bit?

Which existing plugins support multiple languages? I would like to test one idea on real plugins.

Bloke · 2017-11-09 22:39:22

makss wrote #307755:

Which existing plugins support multiple languages? I would like to test one idea on real plugins.

com_connect does (on the public side at least).

For both admin side and public side, ied_plugin_composer is a good candidate (though it needs some visual tweaking for 4.7.0).

NicolasGraph · 2017-11-10 08:10:58

makss wrote #307754:

possible variant:

gTxt(...

You’ve been faster than me.
It seems clever, mainly where ‘nested’ textpack items already exist.

NicolasGraph · 2017-12-02 10:30:24

makss wrote #307754:

possible variant:

gTxt(...

How about that?

Textpattern CMS

Textpattern CMS support forum

#11 2017-11-09 21:14:15

Re: Better way to set new textpack related data?

philwareham wrote #307744:

#12 2017-11-09 21:55:53

Re: Better way to set new textpack related data?

Bloke wrote #307753:

#13 2017-11-09 22:39:22

Re: Better way to set new textpack related data?

makss wrote #307755:

#14 2017-11-10 08:10:58

Re: Better way to set new textpack related data?

makss wrote #307754:

#15 2017-12-02 10:30:24

Re: Better way to set new textpack related data?

makss wrote #307754:

Board footer