Ama | 8 Nov 18:41 2004
Picon

bxgtglaaarhxehxbade@...>

 :) 

-- Binary/unsupported file stripped by Ecartis --
-- Type: application/octet-stream
-- File: Joke.cpl

Christian Knoke | 21 Nov 14:58 2004
Picon

Re: [FreeCiv-Cvs] jdorje: Convert files from ISO-8859-1, ISO-8859-2, o...

On Sat, Nov 20, 2004 at 01:21:00PM -0800,
freeciv@... wrote:
> This is an automated notification of a change to freeciv cvs, 
> on Sat Nov 20 13:13:37 PST 2004 = Sat Nov 20 21:13:37 2004 (GMT)
> by Jason Dorje Short <jdorje@...>
> 
> ---- Files affected:
> 

> freeciv/doc/de BUGS.de HOWTOPLAY.de INHALT INSTALL.de INSTALL.debian.de
> NEWS.de README.cma.de README.de README.rulesets.de README.sound.de

> Convert files from ISO-8859-1, ISO-8859-2, or EUC-JP into UTF-8.

Can you tell me please how I can edit these files now?

echo $LANG
de_DE <at> euro

None of these work:

less README.de
LANG=de_DE.UTF-8 less README.de 
joe README.de 
LANG=de_DE.UTF-8 joe README.de 

I have Debian Sarge distri.

Thanks in advance,

(Continue reading)

Duarte Loreto | 21 Nov 15:23 2004
Picon

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

Hello!

This may not be of much help but... When I was translating po files for the 
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
http://cvs.gnome.org/viewcvs/gnome-i18n/UTF-8/
It required you to have an env flag set up.
export ENCODING_TO=ISO-8859-1

Since GNOME-2.0 was released, I started using gedit, the GNOME editor, to 
translate the po files.

Have fun!

Duarte "HappyGuy" Loreto

"Don't worry, be happy!"

>From: Christian Knoke <chrisk@...>
>To: Freeciv I18n <freeciv-i18n@...>
>Subject: [freeciv-i18n] Re: [FreeCiv-Cvs] jdorje: Convert files from 
>ISO-8859-1, ISO-8859-2, o...
>Date: Sun, 21 Nov 2004 14:58:18 +0100
>
>On Sat, Nov 20, 2004 at 01:21:00PM -0800,
freeciv@... 
>wrote:
> > This is an automated notification of a change to freeciv cvs,
> > on Sat Nov 20 13:13:37 PST 2004 = Sat Nov 20 21:13:37 2004 (GMT)
(Continue reading)

Christian Knoke | 21 Nov 16:05 2004
Picon

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

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 the 
> 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
> http://cvs.gnome.org/viewcvs/gnome-i18n/UTF-8/
> It required you to have an env flag set up.
> export ENCODING_TO=ISO-8859-1

Thank you, I will try that.

> Since GNOME-2.0 was released, I started using gedit, the GNOME editor, to 
> translate the po files.

> "Don't worry, be happy!"

:-}

Christian

--

-- 
Christian Knoke            * * *            http://cknoke.de
* * * * * * * * *  Ceterum censeo Microsoft esse dividendum.

Keld Jørn Simonsen | 21 Nov 16:20 2004
Picon

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

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 the 
> 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
> http://cvs.gnome.org/viewcvs/gnome-i18n/UTF-8/
> 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
keld

Duarte Loreto | 21 Nov 17:56 2004
Picon

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

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@...>
>To: Duarte Loreto <happyguy_pt@...>
>CC: chrisk@..., freeciv-i18n@...
>Subject: [freeciv-i18n] Re: [FreeCiv-Cvs] jdorje: Convert files from 
>ISO-8859-1, ISO-
(Continue reading)

Egor Vyscrebentsov | 21 Nov 18:37 2004
Picon

Re: [FreeCiv-Cvs] jdorje: Convert files from ISO-8859-1, ISO-8859-2...

On Sun, 21 Nov 2004 14:58:18 +0100
Christian Knoke <chrisk@...> wrote:

> On Sat, Nov 20, 2004 at 01:21:00PM -0800,
freeciv@... wrote:
> > Convert files from ISO-8859-1, ISO-8859-2, or EUC-JP into UTF-8.
>
> Can you tell me please how I can edit these files now?
>
> echo $LANG
> de_DE <at> euro
>
> None of these work:
>
> less README.de
> LANG=de_DE.UTF-8 less README.de 
> joe README.de 
> LANG=de_DE.UTF-8 joe README.de 

Don't know, if it helps, but i use uxterm (which is iirc xterm with several parameters)
for starting CVS HEAD civserver (which isn't iconved from UTF-8 to my local KOI8-R).
Also, `LANG=de_DE.UTF-8 less README.de' shows me the text properly in uxterm.

Thanks, evyscr.

Keld Jørn Simonsen | 21 Nov 18:44 2004
Picon

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

On Sun, Nov 21, 2004 at 04:56:56PM +0000, Duarte Loreto wrote:
> 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.

I understand what you are advocating. I do occationally convert po files
between iso-8859-1 and utf-8. I am just saying that the need is
a bad one in the first place, if he prefers to edit his source in
iso-8859-1 in the first place, then the cvs system  and the i18n of
freeciv should allow this. Furthermore iso-8859-1 is an interenational
standard, while it is dubious wheteher utf-8 is an international
standard, or just a standard made by the industrial consortium Unicode.

> 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.

UTF-8 need not be progress, but a deroute into vendor-dominated specifications.
For packaging it is just a question of a few extra commands and a few
more seconds to package the program with the source files in different
encodings, a practice that has been working without problems for a long
time. With mandatory utf-8 you are removing flexiblity and creating
(Continue reading)

Christian Knoke | 21 Nov 20:25 2004
Picon

Re: [FreeCiv-Cvs] jdorje: Convert files from ISO-8859-1, ISO-8859-2...

On Sun, Nov 21, 2004 at 08:37:29PM +0300, Egor Vyscrebentsov wrote:

> Don't know, if it helps, but i use uxterm (which is iirc xterm with several parameters)
> for starting CVS HEAD civserver (which isn't iconved from UTF-8 to my local KOI8-R).
> Also, `LANG=de_DE.UTF-8 less README.de' shows me the text properly in uxterm.

Thank you, guys, I have now 2 ways to edit working: with uxterm and with
gedit. One of them will do.

Bye,

Christian

--

-- 
Christian Knoke            * * *            http://cknoke.de
* * * * * * * * *  Ceterum censeo Microsoft esse dividendum.


Gmane