[ https://issues.apache.org/jira/browse/FOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas L. Delmelle updated FOP-2540: ------------------------------------- Attachment: FOP-2540.patch Updated patch. As I was browsing through the OpenFont class, started doing some more code cleanups, i.e. removal of unnecessary (un)boxing, simplification of if-statements, for-loops converted to foreach, etc. One particular absurdity worth mentioning is probably the private method unicodeToWinAnsi(). As far as I can tell, since that method gets passed a single int, and searches a char array for a matching value, it could never ever return an array with more than one element, so removed that overhead and made it return a single int instead... Not sure why it was equipped to build up a List of Integers, where a simple int would do. > Enhance TTF/OTF support beyond Windows > -------------------------------------- > > Key: FOP-2540 > URL: https://issues.apache.org/jira/browse/FOP-2540 > Project: FOP > Issue Type: Improvement > Components: font/opentype > Affects Versions: 2.0 > Environment: OS X > Reporter: Andreas L. Delmelle > Assignee: Andreas L. Delmelle > Priority: Minor > Attachments: FOP-2540.patch, test_osx_fonts_after_1.log, > test_osx_fonts_before.log > > > Currently, cmap tables in TTF/OTF are only supported for Platform ID = 3, > i.e. MS Windows. There is no support for Platform ID = 0, i.e. basic Unicode, > or 1, i.e. Macintosh. > This makes quite some system fonts bundled with OS X supposedly unusable. The > solution is fairly trivial (patch proposal will be attached shortly), > provided the cmap table format in the font is already supported. FOP > currently only has support for cmap format 4 (segment to delta mapping), but > this seems to suffice for most of the Unicode cmaps as well. > See also FOP-2539, which triggered me to investigate this closer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)