> Hi Nazir, > > As promised, here are details on the next steps and tasks needed on > localization. Many thanks to Van, Kim, Ofer, and Beth for helping me > pull this info together-- and thanks for your reminder to send this > out! > I've also cc-ed the mifos-developer list since I think some of this info may be pertinent to others. Once we get all the localization code checked-in, we will be developing documentation on the mifos.org site around how to localize Mifos. In the meantime, I hope this will give you the information you need:
> * We took the properties files that Lassaad provided us and > changed the file names from .properties to *_fr.properties. You can > find the revised files here: > http://confluence.mifos.org:9090/download/attachments/3014666/enda-pro > ps.zip?version=1 > > * All properties files have been moved into the following > directory: org\mifos\config\localizedResources. The _fr properties > files should be checked in later today (potentially Monday if > something goes wrong). > > * We built a test version of Mifos in French. You can view it > here: > http://build.mifos.org:8086/mifos-fr > Username: mifos > Password: testmifos > > * We also have another localized version of Mifos running-- using > "fake" translated text. All text strings proceed with @@@ and end > with ^^^. This will show you that most of the properties files can be > translated. If you see something in English on the French site, look > on the site below to see if the text is showing up with @@@ ^^^ -- if > it is, it just means the French properties files are missing the > translation: > http://build.mifos.org:8086/mifos-is > Username: mifos > Password: testmifos > > > What you need to do: > * There are several places where English is displaying-- in most > cases because the properties are missing-- either b/c they were missed > the first time or because new features have been added to the site > since the properties files were translated. You need to identify all > the places where properties are missing-- give that list to Lassaad > for translation. > * We recommend a couple of tools that can help you with this task. > Take a look at: https://prbeditor.dev.java.net/ or I18NEdit > (http://www.cantamen.de/i18nedit.php?lang=en). This is listed the > under "Localization/Translation Tools and Approaches" on the mifos.org > site: > http://mifos.org/developers/wiki/MifosLocalization > * Once you've translated these properties and added them into the > _fr properties files, you should check in those changes. > > There are likely a handful of places where English text might be > hardcoded. We're working through those issues on our side-- but if > you come across an example of this-- please log a bug in the issue > tracker. > > Final Step: > > * The last thing that needs to be done to get the app to use the > fr locale is to create a custom configuration file in the decompressed > war file named: > > org\mifos\config\resources\applicationConfiguration.custom.properties > > If you want to see the French localization right away, you should add > the following content: > > Localization.LanguageCode = FR > Localization.CountryCode = FR > Once we've added Tunisia to the database, we suggest you use the TN country code: Localization.LanguageCode = FR Localization.CountryCode = TN > * I believe that this file can be anywhere on the class path > (although we haven't tried that from our side). > > * The file has to be created after the war has been built - > otherwise build will fail. (We will find a better way for doing this > post 1.1) > > Phew! Sorry for the long email. If you have any questions-- Van or > Kim (on the mifos-developer list) should be able to help you out. > > Thanks Nazir, > > Emily. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
