pidgin-i18n

[Gaim-i18n] [Fwd: Re: [Intltool] UTF-8 Conversion Warnings]

[Richard L. <rl...@wi...>]

I'm perfectly okay with ignoring the warnings, but is there any reason
we couldn't just convert the files? I'd rather not do it myself (because
I don't want to break something for the translators), but have the
respective translators do it when they next submit an update.

WARNING: ./po/my_MM.po is not in UTF-8 but iso-8859-1, converting...
WARNING: ./po/tr.po is not in UTF-8 but ISO-8859-9, converting...
WARNING: ./po/nb.po is not in UTF-8 but ISO-8859-1, converting...
WARNING: ./po/en_GB.po is not in UTF-8 but iso-8859-1, converting...
WARNING: ./po/it.po is not in UTF-8 but iso-8859-1, converting...
WARNING: ./po/pl.po is not in UTF-8 but ISO-8859-2, converting...

Richard

-------- Forwarded Message --------
> From: Rodney Dawes <do...@no...>
> To: Richard Laager <rl...@wi...>
> Cc: int...@li...
> Subject: Re: [Intltool] UTF-8 Conversion Warnings
> Date: Mon, 13 Feb 2006 14:32:51 -0500
> 
> On Mon, 2006-02-13 at 13:14 -0600, Richard Laager wrote:
> > On Mon, 2006-02-13 at 13:56 -0500, Rodney Dawes wrote:
> > > On Mon, 2006-02-13 at 11:37 -0600, Richard Laager wrote:
> > > > Gaim recently switched to using intltool. When we build, we get the
> > > > following warnings. The charset is marked in the .po file, and intltool
> > > > doesn't seem to report any problems doing the conversion, so why is it
> > > > necessary to warn?
> > > 
> > > Becuase your po file says it is UTF-8 but contains characters from other
> > > character sets. This means you should fix the po files to actually be in
> > > UTF-8 rather than just saying they are, but without converting them.
> > 
> > It doesn't say it's UTF-8. Here's an example of one that's being warned
> > about:
> 
> > "Content-Type: text/plain; charset=ISO-8859-2\n"
> 
> > It clearly says ISO-8859-2 and that's what intltool detects it as, given
> > the warning is:
> > WARNING: ./po/pl.po is not in UTF-8 but ISO-8859-2, converting...
> > 
> > Am I missing something?
> 
> Ah, sorry. OK. So, it's warning because it's not in UTF-8. And po files
> should be in UTF-8. Just convert them to UTF-8 or ignore the warning.
> The warning is to tell people that they should convert and join the new
> millenium. :)
> 
> -- dobey
> 
> 

Re: [Gaim-i18n] [Fwd: Re: [Intltool] UTF-8 Conversion Warnings]

[Ethan B. <ebl...@cs...>]

Richard Laager spake unto us the following wisdom:
> I'm perfectly okay with ignoring the warnings, but is there any reason
> we couldn't just convert the files? I'd rather not do it myself (because
> I don't want to break something for the translators), but have the
> respective translators do it when they next submit an update.

There is no reason that translators should not submit pofiles in the
character set they are most comfortable with.  The fact that intltool
is crying about it should be considered a bug.

Ethan

--=20
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764

Re: [Gaim-i18n] [Fwd: Re: [Intltool] UTF-8 Conversion Warnings]

[Richard L. <rl...@wi...>]

On Mon, 2006-02-13 at 15:15 -0500, Ethan Blanton wrote:
> Richard Laager spake unto us the following wisdom:
> > I'm perfectly okay with ignoring the warnings, but is there any reason
> > we couldn't just convert the files? I'd rather not do it myself (because
> > I don't want to break something for the translators), but have the
> > respective translators do it when they next submit an update.
> 
> There is no reason that translators should not submit pofiles in the
> character set they are most comfortable with.  The fact that intltool
> is crying about it should be considered a bug.

Sure. All I was saying is, if you're a translator for one of these files
and you're equally comfortable working with UTF-8, then perhaps you
could convert the file for the next update.

Anyway, I filed bug #331046 at http://bugzilla.gnome.org against
intltool. I just wanted to see if this list had any feedback before I
went ahead.

Richard

Re: [Gaim-i18n] [Fwd: Re: [Intltool] UTF-8 Conversion Warnings]

[Luke S. <lsc...@us...>]

On Mon, Feb 13, 2006 at 03:15:45PM -0500, Ethan Blanton wrote:
> Richard Laager spake unto us the following wisdom:
> > I'm perfectly okay with ignoring the warnings, but is there any reason
> > we couldn't just convert the files? I'd rather not do it myself (because
> > I don't want to break something for the translators), but have the
> > respective translators do it when they next submit an update.
> 
> There is no reason that translators should not submit pofiles in the
> character set they are most comfortable with.  The fact that intltool
> is crying about it should be considered a bug.
> 
> Ethan

I strongly agree with Ethan here.  No reason why they should have to
learn UTF-8 when we can automatically convert the encoding at compile
time.

luke

Re: [Gaim-i18n] [Fwd: Re: [Intltool] UTF-8 Conversion Warnings]

[<da...@gn...> )]

Hi guys,

=D0=88=D1=83=D1=87=D0=B5 =D1=83 21:51, Luke Schierer =D0=BD=D0=B0=D0=BF=D0=
=B8=D1=81=D0=B0:

> I strongly agree with Ethan here.  No reason why they should have to
> learn UTF-8 when we can automatically convert the encoding at compile
> time.

You actually can't (or not easily, anyway): intltool is reencoding
only into it's own cache so it can construct properly merged .desktop,
.xml, .schemas, .server and similar files which contain many
languages.  Encoding ends up in the MO file as well, and translation
needs to be re-encoded on every run of the program in that locale.

I've explained this in the bug as well.

Also, you can't serve all the PO files properly via web page (or,
it's harder at least), like the one on http://gaim.sf.net/i18n/, since
you commonly set only a single content-encoding.

Cheers,
Danilo

Re: [Gaim-i18n] [Fwd: Re: [Intltool] UTF-8 Conversion Warnings]

[Richard L. <rl...@wi...>]

On Tue, 2006-02-14 at 15:25 +0100, =D0=94=D0=B0=D0=BD=D0=B8=D0=BB=D0=BE =D0=
=A8=D0=B5=D0=B3=D0=B0=D0=BD wrote:
> =D0=88=D1=83=D1=87=D0=B5 =D1=83 21:51, Luke Schierer =D0=BD=D0=B0=D0=BF=
=D0=B8=D1=81=D0=B0:
>=20
> > I strongly agree with Ethan here.  No reason why they should have to
> > learn UTF-8 when we can automatically convert the encoding at compile
> > time.
>=20
> You actually can't (or not easily, anyway): intltool is reencoding
> only into it's own cache so it can construct properly merged .desktop,
> .xml, .schemas, .server and similar files which contain many
> languages.  Encoding ends up in the MO file as well, and translation
> needs to be re-encoded on every run of the program in that locale.

Why not just have an intltool-msgfmt script which checks the encoding,
and if it's not UTF-8, converts it before passing the contents of
the .po to msgfmt?

Richard