[
https://issues.apache.org/jira/browse/PIVOT-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961406#comment-13961406
]
Mark Chambers commented on PIVOT-940:
-------------------------------------
Thanks for you reply Sandro:]
I think the localisation json files should be in the classpath for good
practice, but definitely allow them to be loaded externally.
It just that I think the localisation files should be associated with the bxml
files not with the Java Class Files. So when you load the bxmlserialiser you
can also specify a localisation json file. Since the people in Charge of the
GUI and the language are normally the same group... and definitely not the same
people that code up the classes...
So you would have in a jar for example:
/gui/*.bxml
/gui/*.json
/apache/pivot/*.class
All in the same jar if needed.
Not:
/gui/*.bxml
/gui/SomeOfThe.json
/apache/pivot/*.class
/apache/pivot/Localisation.json
Is there a way to do this currently? (I may have missed a way to do it?)
> Localisation Using a Non Class Related File
> -------------------------------------------
>
> Key: PIVOT-940
> URL: https://issues.apache.org/jira/browse/PIVOT-940
> Project: Pivot
> Issue Type: Improvement
> Components: core-json, core-serialization, wtk
> Affects Versions: 2.0.3
> Environment: ALL
> Reporter: Mark Chambers
> Assignee: Sandro Martini
> Priority: Minor
> Labels: Localization
>
> Currently it seems that the resources in Pivot are done that same way as the
> JDK, so .json files are associated with the classes.
> Since anybody working in an International software industries has to deal
> with the problem of continualy having to translate applications languages, it
> seems strange to have to wrap up the languages with the Class Files.
> Ideally an external file, should be able to be specified, like the bxml
> file... That is sitting somewhere with the other resource files,
> configuration files etc...
> No reason to link it too the class, since 95% of class are not even GUI
> components, and the way Apache Pivot does it is has a single GUI class, so
> why bother linking it to the Class...And it is relevant to the bxml files not
> the classes...
> Also means that when you wrap it up in a Jar for deployment the language
> files can be sitting outside, so distributors and resellers, or open source
> community members etc. can make the application support their language
> themselves, just by copying,renaming and modifying the Language file...means
> we can obfuscate jars easier etc...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
