bennyc 05/04/24 14:11:51 Modified: xml/htdocs/doc/en utf-8.xml Log: bug 90144: updated and verified patch, sorry for the hassel guys
Revision Changes Path 1.12 +61 -24 xml/htdocs/doc/en/utf-8.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/utf-8.xml?rev=1.12&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/utf-8.xml?rev=1.12&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/utf-8.xml.diff?r1=1.11&r2=1.12&cvsroot=gentoo Index: utf-8.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- utf-8.xml 24 Apr 2005 12:18:59 -0000 1.11 +++ utf-8.xml 24 Apr 2005 14:11:51 -0000 1.12 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v 1.11 2005/04/24 12:18:59 bennyc Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/utf-8.xml,v 1.12 2005/04/24 14:11:51 bennyc Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/utf-8.xml"> @@ -192,13 +192,13 @@ <comment>(Replace "en_GB" with your desired locale setting)</comment> # <i>locale -a | grep 'en_GB'</i> en_GB -en_GB.utf8 +en_GB.UTF-8 </pre> <p> From the output of this command line, we need to take the result with a suffix -similar to <c>.utf8</c>. If there is no result with a suffix similar to -<c>.utf8</c>, we need to create a UTF-8 compatible locale. +similar to <c>.UTF-8</c>. If there is no result with a suffix similar to +<c>.UTF-8</c>, we need to create a UTF-8 compatible locale. </p> <note> @@ -208,7 +208,7 @@ <pre caption="Creating a UTF-8 locale"> <comment>(Replace "en_GB" with your desired locale setting)</comment> -# <i>localedef -i en_GB -f UTF-8 en_GB.utf8</i> +# <i>localedef -i en_GB -f UTF-8 en_GB.UTF-8</i> </pre> <p> @@ -228,32 +228,67 @@ <body> <p> -Although by now you might be determined to use UTF-8 system wide, the author -does not recommend setting UTF-8 for the root user. Instead, it is best to set -the locale in your user's <path>~/.profile</path> (or, if you are using a C -shell, <path>~/.login</path>). +There are two environment variables that need to be set in order to use +our new UTF-8 locales: <c>LANG</c> and <c>LC_ALL</c>. There are also +many different ways to set them; some people prefer to only have a UTF-8 +environment for a specific user, in which case they set them in their +<path>~/.profile</path> or <path>~/.bashrc</path>. Others prefer to set the +locale globally. One specific circumstance where the author particularly +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 +aforementioned shell startup files are sourced, and so before any of the +variables are in the environment. </p> -<note> -If you are not sure which file to use, use <path>~/.profile</path>. Also, if -you are unsure which code listing to use, use the Bourne version. -</note> +<p> +Setting the locale globally should be done using +<path>/etc/env.d/02local</path>. The file should look something like the +following: +</p> + +<pre caption="Demonstration /etc/env.d/02locale"> +<comment>(As always, change "en_GB.UTF-8" to your locale)</comment> +LC_ALL="en_GB.UTF-8" +LOCALE="en_GB.UTF-8" +</pre> -<pre caption="Setting the locale with environment variables (Bourne version)"> -export LANG="en_GB.utf8" -export LC_ALL="en_GB.utf8" +<p> +Next, the environment must be updated with the change. +</p> + +<pre caption="Updating the environment"> +# <i>env-update</i> +>>> Regenerating /etc/ld.so.cache... + * Caching service dependencies ... + # <i>source /etc/profile</i> </pre> -<pre caption="Setting the locale with environment variables (C shell version)"> -setenv LANG "en_GB.utf8" -setenv LC_ALL "en_GB.utf8" +<p> +Now, run <c>locale</c> with no arguments to see if we have the correct +variables in our environment: +</p> + +<pre caption="Checking if our new locale is in the environment"> +# <i>locale</i> +LANG=en_GB.UTF-8 +LC_CTYPE="en_GB.UTF-8" +LC_NUMERIC="en_GB.UTF-8" +LC_TIME="en_GB.UTF-8" +LC_COLLATE="en_GB.UTF-8" +LC_MONETARY="en_GB.UTF-8" +LC_MESSAGES="en_GB.UTF-8" +LC_PAPER="en_GB.UTF-8" +LC_NAME="en_GB.UTF-8" +LC_ADDRESS="en_GB.UTF-8" +LC_TELEPHONE="en_GB.UTF-8" +LC_MEASUREMENT="en_GB.UTF-8" +LC_IDENTIFICATION="en_GB.UTF-8" +LC_ALL=en_GB.UTF-8 </pre> <p> -Now, logout and back in to apply the change. We want these environment -variables in our entire environment, so it is best to logout and back in, or at -the very least to source <path>~/.profile</path> or <path>~/.login</path> in -the console from which you have started other processes. +That's everything. You are now using UTF-8 locales, and the next hurdle is the +configuration of the applications you use from day to day. </p> </body> @@ -671,7 +706,9 @@ <p> AltGr can be used with alphabetical keys alone. For example, AltGr and m, a -Greek lower-case letter mu is produced: 'µ'. +Greek lower-case letter mu is produced: 'µ'. AltGr and s produce a +scharfes s or esszet: 'ß'. As many European users would expect (because +it is marked on their keyboard), AltGr and 4 produces a Euro sign, '€'. </p> </body> -- [email protected] mailing list
