> Hmm ... interesting idea, basically invent our own modified version > of GB18030 (or SJIS?) for backend-internal storage. But I'm not > sure how to make it work without enlarging the string, which'd defeat > the OP's argument. It looks to me like the second-byte code space is > already pretty full in both encodings. But as he already admitted, actually GB18030 is 4 byte encoding, rather than 2 bytes. So maybe we could find a way to map original GB18030 to ASCII-safe GB18030 using 4 bytes. As for SJIS, no big demand for the encoding in Japan these days. So I think we can leave it as it is. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
