Re: glyph selection for Unicode in browsers

From: Tex Texin (tex@i18nguy.com)
Date: Thu Sep 26 2002 - 13:52:13 EDT

  • Next message: RJR: "OCR-B Standard Point & Pitch Size"

    Markus,

    Yes, underlying fonts can be a Unicode architecture. That's a good
    thing, but invisible to end-users.
    I would like to keep the sense of "Unicode font" as meaning a font which
    supports a large number of scripts, rather than meaning one that uses
    Unicode for its mapping architecture.

    Yes, OS and browsers are getting better. My concerns center around:
    Is the mechanism for selecting fallback fonts language-sensitive, so
    that it would favor a Japanese font for Unicode Han characters that were
    tagged as lang:ja And are the fonts labeled so that the supported
    language is known?

    Even so, I'd still need to have a large collection of fonts then.

    I would like to be able to publish a page such as the Unicode example
    page:
    http://www.i18nguy.com/unicode-example.html

    without feeling obligated to publish a pdf version
    http://www.i18nguy.com/unicode/unicodeexample.pdf

    so that the less technical among us would not feel challenged to acquire
    and install several fonts, language by language.

    And my main point is that my investment in tagging text segments with
    "lang" should result in the most appropriate rendering.
    Currently, using a Unicode font, lang has no visible effect.

    tex

    Markus Scherer wrote:
    >
    > Tex Texin wrote:
    >
    > > However, a Japanese user might have to choose a Japanese font, if the
    > > Unicode font does not favor (and cannot be made to favor with language
    > > tags) Japanese renderings.
    > > So it's catch 22. They have native fonts because Unicode fonts are
    > > inadequate, but we can be relieved that although Unicode fonts are
    > > inadequate, we are lucky the users don't use them.
    >
    > I am not sure this is as bad as it may sound:
    > Modern "native fonts" use Unicode cmaps (mapping tables from _Unicode text_ to glyph IDs) instead of SJIS/whatever cmaps.
    > They will just not contain entries for much else but "native" characters.
    >
    > In that sense, those native fonts will also be "Unicode fonts".
    > Operating systems and browsers are also getting better at automatically selecting fallback fonts for characters that are missing in the main font.
    >
    > markus

    -- 
    -------------------------------------------------------------
    Tex Texin   cell: +1 781 789 1898   mailto:Tex@XenCraft.com
    Xen Master                          http://www.i18nGuy.com
                             
    XenCraft		            http://www.XenCraft.com
    Making e-Business Work Around the World
    -------------------------------------------------------------
    


    This archive was generated by hypermail 2.1.5 : Thu Sep 26 2002 - 14:25:45 EDT