[jsword-devel] [JIRA] Commented: (JS-104) Migrate translations into as few files as possible and co-locate them

[DM Smith (JIRA)]

    [ http://www.crosswire.org/bugs/browse/JS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053#comment-14053 ] 

DM Smith commented on JS-104:
-----------------------------

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.

> Migrate translations into as few files as possible and co-locate them
> ---------------------------------------------------------------------
>
>                 Key: JS-104
>                 URL: http://www.crosswire.org/bugs/browse/JS-104
>             Project: JSword
>          Issue Type: Improvement
>          Components: o.c.jsword.util
>            Reporter: DM Smith
>            Assignee: DM Smith
>             Fix For: 1.6.1
>
>         Attachments: JS-104-1.patch.zip
>
>
> 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. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira