linux-from-scratch/glfs
1
0
Fork 0
mirror of https://github.com/Zeckmathederg/glfs.git synced 2025-01-24 23:32:12 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fixed some links in the Locale Related Issues section

Browse Source 
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@6451 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Bruce Dubbs 2007-01-21 18:19:02 +00:00
parent befd6fb0bf
commit 648e8bce39
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
introduction/important/locale-issues.xml
View File

@ -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,