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 h...@openoffice.org Thu Oct 15 14:07:00 +0000 2009 ------- > I'd hoped to pick up this myself by F-12, I might try again to do this myself > by F-13 Thanks! I still think you should concentrate on a FC<->AFAMI interaction and then making sure that apps such OOo gets notified when they succeeded in installing new fonts. OOo will happily reformat then. Having FC negotiate with AFAMI would have so many benefits... as I already said in #desc5 FC has the full picture of what is going on, what is missing etc. And as a central configuration entity for font-related questions it will better know the relationships between different fonts, where to get them directly, where to get nice substitutions. Managing the font autoinstallation from a module other than FC just calls for trouble, useless extra work, annoying modal dialogs, etc. --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
