Changeset 94aa6621 for chapter07/profile.xml
- Timestamp:
- 12/26/2005 07:46:12 PM (18 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- b82f0c0
- Parents:
- 5536f74
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/profile.xml
r5536f74 r94aa6621 70 70 <replaceable>[CC]</replaceable> with the two-letter code for the appropriate 71 71 country (e.g., <quote>GB</quote>). <replaceable>[charmap]</replaceable> should 72 be replaced with the canonical charmap for your chosen locale. Optional 73 modifiers such as <quote>@euro</quote> may also be present.</para> 72 be replaced with the canonical charmap for your chosen locale.</para> 74 73 75 74 <para>The list of all locales supported by Glibc can be obtained by running … … 78 77 <screen role="nodump"><userinput>locale -a</userinput></screen> 79 78 80 <para> Charmaps can have a number of aliases, e.g. <quote>ISO-8859-1</quote>79 <para>Locales can have a number of synonyms, e.g. <quote>ISO-8859-1</quote> 81 80 is also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>. 82 Some applications cannot handle the various synonyms correctly (e.g. require 83 that "UTF-8" is written as "UTF-8", not "utf8"), so it is safest in most 84 cases to choose the canonical name for a particular locale. To determine 81 Some applications cannot handle the various synonyms correctly, so it is 82 safest to choose the canonical name for a particular locale. To determine 85 83 the canonical name, run the following command, where <replaceable>[locale 86 84 name]</replaceable> is the output given by <command>locale -a</command> for … … 118 116 Glibc.</para> 119 117 120 <!-- FIXME: the xlib example will became obsolete real soon -->121 118 <para>Some packages beyond LFS may also lack support for your chosen locale. One 122 119 example is the X library (part of the X Window System), which outputs the … … 143 140 <literal># Begin /etc/profile 144 141 145 export LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>.<replaceable>[charmap]</replaceable> <replaceable>[@modifiers]</replaceable>142 export LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>.<replaceable>[charmap]</replaceable> 146 143 export INPUTRC=/etc/inputrc 147 144 … … 149 146 EOF</userinput></screen> 150 147 151 <para>The <quote>C</quote> (default) and <quote>en_US</quote> (the recommended152 one for United States English users) locales are different. <quote>C</quote>153 uses the US-ASCII 7-bit character set, and treats bytes with the high bit set154 as invalid characters. That's why, e.g., the <command>ls</command> command155 substitutes them with question marks in that locale. Also, an attempt to send156 mail with such characters from Mutt or Pine results in non-RFC-conforming157 messages being set (the charset in the outgoing mail is indicatsed as "unknown158 8-bit"). So you can use the <quote>C</quote> locale only if you are sure that159 you will never need 8-bit characters.</para>160 161 <para>UTF-8 based locales are not supported well by many programs. E.g., the162 <command>watch</command> program displays only ASCII characters in UTF-8163 locales and has no such restriction in traditional 8-bit locales like en_US.164 Without patches and/or installing software beyond BLFS, in UTF-8 based locales165 you will not be able to do such basic tasks as printing plain-text files from166 the command line, recording Windows-readable CDs with filenames containing167 non-ASCII characters, viewing ID3v1 tags in MP3 files and so on. It is also168 impossible (without damaging non-ASCII characters) to connect using ssh from169 the system using a UTF-8 based locale to a host that still uses a traditional170 8-bit locale, and vice versa. In short, use UTF-8 only if you are going to171 use KDE or GNOME and never open the terminal, or if you are going to tolerate172 bugs.</para>173 <!-- All abovementioned problems except "watch" have a known fix beyond BLFS -->174 175 148 <note> 176 <para>Bug reports reproducible only in UTF-8 locales and for which there 177 is no patch or other fix mentioned in the report, will be closed immediately, 178 without investigation, with the "WONTFIX" resolution and a "don't use this 179 program or revert to non-UTF-8 locale" comment. Patches that have ill 180 effects in non-UTF-8 locales (other than replacement of translated program 181 messages with English ones) will be rejected.</para> 149 <para>The <quote>C</quote> (default) and <quote>en_US</quote> (the 150 recommended one for United States English users) locales are different.</para> 182 151 </note> 183 152 153 <para>Setting the keyboard layout, screen font, and locale-related environment 154 variables are the only internationalization steps needed to support locales 155 that use ordinary single-byte encodings and left-to-right writing direction. 156 More complex cases (including UTF-8 based locales) require additional steps 157 and additional patches because many applications tend to not work properly 158 under such conditions. These steps and patches are not included in the LFS 159 book and such locales are not yet supported by LFS.</para> 160 184 161 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.