|  | @@ -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
 | 
	
		
			
				|  |  | -        <command>setfont</command> program, and the default VGA font will be
 | 
	
		
			
				|  |  | -        used together with the default application character map.</para>
 | 
	
		
			
				|  |  | +        In UTF-8 mode, the kernel uses the application character map for
 | 
	
		
			
				|  |  | +        conversion of composed 8-bit key codes in the keymap to UTF-8, and thus
 | 
	
		
			
				|  |  | +        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
 | 
	
		
			
				|  |  | -      produced by converting the existing KOI8-R keymap as illustrated
 | 
	
		
			
				|  |  | -      below:</para>
 | 
	
		
			
				|  |  | +      <para>The following example illustrates keymap autoconversion from
 | 
	
		
			
				|  |  | +      ISO-8859-15 to UTF-8 and enabling dead keys in Unicode mode:</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <screen role="nodump"><userinput>cat > /etc/sysconfig/console << "EOF"
 | 
	
		
			
				|  |  |  <literal># Begin /etc/sysconfig/console
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  UNICODE="1"
 | 
	
		
			
				|  |  | -KEYMAP="ru-ms"
 | 
	
		
			
				|  |  | -LEGACY_CHARSET="koi8-r"
 | 
	
		
			
				|  |  | -FONT="LatArCyrHeb-16"
 | 
	
		
			
				|  |  | +KEYMAP="de-latin1"
 | 
	
		
			
				|  |  | +KEYMAP_CORRECTIONS="euro2"
 | 
	
		
			
				|  |  | +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 Æ</quote> in the default keymap).
 | 
	
		
			
				|  |  | -      Linux-&linux-version; in UTF-8 keyboard mode assumes that accented
 | 
	
		
			
				|  |  | -      characters produced via dead keys or composing are in the Latin-1 range
 | 
	
		
			
				|  |  | -      of Unicode, and it is impossible to change this assumption. Thus,
 | 
	
		
			
				|  |  | -      accented characters needed for, e.g., the Czech language, can't be typed
 | 
	
		
			
				|  |  | -      on Linux console in UTF-8 mode (but files containing these characters can
 | 
	
		
			
				|  |  | -      be displayed correctly). 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>
 | 
	
		
			
				|  |  | +      Linux-&linux-version; interprets dead keys and composition rules in the
 | 
	
		
			
				|  |  | +      keymap correctly only when the source characters to be composed together
 | 
	
		
			
				|  |  | +      are not multibyte. This deficiency doesn't affect keymaps for European
 | 
	
		
			
				|  |  | +      languages, because there accents are added to unaccented ASCII
 | 
	
		
			
				|  |  | +      characters, or two ASCII characters are composed together. However, in
 | 
	
		
			
				|  |  | +      UTF-8 mode it is a problem, e.g., for the Greek language, where one
 | 
	
		
			
				|  |  | +      sometimes needs to put an accent on the letter <quote>α</quote>.
 | 
	
		
			
				|  |  | +      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>
 |