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] Fri Jun 19 14:28:23 +0000 2009 ------- Applied in CWS gfb4win02 with a minor fixes to prevent a side effect: the availability of the unicodemap currently also means that all the interesting details from the matching HDC are known, so we should use UpdateFromHDC() instead of calling directly ReadCmapTable() I also added a big TODO: we are currently checking if the font face can resolve all missing codepoints. This approach is is problematic for some corner cases, e.g. - user types some text that can be resolved by fontA - user types another character that cannot be resolved by fontA but only by fontB => then the whole text switches from fontA to fontB, linebreaking changes etc. This scenario is already bad enough, but it starts to get really hairy when fontB cannot resolve all other codepoints And then used FindBestFontFace() instead of iterating over the font faces manually. This not only helps with finding a better stylistic match but it also avoids leaking WinGlyphFallbackSubstititution into one of the central header files of the platform-independent part of vcl. --------------------------------------------------------------------- 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]
