To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73803 Issue #|73803 Summary|Some fonts are incorrectly interpreted as CJK-capable Component|gsl Version|OOo 2.1 Platform|All URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|pl Reported by|akrioukov
------- Additional comments from [EMAIL PROTECTED] Tue Jan 23 10:26:07 -0800 2007 ------- I noticed that OOo 2 incorrectly calculates default interline space for text formatted with some fonts, thus making the text layout too loose. One such font is Cardo, downloadable from http://scholarsfonts.net/cardofnt.html. A possible workaround is to disable the "No External Leading" flag in OOo options, and yet the problem looks irritating. Since experimenting with OS/2 and hhea vertical metrics produced no result, I attempted to have a look at the code and noticed that additional spacing is applied to fonts which OOo considers CJK-capable. This CJK capability is determined (in vcl/source/glyphs/gcach_ftyp.cxx) by applying the 10111111111111000000000000 (hex 0x2fff0000) bit mask to the UnicodeRange2 OS/2 field. To my mind, 2 bits in this mask are actually not needed and should be reset to zero. Here the rationale: -- the bit 48 is for the CJK Symbols And Punctuation range. This range may well be partially supported in Western fonts, as some characters from it (in particular white square brackets U+301A and U+301B) have been traditionally used also for non-CJK texts. Such a usage may be considered deprecated now, and yet fonts should support those characters for backwards compatibility. On the other hand, this range is relatively small, and supporting it by itself obviously doesn't make a font really CJK capable; -- the bit 57 has nothing to do at all with CJK, as it just means that the font contains at least one Unicode SMP character. >From these 2 bits the second one is more important, as it is impossible to >clean it in the font file without making all characters beyond the Unicode BMP unaccessible. So I propose to change the bit mask to 101101111111100000000000000000 (hex 0x2DFE0000). A simple patch is attached. --------------------------------------------------------------------- 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]
