|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Deprecated SEAC operator is not supported in PS-OTF | ||||||
|---|---|---|---|---|---|---|---|
| Product: | gsl | Reporter: | hdu <hdu> | ||||
| Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
| Status: | ACCEPTED --- | QA Contact: | |||||
| Severity: | Trivial | ||||||
| Priority: | P4 | CC: | fonts-bugs, issues, sven | ||||
| Version: | OOO320m8 | ||||||
| Target Milestone: | AOO PleaseHelp | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- | ||||
| Developer Difficulty: | --- | ||||||
| Issue Depends on: | 43029 | ||||||
| Issue Blocks: | |||||||
| Attachments: |
|
||||||
Also see http://blogs.adobe.com/typblography/2007/05/typotechnica_2007.html : "Developers asked about the need for decomposing SEAC glyphs. SEAC is an old and very limited composite glyph mechanism from the Type 1 format. It only works if both the accent and the base character are in Adobe StandardEncoding. SEAC has been deprecated in CFF and OpenType, and is not well supported in all enivronments today. If using FontLab, go to the preferences for "Generating OpenType PS (.otf)" and make sure the option to "Decompose all composites" is on." Is this something fontlint warns about? If not could you contribute a test to fontlint so font distributors can test for this pattern? I'm not sure whether fontlint already warns about this yet, but the related fontforge project is already
aware of the problem as the quick grep over the source shows
fontforge/splinesave.c:/* Type2 doesn't allow any seacs */
What is meant here are the Type2 charstrings and these are used in about every PS-OTF-font out there to
define the glyph outlines.
If fontlint doesn't warn about it yet doing so would be a good idea.
Also see http://partners.adobe.com/public/developer/opentype/index_composite.html : "In the CFF/Type 2 charstring format, the seac operator is not supported." The priority of this issue depends on the importance of the fonts that have this problem. I do not expect them to be plentyful since if they were important enough to be maintained they would not use illegal operators. Anyway, here is the start of the list: - "Yanone Kaffeesatz" - older versions of "FreeFontPro" Correction: current versions of "Yanone Kaffeesatz" use only non-deprecated operators. Thanks Jan! - ZapfinoPro is affected (http://www.ntg.nl/pipermail/ntg-context/2009/045689.html) Created attachment 66865 [details]
patch for fontforge/fontlint to warn about depreciated SEAC-like operator in Type2
Additional Font: FrutigerNextLT (some chars: ä ö „ “). Upstream fontlint now has applied the suggested patch (and some other nice checks): http://fontforge.cvs.sourceforge.net/viewvc/fontforge/fontforge/fontforge/psread.c?r1=1.83&r2=1.84 Thanks Kevin for suggesting it. AFAIK no fonts provided by the distributions were affected. The change will hopefully prevent them from ever getting new fonts with the old problem. Reset assigne to the default "issues@openoffice.apache.org". |
The Type1 SEAC-Operator ("Standard Encoding Accented Character") is very limited and compared to subrs it only has drawbacks. So it always was deprecated for CFF and PS-OpenType fonts. Still there are some fonts that were converted 1:1 from their Type1 counterparts which didn't decompose the SEAC operator into two subr calls. These fonts should get properly converted. If there are still some important fonts which use SEAC for their accented glyphs in the StandardEncoding then adding support for this obsolete feature should be considered.