Changeset f30e12dd
- Timestamp:
- 11/12/2005 09:43:22 AM (18 years ago)
- Branches:
- 6.1.1
- Children:
- 56052ff2
- Parents:
- 400ae369
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r400ae369 rf30e12dd 42 42 </itemizedlist> 43 43 </listitem> 44 45 <listitem><para>November 12, 2005 [matt]: Improve the heuristic for determining 46 a locale that is supported by both Glibc and packages outside LFS (bug 1642). 47 Many thanks to Alexander Patrakov for highlighting the numerous issues and for 48 reviewing the various suggested fixes.</para></listitem> 44 49 45 50 <listitem><para>November 12, 2005 [matt]: Omit running Bzip2's testsuite as a -
chapter06/glibc.xml
r400ae369 rf30e12dd 149 149 150 150 <para>To save time, an alternative to running the 151 previous command (which generates and installs every locale Glibc is152 aware of) is to install only those locales that are wanted and needed. 153 This can be achieved by using the <command>localedef</command> 154 command. Information on this command is located in the 155 <filename>INSTALL</filename> file in the Glibc source. However, there151 previous command (which generates and installs every locale listed in the 152 glibc-&glibc-version;/localedata/SUPPORTED file) is to install only those 153 locales that are wanted and needed. This can be achieved by using the 154 <command>localedef</command> command. Information on this command is located in 155 the <filename>INSTALL</filename> file in the Glibc source. However, there 156 156 are a number of locales that are essential in order for the tests of 157 157 future packages to pass, in particular, the … … 182 182 (including UTF-8) or right-to-left writing order. Numerous unofficial 183 183 and unstable patches are required to fix these problems, and it has 184 been decided by the LFS developers not to support such complex locales . This applies to the185 ja_JP and fa_IR locales as well—they have been installed only for 186 GCC and Gettext tests to pass, and the <command>watch</command> program 187 (part of the Procps package) does not work properly in them. Various 188 attempts to circumvent these restrictions are documented in 189 internationalization-related hints.</para>184 been decided by the LFS developers not to support such complex locales at this 185 time. This applies to the ja_JP and fa_IR locales as well—they have been 186 installed only for GCC and Gettext tests to pass, and the 187 <command>watch</command> program (part of the Procps package) does not work 188 properly in them. Various attempts to circumvent these restrictions are 189 documented in internationalization-related hints.</para> 190 190 191 191 <para>Build the linuxthreads man pages, which are a great reference -
chapter07/profile.xml
r400ae369 rf30e12dd 84 84 <screen>ISO-8859-1</screen> 85 85 86 <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.</para> 86 <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>. 87 It is important that the locale found using the heuristic above is tested prior 88 to it being added to the Bash startup files:</para> 89 90 <screen><userinput>LC_ALL=[locale name] locale country 91 LC_ALL=[locale name] locale language 92 LC_ALL=[locale name] locale charmap 93 LC_ALL=[locale name] locale int_curr_symbol 94 LC_ALL=[locale name] locale int_prefix</userinput></screen> 95 96 <para>The above commands should print the country and language names, the 97 character encoding used by the locale, the local currency and the prefix to dial 98 before the telephone number in order to get into the country. If any of the 99 commands above fail with a message similar to the one shown below, this means 100 that your locale was either not installed in Chapter 6 or is not supported by 101 the default installation of Glibc.</para> 102 103 <para><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></para> 104 105 <para>If this happens, you should either install the desired locale using the <command>localedef</command> command, or consider choosing a different locale. 106 Further instructions assume that there are no such error messages from Glibc. 107 </para> 108 109 <para>Some packages beyond LFS may also lack support for your chosen locale. One 110 example is the X library (part of the X Window System), which outputs the 111 following error message:</para> 112 113 <para><computeroutput>Warning: locale not supported by Xlib, locale set to C</computeroutput></para> 114 115 <para>Sometimes it is possible to fix this by removing the charmap part of the 116 locale specification, as long as that does not change the character map that 117 Glibc associates with the locale (this can be checked by running the 118 <command>locale charmap</command> command in both locales). For example, one 119 would have to change "de_DE.ISO-8859-15@euro" to 120 "de_DE@euro" in order to get this locale recognized by Xlib.</para> 121 122 <para>Other packages can also function incorrectly (but may not necessarily 123 display any error messages) if the locale name does not meet their expectations. 124 In those cases, investigating how other Linux distributions support your locale 125 might provide some useful information.</para> 87 126 88 127 <para>Once the proper locale settings have been determined, create the
Note:
See TracChangeset
for help on using the changeset viewer.