about summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-12-28 02:59:59 +0000
committerUlrich Drepper <drepper@redhat.com>1999-12-28 02:59:59 +0000
commitffa156afcc46a0b8688a0094e62bc240b4b279a1 (patch)
tree7e4796907a02fde9a61a48c4cbafc48229eedba9 /FAQ.in
parentf3d703cd527d3566808da08ce30b22ec288a78a9 (diff)
downloadglibc-ffa156afcc46a0b8688a0094e62bc240b4b279a1.tar.gz
glibc-ffa156afcc46a0b8688a0094e62bc240b4b279a1.tar.xz
glibc-ffa156afcc46a0b8688a0094e62bc240b4b279a1.zip
Update.
	* iconvdata/gb2312.h (ucs4_to_gb2312): Fix mapping of 0x0101,
	0x2312, and 0x2500..0x254b.
	* iconvdata/TESTS: Add EUC-CN.
	* iconvdata/testdata/EUC-CN: New file.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in5
1 files changed, 5 insertions, 0 deletions
diff --git a/FAQ.in b/FAQ.in
index babca37a11..b894b76ffc 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -1505,6 +1505,11 @@ Before doing this look through the list of known problem first:
   In addition the Unicode tables contain mappings for the GBK characters
   0xA8BC, 0xA8BF, 0xA989 to 0xA995, and 0xFE50 to 0xFEA0.
 
+- when mapping from EUC-CN to GBK and vice versa we ignore the fact that
+  the coded character at position 0xA1A4 maps to different Unicode
+  characters.  Since the iconv() implementation can do whatever it wants
+  if it cannot directly map a character this is a perfectly good solution
+  since the semantics and appearance of the character does not change.
 
 
 Answers were given by: