To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113195
User hdu changed the following:
What |Old value |New value
================================================================================
Target milestone|OOo 3.4 |OOo 3.x
--------------------------------------------------------------------------------
------- Additional comments from h...@openoffice.org Fri Jul 16 13:44:37 +0000
2010 -------
The important question is whether the app+doc has some texts where a
builtin-font candidate is selected
and the base14-coverage does not suffice. We already know that the builtin
fonts do not cover anything
beyond their ansi-only codepoints.
And even when they are covered there are interesting scenarios what to do with
combinations such a 'A'
with U+0306 (breve). Should the 'A' come from the builtin-font and the Breve
from its system-font
counterpart? The system-font suggests a ligature and updates the positioning,
as it knows the detailsfrom
its "morx" table. When there are such gray areas of course the best solution is
to always trust the system
font, which is what we do now.
---------------------------------------------------------------------
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
