[
http://mifosforge.jira.com/browse/MIFOS-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen updated MIFOS-3844:
-------------------------------
Description:
We recently [began accepting translations from
translatewiki.net|http://thread.gmane.org/gmane.comp.finance.mifos.devel/9801/focus=9806].
They commit Java .properties-style resource bundles directly to our source
code repository, but they are in UTF-8 format.
[Java generally expects these files to be
latin1-encoded|http://download.oracle.com/javase/6/docs/api/java/util/Properties.html].
But Spring gives us a way out! Implement
http://forum.springsource.org/showthread.php?p=169307 . Confirm this worked by
changing the Mifos locale and observing localized messages.
If that doesn't work, another idea is to modify the Mifos build so native2ascii
is run on these files before they become part of the Mifos .war file.
was:
We recently [began accepting translations from
translatewiki.net|http://thread.gmane.org/gmane.comp.finance.mifos.devel/9801/focus=9806].
They commit Java .properties-style resource bundles directly to our source
code repository, but they are in UTF-8 format.
[Java generally expects these files to be
latin1-encoded|http://download.oracle.com/javase/6/docs/api/java/util/Properties.html].
But Spring gives us a way out. Implement
http://forum.springsource.org/showthread.php?p=169307
Another idea is to modify the Mifos build so native2ascii is run on these files
before they become part of the Mifos .war file.
Summary: allow use of UTF-8-encoded Java properties-style resource
bundles (was: during the build, run native2ascii on UTF-8 .properties files)
> allow use of UTF-8-encoded Java properties-style resource bundles
> -----------------------------------------------------------------
>
> Key: MIFOS-3844
> URL: http://mifosforge.jira.com/browse/MIFOS-3844
> Project: mifos
> Issue Type: Task
> Reporter: Adam Monsen
> Priority: Major
>
> We recently [began accepting translations from
> translatewiki.net|http://thread.gmane.org/gmane.comp.finance.mifos.devel/9801/focus=9806].
> They commit Java .properties-style resource bundles directly to our source
> code repository, but they are in UTF-8 format.
> [Java generally expects these files to be
> latin1-encoded|http://download.oracle.com/javase/6/docs/api/java/util/Properties.html].
> But Spring gives us a way out! Implement
> http://forum.springsource.org/showthread.php?p=169307 . Confirm this worked
> by changing the Mifos locale and observing localized messages.
> If that doesn't work, another idea is to modify the Mifos build so
> native2ascii is run on these files before they become part of the Mifos .war
> file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security
easier or more difficult to achieve? Read this whitepaper to separate the
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues