diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index e8f2eb5a5f..454f233c42 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -14,7 +14,7 @@
 
     <corpauthor>The FreeBSD Documentation Project</corpauthor>
 
-    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.158 2001/03/16 01:35:30 dd Exp $</pubdate>
+    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.159 2001/03/17 01:33:47 dd Exp $</pubdate>
 
     <copyright>
       <year>1995</year>
@@ -3617,6 +3617,30 @@ quit</programlisting>
         </answer>
       </qandaentry>
 
+      <qandaentry>
+        <question id="cdrom-unicode-filenames">
+          <para>When I mount a CDROM, all non-English characters in
+            filenames show up as <quote>?</quote>.</para>
+        </question>
+
+        <answer>
+          <para>Most likely your CDROM uses the <quote>Joilet</quote>
+            extention for storing information about files and directories.
+            This extension specifies that all filenames are stored using
+            Unicode two-byte characters.  Currently, efforts are under way
+            to introduce a generic Unicode interface into the FreeBSD
+            kernel, but since that isn't ready yet, the CD9660 driver does
+            not have the ability to decode the characters in the
+            filenames.</para>
+
+          <para>As a temporary solution, starting with FreeBSD 4.3, a
+            special hook has been added into the CD9660 driver to allow the
+            user to load an appropriate conversion table on the fly.
+            Modules for some of the common encodings are available via the
+            <filename>sysutils/cd9660_unicode</filename> port.</para>
+        </answer>
+      </qandaentry>
+
       <qandaentry>
         <question id="printer-slow">
           <para>My printer is ridiculously slow. What can I do ?</para>
diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml
index e8f2eb5a5f..454f233c42 100644
--- a/en_US.ISO_8859-1/books/faq/book.sgml
+++ b/en_US.ISO_8859-1/books/faq/book.sgml
@@ -14,7 +14,7 @@
 
     <corpauthor>The FreeBSD Documentation Project</corpauthor>
 
-    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.158 2001/03/16 01:35:30 dd Exp $</pubdate>
+    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.159 2001/03/17 01:33:47 dd Exp $</pubdate>
 
     <copyright>
       <year>1995</year>
@@ -3617,6 +3617,30 @@ quit</programlisting>
         </answer>
       </qandaentry>
 
+      <qandaentry>
+        <question id="cdrom-unicode-filenames">
+          <para>When I mount a CDROM, all non-English characters in
+            filenames show up as <quote>?</quote>.</para>
+        </question>
+
+        <answer>
+          <para>Most likely your CDROM uses the <quote>Joilet</quote>
+            extention for storing information about files and directories.
+            This extension specifies that all filenames are stored using
+            Unicode two-byte characters.  Currently, efforts are under way
+            to introduce a generic Unicode interface into the FreeBSD
+            kernel, but since that isn't ready yet, the CD9660 driver does
+            not have the ability to decode the characters in the
+            filenames.</para>
+
+          <para>As a temporary solution, starting with FreeBSD 4.3, a
+            special hook has been added into the CD9660 driver to allow the
+            user to load an appropriate conversion table on the fly.
+            Modules for some of the common encodings are available via the
+            <filename>sysutils/cd9660_unicode</filename> port.</para>
+        </answer>
+      </qandaentry>
+
       <qandaentry>
         <question id="printer-slow">
           <para>My printer is ridiculously slow. What can I do ?</para>