Re: Broken po files

[Malcolm Tredinnick <malcolm commsecure com au>]

On Wed, 2003-09-10 at 03:55, Jordi Mallach wrote:
> Hello,
> 
> roozbeh found out that a handful of po files are not UTF-8 encoded in a
> few modules. This will break the affected translations badly.
> 
> Are we allowed to mass fix for gnome-2-4 and HEAD?
> 
> 
> [19:38] <roozbeh> Oskuro: did a grep. it seems that it's not the only one.
> [19:41] <roozbeh> Oskuro: file-roller's 'th', gnome-media's 'eu', 'gl', and
>         'lt', gnome-vfs's 'eu', 'ga', 'lt' and 'ro', intltool's 'fr' and
>         'fr_BE', libgnomeprint's 'ms', 'tr' and 'wa', libgnomeprintui's 'eu',
>         'gl', 'hr', 'it', 'lt', 'tr', and 'wa', and almost everything in
>         scrollkeeper.
> [19:42] <carlos> roozbeh: intltool have a po directory?
> [19:42] <roozbeh> carlos: oops. that is in its 'tests'.
> [19:42] <roozbeh> carlos: but the others are the same.
> [19:43] <carlos> :-P
> [19:43] > ok, is sucks.
> [19:43] <carlos> scrollkeeper is not a GNOME module

As far as Scrollkeeper goes, it is intentional that we are not forcing
everybody to use UTF-8 when creating their translations.

Somebody is going to have to explain to me where the breakage is here,
since I do not see what is going wrong: translated strings are not piped
directly to applications, they go via an XML file with valid encodings.
Internally, we are not calling bind_textdomain_codeset(..., "UTF-8") or
anything like that, so things work consistently under the covers as
well.

Scrollkeeper has to work in areas where the native encoding is not
UTF-8, so we have striven to keep it portable in this fashion.

Are you sure this is not just a mistaken over-generalisation from the
fact that GNOME applications all use UTF-8 under the covers to ease
things like GTK+ integration? Scrollkeeper does not have that
requirement.

I am going to be making a scrollkeeper release in about 12 hours, so if
somebody can point out a legitimate problem, I will fix it.

Cheers,
Malcolm