[ https://issues.apache.org/jira/browse/FOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085182#comment-14085182 ]
Gaja Sutra commented on FOP-1969: --------------------------------- (In reply to comment #3) > > request to fix this to support surrogate pairs characters. I'm interested too, by this feature. > thanks for your request; could you provide additional information: > 1. what specific non-BMP characters you would like to use? Alchemical Symbols, by example: 1F701 -> 1F704 > 2. what specific fonts will you use for these characters? Symbola font by example. http://users.teilar.gr/~g1951d/ Thanks, Gaja. > 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 > Assignee: Glenn Adams > Attachments: testing.fo, testing.fo, testing.pdf, testing.pdf, > testing.xml, testing.xsl > > > 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.2#6252)