[ros-bugs] [Bug 894] ROS Win32k doesnt support FON or SBIT data from FreeType

[ReactOS.Bugzilla at reactos.org]

http://www.reactos.org/bugzilla/show_bug.cgi?id=894





------- Additional Comments From wierd_w at yahoo.com  2005-10-12 18:06 CET -------
Many 'difficult' typefaces, like those in the arabic and CJK unicode ranges 
rely heavily on SBIT data for low point sizes, because of the problems with 
scaling those glyphs.

These fonts were kinda the reason why they put support for bitmapped data 
inside otherwise 'outline' fonts.   The bitmaps stored in the SBIT section of 
the glyph data is what gets displayed on screen, while the outline vector is 
what gets rendered when the font is printed out-- Best of both worlds; The 
benefit of TTF over .FON or .BDF, or other bitmap only fonts, is the WYSIWYG 
aspect of printing them out, not being "outline only" on screen, so SBIT data 
doesnt in any way detract from what "TTF" 'is'.

I have come to understand that people in the RosTranslation arena have been 
attempting to do a translation that uses the CJK range, and have been suffering 
the ill effects of the "Win32k doesnt know how to handle FONS" and "Win32k 
doesnt know how to handle SBITs" bugs.

This little blurb was given for their benefit.

-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.