FIXED in ruby-gettext-1.90.0 [bug #21263] BUG: ruby-gettext-1.7.0-1 or later converts UTF-8 mo files into another charset (fwd)

[boud]

hi all,

Bug #21263 was solved (almost immediately after being posted to 
ruby-gettext, but i failed to read the followup...) - it was a bug
in ruby-gettext itself.

i'll close this bug in one week's time (25.02.2008) unless
someone objects. As i mention below: either edit gettext.rb yourself,
and remember to do it each time until you get up to 1.90.0, or else
just wait until 1.90.0 gets into your distribution automatically through
the experimental2stable pipeline.

cheers
boud


---------- Forwarded message ----------
> Date: Mon, 18 Feb 2008 00:22:47 +0000
> Subject: [bug #21263] BUG: ruby-gettext-1.7.0-1 or later converts
     UTF-8 mo files into another charset


Follow-up Comment #3, bug #21263 (project samizdat):

Masao Mutoh found a bug in ruby-gettext:

http://rubyforge.org//tracker/index.php?func=detail&aid=15513&group_id=855&atid=3378


diff -u -r1.32 gettext.rb
--- gettext.rb  29 Oct 2007 15:32:39 -0000      1.32
+++ gettext.rb  10 Nov 2007 02:31:43 -0000
@@ -86,7 +86,7 @@
     end
     opt[:locale] = opt[:locale] ? Locale::Object.new(opt[:locale])
: Locale.get
     opt[:charset] = output_charset if output_charset
-    locale.charset = opt[:charset] if opt[:charset]
+    opt[:locale].charset = opt[:charset] if opt[:charset]
     Locale.set_current(opt[:locale])
     target_key = bound_target
     manager = @@__textdomainmanagers[target_key]


This solves the bug on both systems on which it occurred
previously.

This correction appears in ruby-gettext-1.90.0 which was
released just two weeks ago on 3 Feb 2008:
http://rubyforge.org/frs/?group_id=855

It's not yet in debian unstable, but it looks like the debian
pipeline will eventually get it automatically into ruby-1.8 and ruby-1.9
within 6-12 months:
http://packages.debian.org/search?keywords=libgettext&searchon=names&suite=all&section=all

Dmitry: my guess is that you'll prefer to set this bug
as "won't fix" for this reason: let bug corrections flow
through the system systematically, and people who want to
correct them earlier have to know what they're doing (i assume
that's the policy).

So for people who "know what they're doing", the above one
line fix works perfectly as far as i have seen the bug and
tested the fix.

For other people, sit and wait for the software to flow
through the experimental-to-stable pipeline.

i'll close this bug in one week's time (25.02.2008) unless
someone objects.


 _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?21263>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/