Comment #5 on issue 6425 by [email protected]: Make UniscribeStateTextRun::nextWinFontData work with SegmentedFontData http://code.google.com/p/chromium/issues/detail?id=6425
dglazkov, Even though I have quickly read UniscribeHelperTextRun::nextWinFontData() today, I'm a little wondering whether or not I understand this problem correctly. As you know, this function is called from UniscribeHelper::shape() to retrieve a font that can render the given text run. If the unicode-range property of a font covers all characters in the text run. It does not cause any problems. On the other hand, I'm wondering how we should handle the case when the unicode-range property of a font doesn't cover all characters in the text run. For example, when a text run consists of ASCII characters and Cyrillic ones. Nevertheless, the unicode-range property of a font only supports ASCII characters. For this case, I assume UniscribeHelperTextRun::nextWinFontData() should not return this font because it doesn't make much sense to return a font that causes an error in calling ScriptShape(). But there is another option that splits this text run into two (or more) sub-runs: some consist only of ASCII characters and the others consist only of Cyrillic characters. Even though this option may yield better results, I'm wondering if it is easy to implement this option. Would it be possible to give me your opinions? Regards, -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
