Hi Thomas,
Thank you for the heads up! We just added the internationalization support in 4.2.0:
– wrapped all text in __(“…”, “shortpixel”) thus the text domain is ‘shortpixel’
– added some test/incomplete .po/.mo files in the subfolder /lang.
If I understand correctly from the documentation, the next things that we need to do is to change the domain to ‘shortpixel-image-optimiser’ and to specify this in the plugin header as “Text Domain: shortpixel-image-optimiser” also adding a “Domain Path: /lang” line.
Could you please tell me if this is correct?
Thanks!
Alex.
Thread Starter
Tomas
(@mobby2561)
Yes absolutely.
After these changes can anyone suggest new translations.
If you ask the translators to contribute at translate.ww.wp.xz.cn and the contributors will want to translate the entire plugin, You can make a request to give them PTE(Project Translation Editor) rights to translate (not just make suggestions) your plugin.
When the language reaches 95% translated strings it will automatically generate language pack. On this page you can see all of the generated language packs for your plugin. This is handy thanks probably to WordPress 3.9+ which allows to update/install language packs, same page as plugin/theme updates appear and you as a developed don’t need to include translations in /name_of_your_plugin/lang folder.
Since version 4.6 WordPress prefers community translations instead of /name_of_your_plugin/lang folder.
If you’ll have some problem with generation of translations you should take a look at WordPress Slack’s channel named #meta-language-packs or if you’ll need some more technical info use the #meta-i18n channel.
Regards,
Tomas
Hi Tomas,
Thanks a lot for the further clarifications. I made the changes and after testing the plugin I will release a new version.
Best regards,
Alex.
