Date: Wed, 14 Jan 2004 18:27:50 -0200
From: Euler Taveira de Oliveira <euler@ufgnet.ufg.br>
To: "Dave Page" <dpage@vale-housing.co.uk>
Cc: peter_e@gmx.net, borz_off@cs.msu.su, pgsql-www@postgresql.org
Subject: Re: A briefing is needed...
Message-Id: <20040114182750.4d706865.euler@ufgnet.ufg.br>
In-Reply-To: <03AF4E498C591348A42FC93DEA9661B872045D@mail.vale-housing.co.uk>
References: <03AF4E498C591348A42FC93DEA9661B872045D@mail.vale-housing.co.uk>
Reply-To: euler@ufgnet.ufg.br
Organization: UFGNet
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

> > The internationalization system I see in CVS right now=20
> > doesn't look very well thought out.  Separating the text from=20
> > the context where it will appear will not make the site very=20
> > maintainable.=20=20
>=20
That's what I think. When it is a simple website it is OK, but when it's a =
Portal, IMHO it's a pain in the neck.

> Hmm, we use gettext on the pgAdmin site (and keep the text in the
> context in which it will appear) and I find the site a real pain to
> maintain. The old site (although only in English) was much easier to
> maintain - it kept content in a db and used a single php script to
> display all pages bar a few odd scripts.
>=20
Yep, I know the gettext extension for php is not a real solution for transl=
ation. But I think it's the right thing. I'm working in an extension of get=
text to made the support of internationalization to markup languages (XML, =
HTML, SGML, etc). Maybe it improve the gettext scenario.

Another idea:
1) use index.html.en, index.html.de, index.html.pt_BR for static pages;
2) grad browser language and use it in the dinamic pages;

PS> I just code the Weekly News extension for the website and I will post i=
t tomorrow for comments. It's based in the actual design.

Regards,

--=20
Euler Taveira de Oliveira
euler (at) ufgnet.ufg.br
Desenvolvedor Web e Administrador de Sistemas
UFGNet - Universidade Federal de Goi=E1s