Re: non-ASCII character in untranslated strings

[Bob Proulx]

Chuck Swiger wrote:
> Paul Pogonyshev wrote:
> >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...

On a Debian host with sources on the network you can get the sources
for any individual package with 'apt-get source'.  So for glibc from
the libc6 package it would be:

  apt-get source libc6

But the glibc sources are large.

> >>>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)?

Agreed.  Can you simply avoid the problematic characters for a while
longer?  Perhaps I have a naive view but this seems to be something
that did not work prior to the recent fix for it.  Perhaps it is best
to wait for the fix to propagate more fully before depending upon it.

> 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.

The problem with owning glibc yourself is that it is a big project and
owning all security updates yourself is tedious.  Sure it can be done
and many people do it.  But for the majority of us we really rely upon
the teamwork of sharing a distro version and getting security updates
from it.  Branching a local version of libc is not something I
recommend anyone do without full thought of the consequences.

Bob