r6451 - trunk/BOOK/introduction/important

bdubbs at linuxfromscratch.org bdubbs at linuxfromscratch.org
Sun Jan 21 10:19:02 PST 2007


Author: bdubbs
Date: 2007-01-21 11:19:02 -0700 (Sun, 21 Jan 2007)
New Revision: 6451

Modified:
   trunk/BOOK/introduction/important/locale-issues.xml
Log:
Fixed some links in the  Locale Related Issues section

Modified: trunk/BOOK/introduction/important/locale-issues.xml
===================================================================
--- trunk/BOOK/introduction/important/locale-issues.xml	2007-01-21 17:50:20 UTC (rev 6450)
+++ trunk/BOOK/introduction/important/locale-issues.xml	2007-01-21 18:19:02 UTC (rev 6451)
@@ -58,7 +58,7 @@
     <xref linkend="a2ps"/> and <xref linkend="enscript"/>,
     the <option>-input-charset</option> option in unpatched
     <xref linkend="cdrtools"/>, and the character sets offered for display
-    in the menu of <xref linkend="links"/>. If the required encoding is not
+    in the menu of <xref linkend="Links"/>. If the required encoding is not
     in the list, the program usually becomes completely unusable. For
     non-interactive programs, it may be possible to work around this by
     converting the document to a supported input character set before
@@ -95,7 +95,8 @@
     In fact, the assumption made in the program may be completely
     invalid for documents where the Microsoft Windows operating system
     has set de facto standards. An example of this problem is ID3v1 tags
-    in MP3 files (see <ulink url="&blfs-wiki;/ID3v1Coding">this page</ulink>
+    in MP3 files (see the <ulink url="&blfs-wiki;/ID3v1Coding">BLFS Wiki 
+    ID3v1Coding page</ulink>
     for more details). For these cases, the only solution is to find a
     replacement program that doesn't have the issue (e.g., one that
     will allow you to specify the assumed document encoding).</para>
@@ -257,16 +258,16 @@
     <para>Severity: Low</para>
 
     <para>LFS expects that manual pages are in the language-specific (usually
-    8-bit) encoding, as specified on <ulink
-    url="&lfs-root;/chapter06/man-db.html"/>. However, some packages install
-    translated manual pages in UTF-8 encoding (e.g., Shadow, already dealt
-    with), or manual pages in languages not in the table. Not all BLFS packages
-    have been audited for conformance with the requirements put in LFS (the
-    large majority have been checked, and fixes placed in the book for packages
-    known to install non-conforming manual pages). If you find a manual page
-    installed by any of BLFS packages that is obviously in the wrong encoding,
-    please remove or convert it as needed, and report this to BLFS team as a
-    bug.</para> 
+    8-bit) encoding, as specified on the <ulink
+    url="&lfs-root;/chapter06/man-db.html">LFS Man DB page</ulink>. However,
+    some packages install translated manual pages in UTF-8 encoding (e.g.,
+    Shadow, already dealt with), or manual pages in languages not in the table.
+    Not all BLFS packages have been audited for conformance with the
+    requirements put in LFS (the large majority have been checked, and fixes
+    placed in the book for packages known to install non-conforming manual
+    pages). If you find a manual page installed by any of BLFS packages that is
+    obviously in the wrong encoding, please remove or convert it as needed, and
+    report this to BLFS team as a bug.</para> 
 
     <para>You can easily check your system for any non-conforming manual pages
     by copying the following short shell script to some accessible location,




More information about the blfs-book mailing list