Changeset bc81164

Timestamp:

10/25/2008 09:38:03 PM (15 years ago)

Author:

DJ Lucas <dj@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

6da4dd7

Parents:

7f89db8

Message:

Removed previously commented working text.

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

File:

• chapter06/man-db.xml (modified) (2 diffs)

chapter06/man-db.xml

@@ -41 +41 @@
   <sect2 role="installation">
     <title>Installation of Man-DB</title>
-
-    <!-- <para>Two adjustments need to be made to the sources of Man-DB.</para> 
-
-    <para>The first change is a <command>sed</command> substitution to delete
-    the <quote>/usr/man</quote> and <quote>/usr/local/man</quote> lines in
-    the <filename>man_db.conf</filename> file to prevent redundant results
-    when using programs such as <command>whatis</command>:</para> -->
 
     <para>LFS creates <filename>/usr/man</filename> and
@@ -116 +109 @@
   <sect2>
     <title>Non-English Manual Pages in LFS</title>
-<!--
-    <para>Some packages provide UTF-8 manual pages, which previous versions of
-    <application>Man-DB</application> were unable to display correctly because
-    the expected (8-bit) encoding for each language was hard-coded in the
-    source of <application>Man-DB</application>.
-    <application>Man-DB</application> now uses the extension of the directory
-    name in order to determine the encoding of the manual pages stored within.
-    If no extension exists, <application>Man-DB</application> uses a built-in
-    table (see below) to determine the encoding.  E.g., because of "UTF-8" in
-    the directory name, it knows that all manual pages residing in 
-    <filename class="directory">/usr/share/man/fr.UTF-8</filename> are UTF-8
-    encoded and, according to the built-in table, expects all manual pages
-    residing in <filename class="directory">/usr/share/man/ru</filename> to
-    be encoded using KOI8-R.</para>
-
-    <para>Linux distributions have different policies concerning the character
-    encoding in which manual pages are stored in the filesystem. E.g., RedHat
-    stores all manual pages in UTF-8, while Debian previously used
-    language-specific (mostly 8-bit) encodings. Many other distributions simply
-    ignore the problem all together.  LFS also used the legacy encodings in
-    previuos versions of the book. This was chosen because of the ease of
-    configuration associated with <application>Man-DB</application>.
-    Additionally, <application>Man-DB</application> provided support for
-    Chinese and Japanese locales, and limited support for Korean, whereas
-    <application>Man</application> did not at that time.</para>
-
-    <para>In contrast, the setup in Fedora Core expects all manual pages
-    to be UTF-8 encoded, and stored in directories without suffixes.
-    Disagreement about the expected encoding of manual pages amongst
-    distribution vendors, has led to confusion for upstream package maintainers.
-    Some packages contain, UTF-8 manual pages, while others ship with manual
-    pages in legacy encodings.  Unlike the
-    <application>Man</application>/<application>Groff</application> setup in
-    Fedora Core, <application>Man-DB</application> can make very good decisions
-    about the on disk encoding and present the information to the user in their
-    prefered format, without complex configurations.</para>
-
-    <para><application>Man-DB</application> has, for the most part, made this
-    problem completely transparent to end users, as long as the manual pages
-    are installed into the correct directory.  There may be times, however,
-    where one encoding is preferred over the other.  For this purpose, the
-    <command>convert-mans</command> script was written. It will convert manual
-    pages to another encoding before (or after) installation.  Install the
-    <command>convert-mans</command> script with the following
-    instructions:</para>
--->
+
     <para>Some packages provide non-English manual pages. They are displayed 
     correctly only if their location and encoding matches the expectation of