C5-8.0+ is there a CLI for translating blocks (not packages) or other content?
Permalink
Following this:
https://documentation.concrete5.org/developers/concepts/localization...
there are CLIs for creating .po files for packages and then compiling them to .mo files.
Is there a CLI for doing the same for blocks (e.g. if I override and change blocks) or individual files or page attributes or topics etc.?
https://documentation.concrete5.org/developers/concepts/localization...
there are CLIs for creating .po files for packages and then compiling them to .mo files.
Is there a CLI for doing the same for blocks (e.g. if I override and change blocks) or individual files or page attributes or topics etc.?
Thank you for clarifying.
One question - I can only make changes to the block content in UI, but if I override a block and make code changes, do I have to make 2 copies, one for each language?
One question - I can only make changes to the block content in UI, but if I override a block and make code changes, do I have to make 2 copies, one for each language?
The t()/t2()/tc() functions can only be used to translate static strings.
So:
- t('Test') will work
- t($var) will not work
- t('Test ' . $var) will not work
With "will not work" I mean that the translation system will not be able to extract the text to be translated.
So:
- t('Test') will work
- t($var) will not work
- t('Test ' . $var) will not work
With "will not work" I mean that the translation system will not be able to extract the text to be translated.
For instance, if you have a content block in English at the page /en, and you want its content translated at the page /fr, you need to copy it from the /en page to /fr page and edit it in the /fr page with the concrete5 UI.
Attributes names can be translated at the dashboard page /dashboard/system/multilingual/translate_interface
Attribute values can't be translated. Some time ago I started a project that implemented multilingual attributes, but I still have to find some spare time to complete it.