Hi, Ivan. Thank you for your clear explanation, and thanks to James as well.
I googled for "big5-E0" for some documents on this encoding method, but get nothing helpful. As my intention is to understand how the wheel is rolling, so let's leave big5 stuff behind. I'm not so sure about the actual meaning of the following: > never into cs2/cs3 charsets. (Frankly speaking the wc_encoding values are > actually wrong in that locale description. And if one tries to convert CTEXT > into WC directly and then draw that WC string it will fail, really. But it's > a bug. With MB or UTF8 strings it should not happen.) > 1. What do you mean "wc_encoding values are wrong"? 2. WC means the internal WC format(with wc_encoding bit etc.) here, not the stdc WC, which is UCS4 actually. Am I right? 3. You have that conclusion for some operating test, or reading from source code? As I comprehend, if CTEXT convert to WC directly, then the WC string remain the original charset information, which may be cs2/cs3. This will cause the failure in drawing text. Am I right? Xie Qian Open System and Chinese Information Processing Center, Institute of Software, Chinese Academy of Sciences, P.O. Box 8718, Beijing 100080, CHINA _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
