<version>2.0</version>

<version>2.1</version>

<date>2005-05-08</date>

<date>2005-05-25</date>

There are two environment variables that need to be set in order to use

There are two environment variables that need to be set in order to use our new

our new UTF-8 locales: <c>LANG</c> and <c>LC_ALL</c>. There are also

UTF-8 locales: <c>LANG</c> and <c>LC_ALL</c>. There are also many different

many different ways to set them; some people prefer to only have a UTF-8

ways to set them; some people prefer to only have a UTF-8 environment for a

environment for a specific user, in which case they set them in their

specific user, in which case individual users can set locales in their

<path>~/.profile</path> or <path>~/.bashrc</path>. Others prefer to set the

<path>~/.bash_profile</path>.

locale globally. One specific circumstance where the author particularly

</p>

recommends doing this is when <path>/etc/init.d/xdm</path> is in use, because

this init script starts the display manager and desktop before any of the

<note>

aforementioned shell startup files are sourced, and so before any of the

If <c>bash</c> is called via the <c>sh</c> symlink, it will attempt to conform to POSIX standards, and will source <path>~/.profile</path> and <b>not</b> <path>~/.bash_profile</path>. To remedy this, you can either list the settings in both files, or you can link the files via <c>ln</c>.

variables are in the environment.

</note>

<p>

Other individuals prefer to set the locale globally. One specific circumstance

where the author particularly recommends global options is when a graphical

login manager is in use, because this init script starts the display manager

and desktop before any of the aforementioned shell startup files are sourced,

and so before any of the variables are in the environment.