Klaus.Bartz at coi.de
Fri Apr 20 10:08:40 CEST 2007
you are right that the ISO3 code "por" for Brazilian
Portuguese is wrong because ISO3 is a country code.
Some weeks ago we have discussed how to handle Farsi.
We have decided to change to properties files and remove
We know, that we cannot address all spoken languages
with it, but there is no simple system todo it.
In the moment I have written a simple converter from our
HTML format to the properties format.
I am thinking about the new HTML format for properties. But
then we can only compile with VM version 1.5 (also known as 5.0)
One problem will be, that the properties format do not use
utf-8 else an own - bad readable - format for chars other
than ASCII. In the moment I am faiting with a simple
program which shows the properties files contents in
utf-16 and allows to edit the contents. I do it only for
MS Windows because I have no time to play with locale
switching of the keybord mapping on UNIX derivates.
This "editor" will be really simple e.g. with problems at
resizing. If someone do not love it, he/she can expand it
or write directly the properties files.
Therefore we will get
and no flags.
> -----Original Message-----
> From: izpack-users-bounces at lists.berlios.de
> [mailto:izpack-users-bounces at lists.berlios.de] On Behalf Of
> Ricardo Trindade
> Sent: Thursday, April 19, 2007 11:49 AM
> To: izpack-users at lists.berlios.de
> Cc: Tiago Brazão
> Subject: [izpack-users] Locales
> We've been using izpack for a while, and it works well.
> As a request for enhancement, I wanted to point out that
> there are a
> few errors in your translation scheme.
> For example, what you call a Portuguese translation, is
> actually a
> Brazilian translation. So perhaps it would make sense to rename your
> translations and resources to something respecting the locale :
> For Portugal :
> For Brazil :
> izpack-users mailing list
> izpack-users at lists.berlios.de
More information about the izpack-users