Re: non-utf8 po files breaking the build

[Keld Jørn Simonsen <keld dkuug dk>]

On Tue, Nov 26, 2002 at 01:58:42AM +0100, Christian Rose wrote:
> tis 2002-11-26 klockan 01.24 skrev Keld Jørn Simonsen:
> > > > > > I don't think you should do it, it would create some burdens for 
> > > > > > translators that are unnecesary.
> > > > > 
> > > > > Can you explain this in more detail? What specific burdens, and why do
> > > > > you think they are unnecessary? Vague comments without rationales don't
> > > > > help.
> > > > 
> > > > I have discussed this earlier.
> > > 
> > > Ok, I thought you were to bring up some new input on this issue.
> > 
> > there were new things in it.
> 
> Sorry, I didn't notice. What new input did you bring? What potential
> drawbacks hasn't been mentioned and discussed already?

The problem with tools.
> 
> > > > One ting is people doing corrections and not observing that the encoding
> > > > is UTF-8, and just correcting it in iso-8859-1. I have seen a number
> > > > of examples of this in kde, these errors are cumbersome to solve,
> > > > and these problems are unnecessary, and a waiste of my time.
> > > 
> > > These errors will probably always exist, irregardless of what encodings
> > > we use. There will always be mistakes. But the tools can check for those
> > > errors and they already do (msgfmt certainly does).
> > 
> > And then people need the new tools. gettext 0.11 is not
> > in standard distributions yet.
> 
> I don't know what you count as "standard distributions", but for your
> information I can tell you that Red Hat has had gettext 0.11 in at least
> two major releases, and also Mandrake and SuSE has it.

Only in the latest distributions.

Best regards
keld