Checked in Alexander Patrakov's changes for the console page, and related bootscripts update.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8697 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter01/changelog.xml

@@ -39,6 +39,15 @@
     <listitem>
       <para>2008-10-23</para>
       <itemizedlist>
+        <listitem>
+          <para>[dj] - Updated to lfs-bootscritps-20081023 to account for
+          changes in the console page.</para>
+        </listitem>
+        <listitem>
+          <para>[dj] - Updated text in console page to match current situation
+          regarding linux kernel changes. Thanks to Alexander Patrakov for
+          the text and explanations.</para>
+        </listitem>
         <listitem>
           <para>[dj] - Updated Man-DB instructions and text covering manual
           pages and related i18n issues.</para>

chapter07/console.xml

@@ -84,11 +84,14 @@
         name, <quote>-m</quote>, and the name of the application character
 	map to load. E.g., in order to load the <quote>lat1-16</quote> font
 	together with the <quote>8859-1</quote> application character map
-	(as it is appropriate in the USA), <!-- because of the copyright sign -->
+	(as it is appropriate in the USA), 
+        <!-- because of the copyright sign -->
 	set this variable to <quote>lat1-16 -m 8859-1</quote>.
-        If this variable is not set, the bootscript will not run the
+        In UTF-8 mode, the kernel uses the application character map for
-        <command>setfont</command> program, and the default VGA font will be
+        conversion of composed 8-bit key codes in the keymap to UTF-8, and thus
-        used together with the default application character map.</para>
+        the argument of the "-m" parameter should be set to the encoding of the
+        composed key codes in the keymap.</para>
+
       </listitem>
     </varlistentry>
 
@@ -183,17 +186,17 @@ EOF</userinput></screen>
     </listitem>
 
     <listitem>
-      <para>There is no pre-made UTF-8 Russian keymap, therefore it has to be
+      <para>The following example illustrates keymap autoconversion from
-      produced by converting the existing KOI8-R keymap as illustrated
+      ISO-8859-15 to UTF-8 and enabling dead keys in Unicode mode:</para>
-      below:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
 <literal># Begin /etc/sysconfig/console
 
 UNICODE="1"
-KEYMAP="ru-ms"
+KEYMAP="de-latin1"
-LEGACY_CHARSET="koi8-r"
+KEYMAP_CORRECTIONS="euro2"
-FONT="LatArCyrHeb-16"
+LEGACY_CHARSET="iso-8859-15"
+FONT="LatArCyrHeb-16 -m 8859-15"
 
 # End /etc/sysconfig/console</literal>
 EOF</userinput></screen>
@@ -204,14 +207,16 @@ EOF</userinput></screen>
       character by themselves, but put an accent on the character produced
       by the next key) or define composition rules (such as: <quote>press
       Ctrl+. A E to get &AElig;</quote> in the default keymap).
-      Linux-&linux-version; in UTF-8 keyboard mode assumes that accented
+      Linux-&linux-version; interprets dead keys and composition rules in the
-      characters produced via dead keys or composing are in the Latin-1 range
+      keymap correctly only when the source characters to be composed together
-      of Unicode, and it is impossible to change this assumption. Thus,
+      are not multibyte. This deficiency doesn't affect keymaps for European
-      accented characters needed for, e.g., the Czech language, can't be typed
+      languages, because there accents are added to unaccented ASCII
-      on Linux console in UTF-8 mode (but files containing these characters can
+      characters, or two ASCII characters are composed together. However, in
-      be displayed correctly). The solution is either to avoid the use of
+      UTF-8 mode it is a problem, e.g., for the Greek language, where one
-      UTF-8, or to install the X window system that doesn't have this
+      sometimes needs to put an accent on the letter <quote>&alpha;</quote>.
-      limitation in its input handling.</para>
+      The solution is either to avoid the use of UTF-8, or to install the
+      X window system that doesn't have this limitation in its input
+      handling.</para>
     </listitem>
 
     <listitem>

packages.ent

@@ -293,7 +293,7 @@
 <!ENTITY less-ch6-du "2.8 MB">
 <!ENTITY less-ch6-sbu "0.1 SBU">
 
-<!ENTITY lfs-bootscripts-version "20080522">                 <!-- Scripts depend on this format -->
+<!ENTITY lfs-bootscripts-version "20081023">                 <!-- Scripts depend on this format -->
 <!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB">         <!-- Updated in Makefile -->
 <!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.bz2">
 <!ENTITY lfs-bootscripts-md5 "BOOTSCRIPTS-MD5SUM">           <!-- Updated in Makefile -->