* pathnames.sgml: Add a note that ASCII SO handling isn't foolproof
under all circumstances.
This commit is contained in:
parent
b10a036a92
commit
d84b37e24b
@ -1,3 +1,8 @@
|
|||||||
|
2009-03-25 Corinna Vinschen <corinna@vinschen.de>
|
||||||
|
|
||||||
|
* pathnames.sgml: Add a note that ASCII SO handling isn't foolproof
|
||||||
|
under all circumstances.
|
||||||
|
|
||||||
2009-03-25 Corinna Vinschen <corinna@vinschen.de>
|
2009-03-25 Corinna Vinschen <corinna@vinschen.de>
|
||||||
|
|
||||||
* new-features.sgml: Add missing GB2312 and eucKR character sets.
|
* new-features.sgml: Add missing GB2312 and eucKR character sets.
|
||||||
|
@ -388,7 +388,12 @@ character, it skips over the ASCII SO and handles the following bytes as
|
|||||||
a UTF-8 character. Thus, the filename is symmetrically converted back to
|
a UTF-8 character. Thus, the filename is symmetrically converted back to
|
||||||
UTF-16 and you can access the file.</para>
|
UTF-16 and you can access the file.</para>
|
||||||
|
|
||||||
<para>Again, by using UTF-8 you can avoid this problem entirely.</para>
|
<note><para>Please be aware that this method is not entirely foolproof.
|
||||||
|
In some character set combinations it might not work for certain native
|
||||||
|
characters.</para>
|
||||||
|
|
||||||
|
<para>Only by using the UTF-8 charset you can avoid this problem safely.
|
||||||
|
</para></note>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user