Updated text in section 7.9 to better explain the Xlib locale example.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7667 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2006-07-13 14:37:29 +00:00
parent f67a9da4f7
commit 83f017331f
3 changed files with 22 additions and 11 deletions

View File

@ -35,6 +35,17 @@
</itemizedlist> </itemizedlist>
</listitem> </listitem>
--> -->
<listitem>
<para>July 13, 2006</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Updated text in section 7.9 (The Bash
Shell Startup Files) to better explain the Xlib example.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem> <listitem>
<para>July 12, 20006</para> <para>July 12, 20006</para>
<itemizedlist> <itemizedlist>

View File

@ -120,18 +120,18 @@ LC_ALL=&lt;locale name&gt; locale int_prefix</userinput></screen>
<!-- FIXME: the xlib example will became obsolete real soon --> <!-- FIXME: the xlib example will became obsolete real soon -->
<para>Some packages beyond LFS may also lack support for your chosen locale. One <para>Some packages beyond LFS may also lack support for your chosen locale. One
example is the X library (part of the X Window System), which outputs the example is the X library (part of the X Window System), which outputs the
following error message:</para> following error message if the locale does not exactly match one of the character
map names in its internal files:</para>
<screen><computeroutput>Warning: locale not supported by Xlib, locale set to C</computeroutput></screen> <screen><computeroutput>Warning: locale not supported by Xlib, locale set to C</computeroutput></screen>
<para>Here Xlib expects that the character map will be listed in uppercase <para>In several cases Xlib expects that the character map will be listed in
notation with canonical dashes. For instance, "ISO-8859-1" rather than uppercase notation with canonical dashes. For instance, "ISO-8859-1" rather
"iso88591". It is sometimes possible to fix this by removing the charmap part than "iso88591". It is also possible to find an appropriate specification by
of the locale specification, as long as that does not change the character removing the charmap part of the locale specification. This can be checked
map that Glibc associates with the locale. This can be checked by running by running the <command>locale charmap</command> command in both locales.
the <command>locale charmap</command> command in both locales. For example, For example, one would have to change "de_DE.ISO-8859-15@euro" to
one would have to change "de_DE.ISO-8859-15@euro" to "de_DE@euro" in order to "de_DE@euro" in order to get this locale recognized by Xlib.</para>
get this locale recognized by Xlib.</para>
<para>Other packages can also function incorrectly (but may not necessarily <para>Other packages can also function incorrectly (but may not necessarily
display any error messages) if the locale name does not meet their expectations. display any error messages) if the locale name does not meet their expectations.

View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?> <?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY version "SVN-20060712"> <!ENTITY version "SVN-20060713">
<!ENTITY releasedate "July 12, 2006"> <!ENTITY releasedate "July 13, 2006">
<!ENTITY milestone "6.2"> <!ENTITY milestone "6.2">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" --> <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->