[ https://issues.apache.org/jira/browse/FOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386651#comment-16386651 ]
Kelly H Wilkerson commented on FOP-1969: ---------------------------------------- I wanted to chime in that I've been using Simone's surrogate-pairs patch in production software (for converting text message data to PDF) for a few months now, and have been really happy with it. Are there plans to include it? (An optimistic side-note: This past weekend I merged the current FOP 2.3 trunk into a clone of Simone's surrogate-pairs work just to make there wasn't too much divergence, and it was surprisingly not too painful :)) If there is anything I can do to help with the effort, I'm more than happy to contribute. > 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 (v7.6.3#76005)