Hi Tony,
On 2/27/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote:
[...]
Here is an alternative way to handle it, which may be "the right way" from a
conceptual point of view, and in the long term, though it may be much more
difficult from the coding point of view. It may or may not be "the right thing
to do" pragmatically:
Treat GB18030 as what it is, namely, a Unicode Transformation Format. In other
words, whenever 'encoding' is set to GB18030, use UTF-8 internally and convert
when reading and writing, just like we already do for UTF-16le, UTF-16be,
UTF-32le and UTF-32be.
There is still another problem. When using gvim under Windoze with
CP936 locale, we can only set the encoding to CP936. Or the messages
in gvim will become malformed characters. Could anybody offer a good
solution to this problem?
This, of course, also suffers from the performance problems related to
conversion GB18030 <=> UTF-8.
Best regards,
Tony.
--
Love and scandal are the best sweeteners of tea.
Regards,
Edward Leap Fox
