You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll add that the current way using regex might not be the easiest/safest.
I would try to simply boot the module and get all the translations needed with the prestashop built-in translation system that must be aware of all needed translations.
Plus i think it's @matks that told me about some kind of already built-in translation system in prestashop capable of generating needed translation keys for a module/theme (or something like that).
So now that we have a translation module working, i think it's important that the next step is to get informations about what exists and how we can use it for our needs.
prestashop can translate native modules using one system A
prestashop can translate 3rd party modules (such as this one) using one system B
And system A and system B are not the same (dont asky me why roll_eyes).
Also, we have enabled a system C that uses Symfony translator to be able to translate Symfony modules, and legacy modules (= modules not using Symfony) can use it too ! This one is fully documented here: https://devdocs.prestashop.com/1.7/modules/creation/module-translation/new-system/ and is backward compatible: if a module was using system B and is switching to system C, translations already created for system B can be used by system C.
However this system C is available since PS 1.7.6
The text was updated successfully, but these errors were encountered:
Originally posted by @zalexki in #1 (comment)
I'll add that the current way using regex might not be the easiest/safest.
I would try to simply boot the module and get all the translations needed with the prestashop built-in translation system that must be aware of all needed translations.
Plus i think it's @matks that told me about some kind of already built-in translation system in prestashop capable of generating needed translation keys for a module/theme (or something like that).
So now that we have a translation module working, i think it's important that the next step is to get informations about what exists and how we can use it for our needs.
Answer from @matks
So, I know that:
And system A and system B are not the same (dont asky me why roll_eyes).
Also, we have enabled a system C that uses Symfony translator to be able to translate Symfony modules, and legacy modules (= modules not using Symfony) can use it too ! This one is fully documented here: https://devdocs.prestashop.com/1.7/modules/creation/module-translation/new-system/ and is backward compatible: if a module was using system B and is switching to system C, translations already created for system B can be used by system C.
However this system C is available since PS 1.7.6
The text was updated successfully, but these errors were encountered: