From d84b37e24be2942f60ff395c22a576cb5ef1fcf6 Mon Sep 17 00:00:00 2001 From: Corinna Vinschen Date: Wed, 25 Mar 2009 14:33:05 +0000 Subject: [PATCH] * pathnames.sgml: Add a note that ASCII SO handling isn't foolproof under all circumstances. --- winsup/doc/ChangeLog | 5 +++++ winsup/doc/pathnames.sgml | 7 ++++++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index b49413d31..370a5a376 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2009-03-25 Corinna Vinschen + + * pathnames.sgml: Add a note that ASCII SO handling isn't foolproof + under all circumstances. + 2009-03-25 Corinna Vinschen * new-features.sgml: Add missing GB2312 and eucKR character sets. diff --git a/winsup/doc/pathnames.sgml b/winsup/doc/pathnames.sgml index 722c98b80..2c47bc371 100644 --- a/winsup/doc/pathnames.sgml +++ b/winsup/doc/pathnames.sgml @@ -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 UTF-16 and you can access the file. -Again, by using UTF-8 you can avoid this problem entirely. +Please be aware that this method is not entirely foolproof. +In some character set combinations it might not work for certain native +characters. + +Only by using the UTF-8 charset you can avoid this problem safely. +