Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.7
-
Component/s: o.c.jsword.util
-
Labels:None
Description
Translating Common, JSword and BibleDesktop is difficult as translations files are segregated by Java package. As such there has been little traction in translating Bible Desktop into other languages.
Translations should be co-located in a single location. The translator should not have to dig to find the files to translate. By having them co-located, the translator can quickly find what has and has not been translated.
Translations should be able to be edited in their native script. Java property files are in ASCII and are not conducive to editing.
Translators should be able to edit the files easily outside of Eclipse using a simple translation editor such as poedit.
The conversion of these files to Java property files should be automated.
Recommendation: Explore GNU's "Translation Project." Specifically, gettext "po" files.
Attachments
Issue Links
- is depended on by
-
-
- Resolved
-
Activity
This patch solves an incomplete prior update. There may still be more problems. Please report them if you find them.
With this the user facing messages should all be wrapped with Msg.gettext so that they can be extracted to GNU style pot and po files.
Still need to handle buttons and other widgets as that is using a different mechanism.
Need to unwind the Alias.OK, et al, so that they can properly be represented in pot and po files.
Once that is all done, then the properties need to be slurped into pot and po files, one per project, property files generated from them and Msg.gettext to operate against that consolidated store.
Major merging of Msg into BibleDesktopMsg.
Need to merge config into it.
Restored missing SiteEditorFactory.properties and renamed it SiteEditor.plugin.
Move most resources to src/main/resources.
Support needs to be added to common first.