Description of problem:
The site translations are a mix of java old-school messages.properties and generated *Messages.properties.
As it stands, the editor strings are not available to the translators.
Version-Release number of selected component (if applicable):
The zanata-war/-model should be a multi-module project
Gwt generate the *Messages.properties files
Upload these to translate.zanata.org for translation
This will make activities such as:
- translation auto-update
- pseudo-translation testing
- supported locale query
and others more accessible.
Sean - I think I reported this one for you. Does this address the above?
I haven't tested this feature, but I'd say: more or less.
Zanata wasn't set up to be a multi-module project after all, but that's because we needed project-type 'properties' for the jsf localisation, and 'utf8properties' for the GWT editor.
Also, there's the problem Dean spotted with the zh_TW_Hant/zh_Hant_TW locale (bug 1063562), which does need fixing before we can actually include future zh-Hant translations in a future release of Zanata. It needn't block the 3.3 release though.
I think bug 1066203 will be a better solution for our GWT translations, but it requires a minor refactor to the GWT code, so I'd say it is outside this bug's scope.
Verified at aa31fd676205c4ad428e213cef2dd26030d63f56
Marking bug as RELEASE_PENDING (Fixed in Version commit is ancestor of origin/master).