Loading...

XML

Word

Printable

Urgency:
Critical
ChangeLog Description:

Hide
Refactoring Localization of translate5
* Localized strings can now be extracted from the source-code and developers do not have to provide translations anymore.
* New file-format ".zxliff" to seperate new from old sytematic
* CLI-commands to extract, update, formate, export & import localizations

Show
Refactoring Localization of translate5 * Localized strings can now be extracted from the source-code and developers do not have to provide translations anymore. * New file-format ".zxliff" to seperate new from old sytematic * CLI-commands to extract, update, formate, export & import localizations
Checklist:

Empty

show more show less

PROBLEM
Localization in translate5 has no defined processesso far.
Currently:

developers are expected to provide all translations for their features (if not given in the issue)

SOLUTION

Developers should provide only the english (source)-translations
English is the fallback-language for other languages but german (which falls back to the mostly german sources)
on translate.translate5 a workflow shall be established to continously localize the App

From product owner side it must be ensured:
that missing translations do NOT stop role out of features
that a missing translation falls back to developer EN
that developer EN is still "translated" to real EN by Marion
that we have a continous translation flow, meaning new translations go out to translators once a month.
that this process causes very little work for the dev-team. From my point of view all translators should work in translate.translate5.net instance for this reason. marcmittag will ask Phillip/Apostroph if we can do that.
Of course then als FR and IT TM of existing translations must exist in translate.translate5.net