To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=101552





------- Additional comments from [email protected] Mon May 25 12:08:30 +0000 
2009 -------
@yanminjia: it works and that is a good start!
Here are some more hints:
1. each SalGetSubstituteFontProcExW step leaks an ImplWinFontData item
2. these ImplWinFontData items are already known in the ImplDevFontList
3. these ImplWinFontData items probably have their ImplFontCharMap already 
cached, so setting the 
font and getting the coverage over and over can be avoided
4. since the set of fonts on the system is mostly constant the expensive 
enumeration loop to determine 
the glyph coverage can be avoided for most of the fallbacks after the first one
5. for glyph-fallback we want to make sure that the fallback glyphs are valid. 
Some fonts claim 
coverage for a glyph, but provide empty ones or ones that look like the notdef 
glyph. Unless the font is 
known to be good an additonal check is probably needed.
6. the style of the fallback glyph should try to match the style of the font 
originally requested. E.g. the 
fallback for a bold oblique glyph should be bold oblique too if possible
... more later

So there is a lot of work ahead of us to get this done properly.
For the urgent problem you mentioned (non-BMP CJK glyphs) there is an easy 
workaround that gives us 
time: we should find out which fonts were used to resolve the urgent 
problematic cases; then add these 
fontnames to the aGlyphFallbackList[] list in vcl/source/gdi/outdev3.cxx

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to