|  | @@ -35,7 +35,10 @@ suggested installation instructions.</para>
 | 
	
		
			
				|  |  |  <sect2 role="installation">
 | 
	
		
			
				|  |  |  <title>Installation of Vim</title>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -<para>First change the default locations of the <filename>vimrc</filename> and
 | 
	
		
			
				|  |  | +<para>First, unpack both
 | 
	
		
			
				|  |  | +<filename>vim-&vim-version;.tar.bz2</filename> and (optionally)
 | 
	
		
			
				|  |  | +<filename>vim-&vim-version;-lang.tar.gz</filename> archives into the same
 | 
	
		
			
				|  |  | +directory. Then change the default locations of the <filename>vimrc</filename> and
 | 
	
		
			
				|  |  |  <filename>gvimrc</filename> configuration files to <filename class="directory">/etc</filename>.</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <screen><userinput>echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >> src/feature.h
 | 
	
	
		
			
				|  | @@ -45,11 +48,14 @@ echo '#define SYS_GVIMRC_FILE "/etc/gvimrc"' >> src/feature.h</userinput><
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <screen><userinput>./configure --prefix=/usr --enable-multibyte</userinput></screen>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -<para>The optional <userinput>--enable-multibyte</userinput> switch
 | 
	
		
			
				|  |  | -includes multibyte editing support into
 | 
	
		
			
				|  |  | -vim. It is only needed for those people who ignore our recommendation not to
 | 
	
		
			
				|  |  | -use LFS in locales with multibyte character sets, but it does not hurt
 | 
	
		
			
				|  |  | -others.</para>
 | 
	
		
			
				|  |  | +<para>The optional but highly recommended
 | 
	
		
			
				|  |  | +<userinput>--enable-multibyte</userinput> switch
 | 
	
		
			
				|  |  | +includes support for editing files in multibyte character encodings into
 | 
	
		
			
				|  |  | +vim. It is needed for those people who ignore our recommendation not to
 | 
	
		
			
				|  |  | +use LFS in locales with multibyte character sets. It is also needed for
 | 
	
		
			
				|  |  | +people who want to be able to edit text files initially created
 | 
	
		
			
				|  |  | +in Linux distributions like Fedora Core
 | 
	
		
			
				|  |  | +that use UTF-8 as a default character set.</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <para>Compile the package:</para>
 | 
	
		
			
				|  |  |  
 | 
	
	
		
			
				|  | @@ -99,6 +105,7 @@ set nocompatible
 | 
	
		
			
				|  |  |  set backspace=2
 | 
	
		
			
				|  |  |  syntax on
 | 
	
		
			
				|  |  |  set background=dark
 | 
	
		
			
				|  |  | +set fileencodings=ucs-bom,utf-8,<replaceable>your-8-bit-charset</replaceable>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  " End /etc/vimrc
 | 
	
		
			
				|  |  |  <userinput>EOF</userinput></screen>
 | 
	
	
		
			
				|  | @@ -112,7 +119,14 @@ backspacing over line breaks, autoindents and the start of insert. The
 | 
	
		
			
				|  |  |  syntax highliting, while <emphasis>set background=dark</emphasis> gives the
 | 
	
		
			
				|  |  |  highliting a better color scheme for use on the black background of a linux
 | 
	
		
			
				|  |  |  console.  If you later use X and terminals with a light background, changing
 | 
	
		
			
				|  |  | -this will be useful.</para>
 | 
	
		
			
				|  |  | +this will be useful. The <emphasis>set fileencodings=...</emphasis> makes
 | 
	
		
			
				|  |  | +<command>vim</command> capable of detecting the character set of the
 | 
	
		
			
				|  |  | +file being edited. This is useful because bleeding-edge distributions
 | 
	
		
			
				|  |  | +like Fedora Core use UTF-8, and conservative ones like Debian
 | 
	
		
			
				|  |  | +use traditional 8-bit encodings for text files. If you have not
 | 
	
		
			
				|  |  | +passed the <option>--enable-multibyte</option> switch to the
 | 
	
		
			
				|  |  | +<command>./configure</command> command above, this line will not work.
 | 
	
		
			
				|  |  | +</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <para>Documentation for other available options can be obtained by running
 | 
	
		
			
				|  |  |  the following command:</para>
 |