Ignore:
Timestamp:
12/29/2005 06:15:18 AM (18 years ago)
Author:
Randy McMurchy <randy@…>
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:
4cca673
Parents:
3cd5c69
Message:

Minor fixes to the Locale Related Issues page

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

File:
1 edited

Legend:

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

    r3cd5c69 rc151abf  
    6767        <para>Use of <application>UnZip</application> in the
    6868        <application>JDK</application>, <application>Mozilla</application>,
    69         <application>DocBook</application> or any other BLFS installation
    70         instructions is not a problem, as these applications never use
     69        <application>DocBook</application> or any other BLFS package
     70        installation is not a problem, as BLFS instructions never use
    7171        <application>UnZip</application> to extract a file with non-ASCII
    72         characters in its name.</para>
     72        characters in the file's name.</para>
    7373      </note>
    7474
     
    8787      <para>When using <command>unzip</command> to unpack a ZIP archive
    8888      containing non-ASCII filenames, the filenames are damaged because
    89       <command>unzip</command> uses improper conversion when any of
    90       <replaceable>[SOMETHING NEEDS TO BE PUT HERE AS THE SENTENCE WAS
    91       INCOMPLETE]</replaceable>. For example, in the ru_RU.KOI8-R locale,
    92       conversion of filenames from CP866 to KOI8-R is required, but conversion
    93       from CP850 to ISO-8859-1 is done, which produces filenames consisting of
    94       undecipherable characters instead of words (the closest equivalent
    95       understandable example for English-only users is rot13). There are
    96       several ways around this limitation:</para>
     89      <command>unzip</command> uses improper conversion when any of its
     90      encoding assumptions are incorrect. For example, in the ru_RU.KOI8-R
     91      locale, conversion of filenames from CP866 to KOI8-R is required, but
     92      conversion from CP850 to ISO-8859-1 is done, which produces filenames
     93      consisting of undecipherable characters instead of words (the closest
     94      equivalent understandable example for English-only users is rot13). There
     95      are several ways around this limitation:</para>
    9796
    9897      <para>1) For unpacking ZIP archives with filenames containing non-ASCII
Note: See TracChangeset for help on using the changeset viewer.