still the official way for contributing translations to Plone 5?
Situation: at least the German translations are far away from being complete...many forms are a bad mixture of English and German.
So what is the best way to contribute translations?
Wasn't there a web-based tool for managing translations and in particular checking a language for completeness?
Tools like Transiflex?
In general: at the time when Plone 5.1 should be released all "major" languages must be supported completely. It's ok having this mixture in 5.0 release. However as a professional enterprise-level CMS the most important languages must be support out-of-the-box and completely. How can we manage and measure the translation quality in Plone?
Yes, the information on that page seems correct to me.
There is a plone translation project on Transifex, but as far as I know it is not up to date. So committing to plone.app.locales is still the best way.
To measure the amount of translations in the plone domain:
$ src/plone.app.locales/plone/app/locales/locales $ i18ndude list -p plone
Result on current master branch:
Messages: 2695
Tier 1:
100% - English (en)
93% - French (fr)
92% - Italian (it)
78% - German (de)
89% - Spanish (es)
98% - Dutch (nl)
72% - Chinese (China) (zh-cn)
95% - Chinese (Taiwan) (zh-tw)
79% - Japanese (ja)
10% - Korean (ko)
93% - Portuguese (Brazil) (pt-br)
77% - Russian (ru)
57% - Polish (pl)
52% - Turkish (tr)
13% - Thai (th)
38% - Arabic (ar)
I don't know who first came up with the tier 1/2/3 and if much thought has gone into that. Presumably these are the most used languages in the world, with some arbitrariness added, like Dutch.
Yes, update those empty msgstrs.
And check any messages that are marked with 'fuzzy': the English message has changed since the last translation, so maybe the translation needs to be updated too. If the translation is fine, remove the fuzzy marker.
And note that next to plone.po there are other po files, and there is the locales-addons directory in the same package, which may have interesting domains.
Direct commits are fine. If you want someone else to check it first, you can create a pull request. Probably best to directly @mention a native speaker then.