Rename terms in correspondence with multibyte(3)

8-bit wide -> single C chars
16-bit wide -> wide or multibyte
No English touched.

1 files changed, 27 insertions, 21 deletions

diff --git a/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml b/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml
index b4eaff7899..d29eb004d5 100644
--- a/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml
@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.33 2000/03/21 16:54:56 ache Exp $
+     $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.34 2000/04/10 17:27:51 phantom Exp $
 -->
 
 <chapter id="l10n">
@@ -127,13 +127,14 @@
     <sect2>
       <title>Encodings</title>
 
-      <para>Some languages use non-ASCII encodings that are 8-bit or
-        16-bit wide characters.  Older applications do not recognize them
+      <para>Some languages use non-ASCII encodings that are 8-bit, wide
+	or multibyte characters, see &man.multibyte.3; for more
+	details. Older applications do not recognize them
 	and mistake them for control characters.  Newer applications
 	usually do recognize 8-bit characters.  Depending on the
 	implementation, users may be required to compile an application
-	with 16-bit support, or configure it correctly.  To be able to
-	input and process 16-bit wide characters, the <ulink
+	with wide or multibyte characters support, or configure it correctly.
+	To be able to input and process wide or multibyte characters, the <ulink
 	url="../ports/">FreeBSD Ports collection</ulink> has provided
 	each language with different programs.  Refer to the i18n
 	documentation in the respective FreeBSD Port.</para>
@@ -146,12 +147,13 @@
 
       <itemizedlist>
 	<listitem>
-	  <para>Language specific 8-bit wide character sets, i.e.,
+	  <para>Language specific single C chars character sets
+	  (see &man.multibyte.3;), i.e.,
 	    ISO_8859-1, KOI8-R, CP437.</para>
 	</listitem>
 
 	<listitem>
-	  <para>16-bit wide encodings, f.e. EUC, Big5.</para>
+	  <para>Wide or multibyte encodings, f.e. EUC, Big5.</para>
 	</listitem>
       </itemizedlist>
 
@@ -363,9 +365,9 @@ user:password:1111:11:<replaceable>language</replaceable>:0:0:User Name:/home/us
     <sect2 id="setting-console">
       <title>Console Setup</title>
 
-      <para>For all 8-bit wide languages, set the correct console fonts
-        in <filename>/etc/rc.conf</filename> for the language in question
-	with:</para>
+      <para>For all single C chars character sets, set the correct
+	console fonts in <filename>/etc/rc.conf</filename> for the
+	language in question with:</para>
 
       <programlisting>
 font8x16=<replaceable>font_name</replaceable>
@@ -377,7 +379,8 @@ font8x8=<replaceable>font_name</replaceable></programlisting>
 	without the <filename>.fnt</filename> suffix.</para>
 
       <para>Also be sure to set the correct keymap and screenmap for your
-        8-bit language through <filename>/stand/sysinstall</filename>.
+	single C chars character set through
+	<filename>/stand/sysinstall</filename>.
 	Once inside sysinstall, choose <literal>Configure</literal>, then
 	<literal>Console</literal>.  Alternatively, you can add the
 	following to <filename>/etc/rc.conf</filename>:</para>
@@ -466,8 +469,9 @@ options         SC_MOUSE_CHAR=0x03</programlisting>
 	</tgroup>
       </informaltable>
 
-      <para>For 16-bit wide languages, use the correct FreeBSD port in
-        your <filename>/usr/ports/<replaceable>language</replaceable></filename>
+      <para>For wide or multibyte characters languages, use the correct
+	FreeBSD port in your
+	<filename>/usr/ports/<replaceable>language</replaceable></filename>
 	directory.  Some ports appear as console while the system sees it
 	as serial vtty's, hence you must reserve enough vtty's for both
 	X11 and the pseudo-serial console.  Here is a partial list of
@@ -537,8 +541,9 @@ options         SC_MOUSE_CHAR=0x03</programlisting>
     <sect2>
       <title>Printer Setup</title>
 
-      <para>8-bit characters are usually hardware coded into printers.
-        16-bit characters require special setup and we recommend using
+      <para>Some single C chars character sets are usually hardware
+	coded into printers. Wide or multibyte
+	character sets require special setup and we recommend using
 	<application>apsfilter</application>.  You may also convert the
 	document to Postscript or PDF formats using language specific
 	converters.</para>
@@ -548,11 +553,12 @@ options         SC_MOUSE_CHAR=0x03</programlisting>
       <title>Kernel and File Systems</title>
 
       <para>The FreeBSD FFS filesystem is 8-bit clean, so it can be used
-	with any 8-bit wide character set, but there is no character set
+	with any single C chars character set (see &man.multibyte.3;),
+	but there is no character set
 	name stored in the filesystem; i.e., it is raw 8-bit and does not
 	know anything about encoding order.  Officially, FFS does not
-	support any form of 16-bit wide character sets yet.  However, many
-	16-bit wide character sets have independent patches for FFS
+	support any form of wide or multibyte character sets yet.  However, some
+	wide or multibyte character sets have independent patches for FFS
 	enabling such support.  They are only temporary unportable
 	solutions or hacks and we have decided to not include them in the
 	source tree.  Refer to respective languages' websites for more
@@ -600,7 +606,7 @@ options         SC_MOUSE_CHAR=0x03</programlisting>
       <para>To the contrary of common perception, i18n compliant code is
 	easy to write.  Usually, it only involves wrapping your strings
 	with library specific functions.  In addition, please be sure to
-	allow for 16-bit wide character support.</para>
+	allow for wide or multibyte characters support.</para>
 
       <sect3>
 	<title>A Call to Unify the i18n effort</title>
@@ -622,11 +628,11 @@ options         SC_MOUSE_CHAR=0x03</programlisting>
       <sect3>
 	<title>Perl and Python</title>
 
-	<para>Perl and Python have i18n and 16-bit wide character handling
+	<para>Perl and Python have i18n and wide characters handling
 	  libraries.  Please use them for i18n compliance.</para>
 
 	<para>In older FreeBSD versions,
-	  Perl may gives warning about not having a 16-bit wide locale
+	  Perl may gives warning about not having a wide characters locale
 	  that is already installed in your system.  You can set the
 	  environmental variable <envar>LD_PRELOAD</envar> to
 	  <filename>/usr/lib/libxpg4.so</filename> in your shell.</para>