Actually fonts on Windows are normally Unicode based (including MS
Mincho and MS Gothic) and most have in addition some codepage access. So
there is neither a perf hit nor a codepage problem in using such fonts
on NT, Win2000 and WinXP. These considerations are orthogonal to
OpenType.
 
Murray

        -----Original Message----- 
        From: Richard, Francois M 
        Sent: Wed 2001/08/01 05:40 
        To: [EMAIL PROTECTED]; [EMAIL PROTECTED] 
        Cc: 
        Subject: Unicode/font questions.
        
        

        Since Win2000 and NT are native Unicode, is it true to say that
any use of a
        non-Unicode font (in fact most of the fonts on Windows. And in
particular
        Asian font like MS Mincho, MS Gothic) in a Unicode application
will generate
        a conversion WideCharToMultibyte (to convert the Unicode text to
the
        specific font codepage)?
        Is this a big performance hit?
        Can this create mapping issues (e.g. Unicode <-> Chinese
character
        encoding)?
        Are we sure that if a font is installed on a machine, then the
appropriate
        codepage is going to be available too (for the conversion)?
        
        What about "extending" current non-Unicode font to support
Unicode? Like a
        "MS Mincho Unicode"... It would still be specialized/dedicated
to Asian
        glyphs, but by using Unicode character encoding, it would not
require the
        WideCharToMultibyte conversion...
        
        Is Open TrueType related to this?
        
        François
        
        
        


Reply via email to