To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=96826
------- Additional comments from [email protected] Thu Oct 15 13:42:04 +0000 2009 ------- Ok, doing it as a last level resort for glyph fallback looks like a reasonable first step. The resulting modal dialog may be annoying though e.g. when something with an invalid encoding is pasted resulting in gazillions of weird codepoints. Regarding RFEs for this feature I already have an idea: make FC interact with AFAMI directly. If an app asks for a font with support for a specific codepoint and FC does not find a good answer, it should ask AFAMI for help. IMHO it should be configurable whether FC does this asynchronously, synchronously (using a modal) dialog or if the feature is disabled, globally or application specific or as part of the font pattern. OOo already does the right thing when the equivalent of a WM_FONTCHANGED comes along. I would prefer it to be asynchronous by default. And having a patterns like FC_AUTOFONT_REQUIRED, FC_AUTOFONT_SUGGESTED, FC_AUTOFONT_MAYBE or FC_AUTOFONT_DONTCARE would help to distinguish important use cases such as idle formating or UI-text. IMHO most external observers overestimate the number of "OO.o people" working on stuff like this... --------------------------------------------------------------------- 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]
