xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Markovskyi (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FOP-2540) [PATCH] Enhance TTF/OTF support beyond Windows
Date Mon, 22 Jun 2020 19:54:00 GMT

    [ https://issues.apache.org/jira/browse/FOP-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142377#comment-17142377

Eugene Markovskyi commented on FOP-2540:

[~adelmelle] thank you for the research and proposal. It is a pity that the changes are still
not merged. I am trying to patch the current FOP version to support fonts with Platform ID
= 0 Unicode encoding. I added a small change - it is just reading Platform ID = 0 encoding
if others (Platform ID = 3) are not provided. Tests show that FOP uses such encoding correctly.
As I see your patch contains much more changes.  I tend to think that I was too optimistic
when I was applying such simple patch. But I assume your patch implemented supporting of non
unicode encodings also. Could you please give me a hint what changes from your patch should
be applied to support only Unicode(Platform ID = 0) encoding? Thanks in advance.

> [PATCH] 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

View raw message