You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "simon steiner (JIRA)" <ji...@apache.org> on 2018/03/19 08:52:00 UTC

[jira] [Updated] (FOP-1969) Support for unicode Surrogate pairs

     [ https://issues.apache.org/jira/browse/FOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

simon steiner updated FOP-1969:
-------------------------------
    Summary: Support for unicode Surrogate pairs  (was: Surrogate pairs not treated as single unicode codepoint for display purposes)

> Support for unicode Surrogate pairs
> -----------------------------------
>
>                 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
>            Assignee: simon steiner
>         Attachments: AndroidEmoji.ttf, Urdu.zip, fop.xconf, pcltest.zip, single-byte.zip, test.fo, 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;
>  
> fop test.fo -c fop.xconf out.pdf
> Glyphs should be rendered



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)