...
Page Properties | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
|
Star
Background
At the moment the Swing GUI translations are provided as .properties and .csv files in the project’s bundle/ subfolder. These files are also hosted on Transifex platform for the community contribution. Thanks to the GitHub-Transifex integration, new strings are automatically uploaded to Transifex and 100% translations are pushed back to GitHub (via PullRequest).
...
Option 1: | Option 2: | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Separated Translation files between “gui” and “ui” | Same translation files | ||||||||||||
Pros and cons | possibility to adopt different and more reliable translations formats double maintainance until “gui” will be still included in the release packages more resources on Transifex | Same translations files for both “gui” and “ui” Only one set of resources on Transifex Transifex can handle automatically only one repository (Pull Requests), so updating both components will require manual work or more advanced release scripts | ||||||||||||
Estimated cost |
|
|
Action items
- To define the localization pattern for the “ui” component