Re: [debian-user] International Characters
> On Wed, Oct 15, 2003 at 02:05:38PM -0700, Tom wrote:
> > On Tue, Oct 14, 2003 at 02:40:09PM +0200, Rüdiger Kuhlmann wrote:
> > > 100 DM = 51 ? 13 ¢.
> > My /etc/environment is now: LANG=en_US, and 'locale' says "en_US" for
> > everthing except LC_ALL which is blank. So things like ½,é,¢ are
> > working, but what I guess is the Euro symbol in Rüdiger's signature
> > is a ?. (FYI: If I hit e in mutt in Rüdiger's message, Nano shows "the
> > universal currency" symbol.
You could use the ISO-8859-15 encoding, which replaces ~ 6 characters, e.g.
the currency symbol for the Euro sign. However, it's not really worth it
unless you're European or need the Euro sign for other reasons.
> > What's "the next step" to take.
> Whoops, I posted too fast: I set my locale to "en_US.UTF-8" and I see
> the Euro symbol now. But now my question is: should I just leave the
> locale at this? Will some text editors start saving in Wide chars now?
> Am I going to be missing further functionality? Or UTF-8 just nirvana?
That's your choice. You'll have a broader set of characters available, but
there will be programs that won't cope with it. Examples are e.g. joe
(treats them byte-wise), elm, pine, irc (can only recode byte encodings),
telnet (an upper case Ü is 0xc3 0x9c, the 0x9c will be treated by telnet
like a 0x1c, causing some out of band information exchanged instead of the
0xc9 sent), and more. KDE and GNOME apps usually cope well, definately
the "official" programs. Games usually are bad at it, like not allowing
umlauts to be entered at all. So you're going to have fun replacing or
fixing the broken programs.
Other then that, you need to recode your plain text files (and file names)
into UTF-8. If all your files are US-ASCII, then you need to do nothing,
because US-ASCII is a subset of ISO-8859-1 and UTF-8 as well.
100 DM = 51 € 13 ¢.
100 € = 195 DM 58 pf.