Changeset 648e8bc

Timestamp:

01/21/2007 06:19:02 PM (16 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, ken/inkscape-core-mods, krejzi/svn, lazarus, nosym, perl-modules, plabs/python-mods, qt5new, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226

Children:

57aa7a28

Parents:

befd6fb

Message:

Fixed some links in the Locale Related Issues section

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@6451 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• introduction/important/locale-issues.xml (modified) (3 diffs)

introduction/important/locale-issues.xml

@@ -59 +59 @@
     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
@@ -96 +96 @@
     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
@@ -258 +259 @@
 
     <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