Why is translation done pr. theme and not global

[rabol]

Hi

I don't understand why translation is done pr. theme as far as I can see it 'just' adds more work to the theme designers, furthermore there is a lot of 'duplicate' entries e.g. strings like 'My account' and 'E-Mail' shows up several times.

If the translation is done in a global scope all themes could benefit and duplicate entries could be prevented - Only very theme specific entries needed to be added on installation, furthermore: Using a global array just adds additional ’overhead' to the web server and global vars is potential security issues.

I have done 3 different translation systems (DB and site wide) and none of them added extra overheat to the application due to the fact that all strings was 'loaded' using a query (or cached queries).

Br
Steen

[Peter Wilson]

Hi rabol,

As for duplicate phrases throughout PrestaShop, this is indeed an issue and we have plans to change this for a future (post-v1.0) version.

Please note, however, that the 'added work' for importing a translation to a theme is very minimal. Simply go to Back Office >> Tools >> Translations >> Copy section, then copy the same language from one theme to another.