Re: non-ASCII character in untranslated strings

[Chuck Swiger]

Paul Pogonyshev wrote:
> Bruno Haible wrote:
> > Paul Pogonyshev wrote:
> > > >   - You are not using glibc >= 2.3.3 (on glibc systems) or
> > > >     libintl from GNU gettext >= 0.13 (on non-glibc systems).
> > > I have file `/lib/libc-2.3.2.so', so I suppose that means the first
> > > requirement fails?  Or how do I check?
> > Probably, yes. You can check for sure by unpacking the source of
> > /lib/libc-2.3.2.so and looking whether the ChangeLog contains this
> > entry:
>
> I'm afraid I don't have the sources.

The GPL guarantees you access to the sources.  However, most probably, they 
came with the Linux CD you installed your system from, or are available from 
the Debian site...

> > > Do you mean this problem exists on new distributions?
> > Newer distros use newer glibcs and therefore will not have this problem.
>
> That's true.  Just very sad that this problem was fixed not long ago
> and is still present in some _current_ new distros (Debian Sarge is
> quite new.)  I assume there is no way to overcome it other than
> upgrading libc (which I cannot demand from users)?

Oh, you have lots of choices.  This includes building a fixed version of libc 
yourself, updating your deployed systems to a newer OS release, living with 
the problem, finding a workaround, or finding some other tool to use.

--
-Chuck