[gsl-issues] [Issue 102911] kerning fails for DejaVu Serif on Windows
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102911 --- Additional comments from h...@openoffice.org Mon Nov 9 08:04:49 + 2009 --- Fontforge itself now warns about the problematic fonts: See http://thread.gmane.org/gmane.comp.fonts.fontforge.devel/6359/focus=640 and http://fontforge.cvs.sourceforge.net/viewvc/fontforge/fontforge/fontforge/tottfaat.c? r1=1.41r2=1.42 and with a message people can actually understand I'm not a native speaker so I apologize that I just came up with this message Kerning is likely to fail on Windows On Windows many apps will have problems with this font's kerning, because %d of its glyph kern pairs cannot be mapped to unicode-BMP kern pairs Suggestions on a new wording that make the problem much clearer are very welcome. - 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...@gsl.openoffice.org For additional commands, e-mail: issues-h...@gsl.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[gsl-issues] [Issue 102911] kerning fails for DejaVu Serif on Windows
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102911 --- Additional comments from nmail...@openoffice.org Sat Nov 7 13:35:22 + 2009 --- @hdu: when OO.o cares about something in fonts *please make sure it is detected by fontforge's fontlint* (and with a message people can actually understand) There are thousands of ways fonts can differ, some of them are detected but do not matter because apps learned how to workaround them, others do matter but are not detected (or hidden behind black vodoo messages) If you don't give people the means to detect problems that affect OO.o, you'll continue to get fed problem fonts - 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...@gsl.openoffice.org For additional commands, e-mail: issues-h...@gsl.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[gsl-issues] [Issue 102911] kerning fails for DejaVu Serif on Windows
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102911 User mechtilde changed the following: What|Old value |New value Status|RESOLVED |CLOSED --- Additional comments from mechti...@openoffice.org Sun Jul 12 17:52:33 + 2009 --- invalid - closed - 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...@gsl.openoffice.org For additional commands, e-mail: issues-h...@gsl.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[gsl-issues] [Issue 102911] kerning fails for DejaVu Serif on Windows
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102911 User hdu changed the following: What|Old value |New value OtherIssuesDependingOnTh| |103157 is| | Status|STARTED |RESOLVED Resolution| |INVALID Summary|DejaVu font without kernin|kerning fails for DejaVu |g on Windows |Serif on Windows --- Additional comments from h...@openoffice.org Wed Jul 1 06:50:05 + 2009 --- Every windows application that relies on the GDI call GetKerningPairs() will fail with these problematic fonts. On the other hand the font's kern table is valid and OOo is right that it trusts GDI to provide the kerning pairs. There are four ways to fix it: 1. fix Windows so that GetKerningPairs() ignores pairs it cannot handle 2. remove the problematic kernings from the DejaVu Serif fonts 3. make sure that every glyph mentioned in the kern table has a (proper or dummy) unicode inside the baseplane 4. make OOo and all other Windows applications avoid GDI calls and parse all font tables themselves Fixing the problematic fonts seems to be the best way. To identify them I sent a patch for fontforge which warns when such a problematic font is being generated. The mail should show up in http://sourceforge.net/mailarchive/forum.php?forum_name=fontforge- develmax_rows=25style=ultimateviewmonth=200907 soon. - 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...@gsl.openoffice.org For additional commands, e-mail: issues-h...@gsl.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
