Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: euler@ufgnet.ufg.br, pgsql-www@postgresql.org
Subject: Re: Considerations on a Multi-Lingual Site
Date: Tue, 11 Nov 2003 13:45:44 -0800
User-Agent: KMail/1.4.3
References: <7758E5AE-1470-11D8-9A55-0005029FC1A7@myrealbox.com>
	<3FB1316C.5050603@postgresql.org>
	<20031111191105.7bfe0747.euler@ufgnet.ufg.br>
In-Reply-To: <20031111191105.7bfe0747.euler@ufgnet.ufg.br>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200311111345.44799.josh@agliodbs.com>

Euler,

> From last one, we could see how to deal the docs and how to proceed. As=
=20
Alvaro said, the guys are using SGML docs and extract a PO file. I think th=
is=20
is not too hard to handle .po files. There are some GUIs that handle this=
=20
easily. (Kbabel, ktranslator, gtranslator, etc).

I'm not clear on how the KDE solution would work in terms of keeping websit=
e=20
translations updated.   It seems designed for monumental rip-through of a=
=20
stable version of a project. It also requires KDE-based tools, which leaves=
=20
out a *lot* of people.

The Debian solution seems much more thourough.   If we could find some GUI=
=20
editor so that translation vols would not need to learn WML or HTML, this=
=20
would be perfect.  Hmmm, and we'd need to figure out how to do this if not=
=20
all translation vols are web CVS committers or if they're running on=20
platforms where good CVS tools are not available (i.e. Win95).


--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco