Re: creating a test font w/ CJKV Extension B characters.

From: Frank Yung-Fong Tang (
Date: Thu Nov 20 2003 - 18:14:02 EST

  • Next message: Michael Everson: "Re: [OT] "Www" as an internet riddle"

    Michael (michka) Kaplan wrote:

    > From: "Frank Yung-Fong Tang" <>
    > > so.. in summary, how is your concusion about the quality of "GB18030"
    > > support on IE6/Win2K ? If you run the same test on Mozilla / Netscape
    > > 7.0, what is your conclusion about that quality of support?
    > In Summary?
    > Well, in summry, I fail to see how testing for NCRs has anything to do
    > with
    > suport of *any* encoding in a browser. It seems like an inadequate
    > test of
    > functionality of "gb18030" support.
    > If you want to test gb18030 support, then please encode a web page in
    > gb18030 and test *that* in the browser of your choice.

    Have you ever look at that page before you said this? or the html source
    of that page?
    Those page display 5 information [for BMP characters, less information
    is there] for each characters
    1. the GB18030 encoded value in hex. That hex value of the first two
    bytes are display on the top of the page for the plane 2 characters. The
    hex value of the thrid byte is display on the left of each row. The 4th
    byte is display on top of each column
    2. The 4 bytes of the characters encoded in GB18030
    3. The same characters encoded by using hex escape in html as &#xhhhhhhh;
    4. a <IMG> point to the image on
    5 The equvilant Unicode hex value is display as U+xxxx in the bottom

    Ideally, if the browser do thing right and the font is install, the one
    who want to test can compare 2, 3, and 4 to see what happen.
    Therefore, it could be used to test BOTH the NCR and GB18030.
    If 2 display different from 4 (assume the server is up and running and
    you do see the glyph in gif), then it mean the conveter have problem.
    If 3 display different from 4 (assume the gif can be view), then it mean
      your html parser have problem
    If 2 and 3 display different from 4, then it could be both have problem
    , the rendering engine itself have problem, or all of them have problem.

    Of course, you don't really need to <img> part, you can compare with the
    Unicode 4.0 standard by yourself. But my tool is written 1 year before I
    got my hardcopy of Unicode 4.0 standard so that image help us to QA.

    If you SAVE the page locally then look at the result, notice the "save"
    operation could already damange you page.

    And YES, I DO encode that page in GB18030 and use byte to encode. I did
    have ADDITIONAL information encoded in NCR and <img> there to help to
    verfication. You may missed the real GB18030 encoded characters there if
    you do not pay close attention.

    > Now if you want to discuss NCR support then that may also be interesting.
    > But it would be nice to have tests that actually cover what they claim to
    > cover....
    I do have actual claim about what it cover. And more than that. The
    problem is you look at the addition part which is beyond what I claim in
    the last email.

    > MichKa [MS]
    > NLS Collation/Locale/Keyboard Development
    > Globalization Infrastructure and Font Technologies

    Frank Yung-Fong Tang
    Šýštém Årçhîtéçt, Iñtërnâtiônàl Dèvélôpmeñt, AOL Intèrâçtívë Sërviçes
    AIM:yungfongta Tel:650-937-2913
    Yahoo! Msg: frankyungfongtan
    John 3:16 "For God so loved the world that he gave his one and only Son,
    that whoever believes in him shall not perish but have eternal life."
    Does your software display Thai language text correctly for Thailand users?
    -> Basic Conceptof Thai Language linked from Frank Tang's
    Iñtërnâtiônàlizætiøn Secrets
    Want to translate your English text to something Thailand users can
    understand ?
    -> Try English-to-Thai machine translation at

    This archive was generated by hypermail 2.1.5 : Thu Nov 20 2003 - 19:12:45 EST