Just to be sure we are on the same page, we can't commit arbitrary font
resources to our repository, even for testing purposes, unless we determine
their compatibility with ASF license requirements.

On Tue, Sep 20, 2016 at 4:07 AM, simon steiner (JIRA) <j...@apache.org>
wrote:

>
>      [ https://issues.apache.org/jira/browse/FOP-1969?page=com.
> atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> simon steiner updated FOP-1969:
> -------------------------------
>     Attachment: tiffttc.zip
>
> tiffttc.zip needs cambria.ttc
>
> > Surrogate pairs not treated as single unicode codepoint for display
> purposes
> > ------------------------------------------------------------
> ----------------
> >
> >                 Key: FOP-1969
> >                 URL: https://issues.apache.org/jira/browse/FOP-1969
> >             Project: FOP
> >          Issue Type: Improvement
> >          Components: unqualified
> >    Affects Versions: trunk
> >         Environment: Operating System: All
> > Platform: All
> >            Reporter: Glenn Adams
> >         Attachments: Urdu.zip, pcltest.zip, single-byte.zip, testing.fo,
> testing.fo, testing.pdf, testing.pdf, testing.xml, testing.xsl,
> tiffttc.zip
> >
> >
> > unicode codepoints outside of the BMP (base multilingual plane), i.e.,
> whose scalar value is greater than 0xFFFF (65535), are coded as UTF-16
> surrogate pairs in Java strings, which pair should be treated as a single
> codepoint for the purpose of mapping to a glyph in a font (that supports
> extra-BMP mappings);
> > at present, FOP does not correctly handle this case in simple (non
> complex script) rendering paths;
> > furthermore, though some support has been added to handle this in the
> complex script rendering path, it has not yet been tested, so is not
> necessarily working there either;
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Reply via email to