On Fri, Oct 06, 2006 at 02:04:54PM -0600, Andrew McNabb wrote:
> Здраво!
> 
> 2) I used to use aterm as my terminal.  I now use rxvt-unicode.  There
> are a number of others that work well with Unicode, too.  Plain old
> xterm, plain old rxvt, and plain old aterm are not Unicode-aware.

Plain old xterm works for me.  I have gentoo and the unicode flag was
set when I built it.  I'm not sure about other distributions, but I
imagine most of them have a relatively recent xterm with unicode
support.

So I can see your Serbian hello no problem (Здраво).  Try Ctrl +
right-click to see if UTF-8 is checked in the menu.  If your LANG (or
LC_ALL) was set correctly before X was started, xterm should have UTF-8
checked automatically.

> You probably also want to change the system-wide default (maybe in
> /etc/enviroment or somewhere like that), since the environment variable
> needs to get set before the terminal program is started.

On gentoo there is a file /etc/locale.gen (or /etc/locales.build if you
haven't updated in a while) that should contain all the locales you
want.  Make sure en_US.UTF-8/UTF-8 is in there, uncommented, and if not
run locale-gen to fix it.

Also you'll want to put LANG="en_US.UTF-8" in your /etc/env.d/02locale
file.  I think I was following this guide when I found out about all
this:

http://www.gentoo.org/doc/en/utf-8.xml

> Anyway, that's it for now.

At a shell prompt type "locale" and hit enter.  If you see something
like this you'll know your LANG (or LC_ALL) was set correctly:

LANG=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

If you see "POSIX" or "C" or "en_US/ISO-8859-1" then go and figure out
why LC_ALL or LANG is not getting set like you want it to.

One thing to make sure is your terminal is using a font that supports
all the characters you want to display.  One particular good font is
called iso10646 or something.  Anyway, I know that is the font I'm using
in xterm because of these lines in my XTerm resource file (in
app-defaults):

*VT100.utf8Fonts.font2: -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1
*VT100.utf8Fonts.font: 
-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
*VT100.utf8Fonts.font3: 
-misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1
*VT100.utf8Fonts.font4: 
-misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1
*VT100.utf8Fonts.font5: 
-misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
*VT100.utf8Fonts.font6: 
-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1

Also, another cool thing to learn about unicode is the BOM (Byte-Order
Marker).  If your text file starts with a BOM, then many text editors
(including vi and even notepad.exe on windows) will recognize that and
know your text file is in UTF-8 (or UTF-16 or whatever it is).  Then it
will be more likely to display your file correctly.  I think vim has a
setting for saving the BOM automatically, but I can't remember now.

See this page for details about BOM:

http://www.websina.com/bugzero/kb/unicode-bom.html

Phillip

P.S.  I'm sticking with white on black.  It's easier on my eyes :)

-- 
Phillip Hellewell <phillip AT hellewell.homeip.net>

--------------------
BYU Unix Users Group 
http://uug.byu.edu/ 

The opinions expressed in this message are the responsibility of their
author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG. 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to