Re: UTF8 encoding for all .po files
- From: Gregory Leblanc <gleblanc linuxweasel com>
- To: Trond Eivind Glomsrød <teg redhat com>
- Cc: GNOME i18n list <gnome-i18n gnome org>
- Subject: Re: UTF8 encoding for all .po files
- Date: 30 Apr 2002 16:16:29 -0700
On Tue, 2002-04-30 at 14:55, Trond Eivind Glomsrød wrote:
> Carlos Perelló Marín <carlos@gnome-db.org> writes:
> ----
>
>
> > El mié, 24-04-2002 a las 15:34, Keld Jørn Simonsen escribió:
> > > On Wed, Apr 24, 2002 at 12:13:51PM +0200, Carlos Perelló Marín wrote:
> > > > Hi I'm thinking on recode all GNOME2's .po files into UTF8 before the
> > > > release. Some teams are not working on translations and then those
> > > > translations could cause problems on old systems (as old as a Debian
> > > > Potato or RedHat 6.2).
> > > >
> > > > What do you think?
> > > >
> > > > Could I reencode all those files and commit them to cvs.gnome.org?
> > >
> > > I think it would create some problems. I have experienced
> > > quite a lot of problems with utf-8 files, because they
> > > are not adhered to. That is, many make modifications
> > > to utf-8 files in another charset, eg iso-8859-1.
> > > And then one has to remedy these errors. I have lost
> > > quite some hours on that account.
> > >
> > > It has been discussed before and the conclusion
> > > was also then to not do it.
> >
> > But we need it as UTF8 at release time...
> >
> > We can add a script at cvs.gnome.org to check for a valid .po file, if
> > the file is not well enconded the commit can fail.
>
> Shouldn't that be done anyway? Invalid po files are a big pain....
Yep, it should. There was some attempt at doing this in CVS, but the
regexp was broken and never matched any files. I think it's gone now,
but I'm not sure. Sopwith was the last one looking at this, IIRC.
Greg
--
Portland, Oregon, USA.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]