Changeset df8df0a5 for introduction/important
- Timestamp:
- 04/10/2010 10:48:57 AM (14 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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:
- c5dc5a2
- Parents:
- f9a051f9
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/locale-issues.xml
rf9a051f9 rdf8df0a5 144 144 don't respect that environment variable are buggy.</para> 145 145 146 <para>The <xref linkend="zip"/>, <xref linkend="unzip"/>, and 147 <xref linkend="nautilus-cd-burner"/> have this problem because 148 they hard-code the expected filename encoding. 149 <application>UnZip</application> contains a hard-coded conversion 150 table between the CP850 (DOS) and ISO-8859-1 (UNIX) encodings and 151 uses this table when extracting archives created under DOS or 152 Microsoft Windows. However, this assumption only works for those 153 in the US and not for anyone using a UTF-8 locale. Non-ASCII 154 characters will be mangled in the extracted filenames.</para> 155 156 <para>On the other hand, 146 <para>The <xref linkend="zip"/> and <xref linkend="unzip"/> have this 147 problem because they hard-code the expected filename encoding. 148 <application>UnZip</application> contains a hard-coded conversion table 149 between the CP850 (DOS) and ISO-8859-1 (UNIX) encodings and uses this table 150 when extracting archives created under DOS or Microsoft Windows. However, 151 this assumption only works for those in the US and not for anyone using a 152 UTF-8 locale. Non-ASCII characters will be mangled in the extracted 153 filenames.</para> 154 155 <!--<para>On the other hand, 157 156 <application>Nautilus CD Burner</application> checks names of 158 157 files added to its window for UTF-8 validity. This is wrong for … … 161 160 calls <command>mkisofs</command> with the 162 161 <parameter>-input-charset UTF-8</parameter> parameter, which is 163 only correct in UTF-8 locales.</para> 162 only correct in UTF-8 locales.</para>--> 164 163 165 164 <para>The general rule for avoiding this class of problems is to
Note:
See TracChangeset
for help on using the changeset viewer.