Ignore:
Timestamp:
Feb 7, 2009, 2:42:23 PM (16 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
630a58e
Parents:
46945af
Message:

Updated Profile Information about UTF-8

File:
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/bootscripts/common/profile.xml

    r46945af r35cce5c  
    8686  the canonical name, run the following command, where <replaceable>[locale
    8787  name]</replaceable> is the output given by <command>locale -a</command> for
    88   your preferred locale (<quote>en_GB.iso88591</quote> in our example).</para>
     88  your preferred locale (<quote>en_US.utf8</quote> in our example).</para>
    8989
    9090<screen role="nodump"><userinput>LC_ALL=<replaceable>[locale name]</replaceable> locale charmap</userinput></screen>
    9191
    92   <para>For the <quote>en_GB.iso88591</quote> locale, the above command
     92  <para>For the <quote>en_US.utf8</quote> locale, the above command
    9393  will print:</para>
    9494
    95 <screen><computeroutput>ISO-8859-1</computeroutput></screen>
     95<screen><computeroutput>UTF-8</computeroutput></screen>
    9696
    97   <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
     97  <para>This results in a final locale setting of <quote>en_US.UTF-8</quote>.
    9898  It is important that the locale found using the heuristic above is tested prior
    9999  to it being added to the Bash startup files:</para>
     
    149149EOF</userinput></screen>
    150150
    151   <note>
    152     <para>The <quote>C</quote> (default) and <quote>en_US</quote>
    153     (the recommended one for United States English users) locales are
    154     different.</para>
    155   </note>
    156 
    157151  <para>Setting the keyboard layout, screen font, and locale-related
    158152  environment variables are the only internationalization steps needed to
    159153  support locales that use ordinary single-byte encodings and left-to-right
    160   writing direction. More complex cases (including UTF-8 based locales)
    161   require additional steps and additional patches because many applications
    162   tend to not work properly under such conditions. These steps and patches
    163   are not included in the CLFS book and such locales are not yet supported
    164   by CLFS.</para>
     154  writing direction. UTF-8 has been testing on the English, French, and
     155  German, Spanish locales. All other locales are untested. If you discover
     156  issues with any other locale please open a ticket in our trac system.</para>
    165157
    166158</sect1>
Note: See TracChangeset for help on using the changeset viewer.