[
http://mifosforge.jira.com/browse/MIFOS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66036#comment-66036
]
Michael Vorburger commented on MIFOS-4851:
------------------------------------------
Reminder: As MIFOS-3844 said, [Java generally expects these files to be
latin1-encoded|http://download.oracle.com/javase/6/docs/api/java/util/Properties.html].
Choice of two solutions really probably:
a) As MIFOS-3844 already pondered, run native2ascii (or a pure-Java equivalent;
native2ascii is a native tool) "at a suitable point" (which may not be obvious;
having just invested a lot of time in Hot Workspace 2.0, I'm strongly opposed
to any "build steps" required after a git clone - workspaces must work
out-of-the-box!). May be translatewiki could do this when...ever those files
get created (I'm unclear about the exact process used).
b) Use XML Java Properties files! I like that, as with XML encoding header
this is clear & clean.
[Spring's ReloadableResourceBundleMessageSource supports XML properties files
|http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/context/support/ReloadableResourceBundleMessageSource.html]
([SPR-925|https://jira.springsource.org/browse/SPR-925]). How can we get
translatewiki to provide Java XML properties files instead? (BTW: It would be
trivial to write a Java CLI tool to transform *.properties to *.xml using only
java.util.Properties)
> Translations in UTF-8 encoded Java *.properties files are problematic
> ---------------------------------------------------------------------
>
> Key: MIFOS-4851
> URL: http://mifosforge.jira.com/browse/MIFOS-4851
> Project: mifos
> Issue Type: Bug
> Reporter: Michael Vorburger
> Assignee: Adam Monsen
> Priority: Critical
>
> Mifos currently "uses UTF-8-encoded Java properties-style resource bundles".
> This seems to have been intentionally introduced in MIFOS-3844. I'd argue
> that this is wrong / confusing / problematic, and is the secondary cause of
> MIFOS-4789 (who's primary cause is the wrong Content-Type / charset, which is
> a separate problem that I suggest be addressed with my patch in MIFOS-4789).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
