Ignore:
Timestamp:
01/21/2007 06:19:02 PM (17 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
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:
1 edited

Legend:

Unmodified
Added
Removed
  • introduction/important/locale-issues.xml

    rbefd6fb r648e8bc  
    5959    the <option>-input-charset</option> option in unpatched
    6060    <xref linkend="cdrtools"/>, and the character sets offered for display
    61     in the menu of <xref linkend="links"/>. If the required encoding is not
     61    in the menu of <xref linkend="Links"/>. If the required encoding is not
    6262    in the list, the program usually becomes completely unusable. For
    6363    non-interactive programs, it may be possible to work around this by
     
    9696    invalid for documents where the Microsoft Windows operating system
    9797    has set de facto standards. An example of this problem is ID3v1 tags
    98     in MP3 files (see <ulink url="&blfs-wiki;/ID3v1Coding">this page</ulink>
     98    in MP3 files (see the <ulink url="&blfs-wiki;/ID3v1Coding">BLFS Wiki
     99    ID3v1Coding page</ulink>
    99100    for more details). For these cases, the only solution is to find a
    100101    replacement program that doesn't have the issue (e.g., one that
     
    258259
    259260    <para>LFS expects that manual pages are in the language-specific (usually
    260     8-bit) encoding, as specified on <ulink
    261     url="&lfs-root;/chapter06/man-db.html"/>. However, some packages install
    262     translated manual pages in UTF-8 encoding (e.g., Shadow, already dealt
    263     with), or manual pages in languages not in the table. Not all BLFS packages
    264     have been audited for conformance with the requirements put in LFS (the
    265     large majority have been checked, and fixes placed in the book for packages
    266     known to install non-conforming manual pages). If you find a manual page
    267     installed by any of BLFS packages that is obviously in the wrong encoding,
    268     please remove or convert it as needed, and report this to BLFS team as a
    269     bug.</para>
     261    8-bit) encoding, as specified on the <ulink
     262    url="&lfs-root;/chapter06/man-db.html">LFS Man DB page</ulink>. However,
     263    some packages install translated manual pages in UTF-8 encoding (e.g.,
     264    Shadow, already dealt with), or manual pages in languages not in the table.
     265    Not all BLFS packages have been audited for conformance with the
     266    requirements put in LFS (the large majority have been checked, and fixes
     267    placed in the book for packages known to install non-conforming manual
     268    pages). If you find a manual page installed by any of BLFS packages that is
     269    obviously in the wrong encoding, please remove or convert it as needed, and
     270    report this to BLFS team as a bug.</para>
    270271
    271272    <para>You can easily check your system for any non-conforming manual pages
Note: See TracChangeset for help on using the changeset viewer.