Re: non-utf8 po files breaking the build

[Yanko Kaneti <yaneti declera com>]

On Wed, 2002-11-27 at 17:02, Keld Jørn Simonsen wrote:
> On Wed, Nov 27, 2002 at 12:58:18PM +0100, Kjartan Maraas wrote:
> > ons, 2002-11-27 kl. 11:41 skrev Keld Jørn Simonsen:
> > > On Mon, Nov 25, 2002 at 01:15:48AM +0100, Christian Rose wrote:
> > > > mån 2002-11-25 klockan 00.02 skrev Keld Jørn Simonsen:
> > > > 
> > > > The decision to use UTF-8 as the mandatory encoding for all GNOME 2.x po
> > > > files has been made. Please accept that.
> > > 
> > > I really dont understand your rhetorics here. We have decided not to
> > > force UTF-8 on our translators a number of times, and then you again and
> > > again claim the opposite. Please accept that we live in a world that
> > > has multiple charsets, and please do not make it harder for translators
> > > to contribute to Gnome.
> > > 
> > 
> > We are not forcing UTF-8 on anyone. The only thing that has been decided
> > is that all po files should be in UTF-8 format *in* *CVS* so that we
> > have less problems for the people trying to make tarballs once a week
> > and also for the people who are trying to keep the tree buildable at all
> > times.
> 
> Well, we have decided to keep the po files in the CVS in all charsets, two times.
> We have never decided to only have it in UTF-8.

The result of all discussion on this topic until recently has been
indecision rather than any concrete result. Someone was saying: "Lets
make UTF-8 mandatory"  you or somebody else were chiming in: "Lets fix
the tools". And this has happened more than once without anybody doing
anything.

For good or worse now all gnome 2.2 translations in cvs are UTF-8 and I
am keeping an eye on them to stay this way. Would be nice if someone
makes this more automatic.


Regards
Yanko