Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: euler@ufgnet.ufg.br, Justin Clift <justin@postgresql.org>
Subject: Re: [HACKERS] Changes to Contributor List
Date: Tue, 11 Nov 2003 10:11:35 -0800
User-Agent: KMail/1.4.3
Cc: alvherre@dcc.uchile.cl, xzilla@users.sourceforge.net,
	dpage@vale-housing.co.uk, pgsql-www@postgresql.org,
	grzm@myrealbox.com, webmaster@letzplay.de
References: <03AF4E498C591348A42FC93DEA9661B84C5D2B@mail.vale-housing.co.uk>
	<3FB1020A.3010004@postgresql.org>
	<20031111142830.6cc4a5e2.euler@ufgnet.ufg.br>
In-Reply-To: <20031111142830.6cc4a5e2.euler@ufgnet.ufg.br>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200311111011.35840.josh@agliodbs.com>

Euler, Alvaro,

> All the translators do know HTML. And I wanna propose to use the
> internationalization like Debian Project, eg, using Languages capabilities
> of Apache Webserver. Basically we have:

I manage PostgreSQL's team of translators for advocacy/website stuff, and I 
can tell you that they don't all, or even most, know enough HTML to handle 
even a simple table.  

> If the text could be automatically generated from a DocBook source, then
> the translation could be handled by the same mechanism the KDE guys use:
> a Docbook -> PO -> Docbook tool.  Translator don't have to know HTML;
> they just use KBabel or gtranslator, etc.  That's the theory at least ...

This is a fine idea if we can come up with a tool which is available on all 
major platforms: win95, winNT/2k, Mac OS X, Linux and BSD.   Otherwise, a web 
form will be a *lot* easier to manage.

Personally, even when I'm editing something which someone else has marked up I 
find editing wiki-markup to be *much* easier.   In HTML, it's far two easy to 
accidentially paste over a closing tag or a bracket and screw up the whole 
page.  This will be even more the case if you want to adopt the stricter 
XHTML.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco