[
https://issues.apache.org/jira/browse/FOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030873#comment-15030873
]
Andreas L. Delmelle commented on FOP-2540:
------------------------------------------
EDIT - Note that the Macintosh/Roman cmap is currently processed as if it were
a "symbol" cmap. This still needs to be revisited, I think. I have only done it
that way now, since otherwise, the Macintosh/Roman cmap in the "Symbol" font
would be processed before the Unicode/Unicode 2.0 cmap (i.e. the former appears
before the latter in the font file), which would then leave the actual symbol
codepoints unmapped... :(
> 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)
