To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54780
User us changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |WONTFIX
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Sep 22 02:51:31 -0700
2005 -------
Not in haste and I didn't closed it either. I set to 'invalid' and the tool
automatically sets the issue to 'resolved'.
> The problem is with AnnaCTT font
I very well understood this. But again non-UNICODE fonts are not supported and
never will be.
> BTW. This issue makes impossuble for users to use their (big) custom font
> collections
I'm aware of this. But these kind of legacy fonts cause more than headaches and
simply are inappropriate in the age of UNICODE.
Legacy/non-UNICODE fonts typically map their glyphs into the range of latin
glyphs but at the correct UNICODE defined positions they are blank. Hence it's
correct that OO.o performs a GlyphFallback for these positions.
As this issue turns against the GlyphFallback feature in the description (which
is essential for OO.o) I set to 'invalid'.
---------------------------------------------------------------------
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]
