RE: more dingbats in plain text

From: Peter Constable (petercon@microsoft.com)
Date: Sun Apr 19 2009 - 18:32:55 CDT

  • Next message: William J Poser: "Re: Handling of Surrogates"

    I tried it and couldn't get it working. I guess something must have changed in GDI. Honestly, this worked in Win98. Bob Hallissy and I did that experiment together, and he can corroborate those results.

    Peter

    -----Original Message-----
    From: Andrew West [mailto:andrewcwest@gmail.com]
    Sent: Sunday, April 19, 2009 6:56 AM
    To: Peter Constable
    Cc: Unicode Mailing List
    Subject: Re: more dingbats in plain text

    2009/4/19 Peter Constable <petercon@microsoft.com>:
    >
    >> whereby [Windows] adds an extra mapping layer from F020..F0FF in the font to
    >> ASCII codepoints if the font has a symbol encoding.
    >
    > Not 100% true. GDI will map *some range* to ASCII code points based on the code points used in the font. (At least, it worked this way back in Win98; I haven't checked this since but I really doubt it has changed.) You can construct a font with a format 4 cmap set to platform ID 3, encoding ID 0 but with code points ranging from, say, E020..E0FF, and GDI will map "J" to E04A.

    Perhaps you can try that. I just modified wingdings so that the glyphs
    for F04A..F04C map to E0FA..E0FC, and I can't get WordPad to display
    anything in the new font, either in the ASCII or PUA range. Certainly
    I would be very surprised if what you said about Windows mapping any
    range to ASCII was true. I am sure that it must be a fixed range of
    characters in the PUA.

    Andrew



    This archive was generated by hypermail 2.1.5 : Sun Apr 19 2009 - 18:37:17 CDT