Complete.Org: Mailing Lists: Archives: freeciv-i18n: November 2004:
[freeciv-i18n] Re: [FreeCiv-Cvs] jdorje: Convert files from ISO-8859-1,

[freeciv-i18n] Re: [FreeCiv-Cvs] jdorje: Convert files from ISO-8859-1,

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: keld@xxxxxxxx
Cc: chrisk@xxxxxxxxx, freeciv-i18n@xxxxxxxxxxx
Subject: [freeciv-i18n] Re: [FreeCiv-Cvs] jdorje: Convert files from ISO-8859-1, ISO-
From: "Duarte Loreto" <happyguy_pt@xxxxxxxxxxx>
Date: Sun, 21 Nov 2004 16:56:56 +0000

Hello, Keld

Either you missed the point or I didn't understand what you are saying...

Chris needs to translate po files in UTF-8. His system is not UTF-8 enabled. 
So, he needs to convert UTF-8 files to ISO-8859-1 for translation update and 
then reconvert them to UTF-8 to store in CVS. This is easyer than updating 
his system to be fully UTF-8 compliant.

If a project decides that all translations should be done in UTF-8, as it 
seems to be the trend, I don't see why having people with "old configured" 
machines should stall the progress of using a better encoding. And for a 
packaging prespective, it's easyer (and faster) to create build scripts that 
take as granted all po files will use the same enconding (UTF-8) than using 
iconv over each translated file.

Anyway, maybe I'm talking about a completly diferent thing from what you are 
talking just because I didn't understand you :)

All be happy!

Duarte "HappyGuy" Loreto

"Don't worry, be happy!"

>From: Keld Jørn Simonsen <keld@xxxxxxxx>
>To: Duarte Loreto <happyguy_pt@xxxxxxxxxxx>
>CC: chrisk@xxxxxxxxx, freeciv-i18n@xxxxxxxxxxx
>Subject: [freeciv-i18n] Re: [FreeCiv-Cvs] jdorje: Convert files from 
>ISO-8859-1, ISO-
>Date: Sun, 21 Nov 2004 16:20:55 +0100
>On Sun, Nov 21, 2004 at 02:23:24PM +0000, Duarte Loreto wrote:
> > Hello!
> >
> > This may not be of much help but... When I was translating po files for 
> > GNOME 2.0 release, I had to do them in UTF-8. What I did was to convert
> > UTF-8 to ISO-8859-1, translate or update and then reconvert to UTF-8. It
> > worked quite well. I used these scripts
> >
> > It required you to have an env flag set up.
> > export ENCODING_TO=ISO-8859-1
>It defeats the very role of cvs to store documents in a different format
>  from the source, that is the preferred format the the maintainer of the
>file has for doing modifications to the file. So please do not force
>translators to use utf-8, if they prefer standardized character encoding
>like iso-8859-1.
>best regards

Don't just search. Find. Check out the new MSN Search!

[Prev in Thread] Current Thread [Next in Thread]