Contributing to PrestaShop is not only about the code, it’s also about taking part to the PrestaShop translation project! Read this report to see how the translations of the software evolved in June.
1.7.1 made way for 1.7.2
As we’ve recently released the new version 184.108.40.206, the translations folder for the version 1.7.1 has been removed.
This version brings some new content; you can read more about it here.
Domain change in 1.7.2 (read this for your themes)
As a theme creator, the 220.127.116.11 version contains modifications that could impact the theme you’re selling.
If you are using the Classic strings (and attached translations) for your own theme, we’ve made some changes in 1.7.2 that you should report on your theme if you still want to benefit from the PrestaShop translations.
- Translation domain “Shop.Theme” is now “Shop.Theme.Global”.
- Harmonization of domains for customer form: see domains to update.
- Correction of “Brands list” to “Brand list”: see domains to update.
And as a reminder, you can read this article to know how theme translation works in 1.7 (and 18.104.22.168 brings many improvements on this side).
Each time we add a new version, there can be some propagation issues. Old translations seem to come back and some more recent work can be lost. C’est la vie !
When a string is identical between versions, here is how it works:
- If translated in 1.6 folder, it will be shared with 1.7.2 folder.
- If not translated in 1.6, it won’t be shared with 1.7.2 folder. But if translated in 1.7.1, the 1.7.1 translation will be propagated to 1.7.2.
- If a string is updated in 1.7.1 but NOT in 1.6 folder, it is still the 1.6 version which will be shared with new folders (1.7.2 in the present case).
Because of this propagation process, sometimes you will see old translations coming back. If you are editing existing translations, please make sure they are also corrected in version 1.6 too.
To check whether a string is available in 1.6, you need to display all strings from the project, make a search for the string, then hover on the file name to see if it comes from version 1.6 or 1.7. Then you can edit the 1.6 version too:
We recently welcomed the 4,000th member to the PrestaShop translation project. As of today, we’re already more than 4,100 members: WOW.
Thank you for believing in open source and for helping fellow merchants in having a software translated in their language!
Now let’s get back to our Crowdin project, and the full report of its activity in June:
A few stats
- 40 members were active on the project this month.
- A total of 26,340 words have been translated and 12,237 validated.
- All this in 30 different languages.
Thank you for your involvement!
A lot of you are working every day on Crowdin to have PrestaShop available in many languages, and we can’t thank you enough for your dedication! Here are the most active translators and proofreaders for June 2017.
Top 10 translators in June:
- | Jesús Ruiz (jruiz) | Spanish | 14,046
- | Yosef Esses Cohen (ppesses) | Spanish, Mexico | 8,857
- | SeongHyeon Cho (jaymz9634) | Korean | 3,024
- | Morten Borg (mortenborg) | Danish | 2,800
- | Yuji Sugimoto (bm-sugi) | Japanese | 2,007
- | Olta Çantası (soyalp.ms.ms) | Turkish | 1,463
- | Anouar Talidi (Anouar_Talidi) | Arabic | 1,100
- | Enzo Ferrara (ferribbotte) | Italian | 934
- | jinjit | Hebrew | 932
- | Nikos Krontiris (nikoskrontirist) | Greek | 929
Top 10 proofreaders in June:
- | Jesús Ruiz (jruiz) | Spanish | 13,989
- | Yuji Sugimoto (bm-sugi) | Japanese | 3,643
- | Morten Borg (mortenborg) | Danish | 2,800
- | SeongHyeon Cho (jaymz9634) | Korean | 1,188
- | lolypop000 | Slovenian | 915
- | AmirRzd | Persian | 704
- | Enzo Ferrara (ferribbotte) | Italian | 646
- | Gabriel Tenita (ggedamed)| Romanian | 618
- | Stanislav Yordanov (StanProg) | Bulgarian | 269
- | Patrik Lindblom (extendus) | Swedish | 230
Congrats, and welcome to our new top contributors!
Remember, you can see who’s been contributing to our translation project thanks to the Translators page.
Fully translated languages
At the end of July 2017, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 15 languages:
| Bulgarian | English | French | French, Canada | | French, Canada | German | Greek | Italian | | Norwegian | Russian | Slovak | Slovene | | Spanish | Swedish | Turkish |
For its part, PrestaShop 1.7.2 is already fully available in 10 languages!
| Croatian | English | French | French, Canada | | German | Greek | Italian | Norwegian | | Russian | Slovak | Slovene | Spanish | | Swedish | Turkish | Ukrainian |
Languages with the best evolution
In comparison with May 2017, the following languages had the best progress thanks to the translation community:
- Spanish, MX (+6% to reach 49% translated in 1.7)
- Korean (+2% to reach 23% translated in 1.6)
- Romanian (+1% to reach 100% translated in 1.6)
Thanks to all the contributors!
Of course, this is highlighting the languages that made some progress with new translations; but it doesn’t mean that the languages that aren’t mentioned here aren’t active. Indeed, some editing and rewriting could be going on, but the percentage of translation wouldn’t be modified (since it’s working on strings that are already translated). So let’s not forget about the work of these proofreaders! Thank you too!
Languages that need (more) proofreaders
A translated string will not be available in PrestaShop as long as it is not validated. For this reason, it’s important we should keep a good level of validated strings vs. translated strings, to make sure everyone benefits from the latest translations!
The list has quite evolved over the last few months, meaning that a lot of proofreading took place. It’s great!
At the end of June 2017, some languages would still benefit from some proofreading:
- Arabic (64% translated vs 18% validated in 1.7).
- Galician (65% vs 46% in 1.7).
- Romanian (94% vs 75% in 1.7).
Again, these figures are mostly for 1.7, but 1.6 needs some proofreading too :)
If you wish to help to proofread what has been translated, please contact me on Crowdin with the language you’d like to proofread. We need your help!
If you haven’t joined us on Crowdin yet, it’s never too late!
If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let us know: we’ll include a word about it in the next monthly report.
Do you have a question, a remark? Don’t hesitate to leave a comment. See you next month!