[jira] [Commented] (FOP-1969) Surrogate pairs not treated as single unicode codepoint for display purposes

[ https://issues.apache.org/jira/browse/FOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175872#comment-15175872 ] Vinesh Kumar commented on FOP-1969: --- Hi Glenn, We are using FOP 2.0 and looking for non-BMP characters

Re: [jira] [Commented] (FOP-1969) Surrogate pairs not treated as single unicode codepoint for display purposes

On Wed, Mar 2, 2016 at 9:24 AM, Vinesh Kumar (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/FOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175872#comment-15175872 > ] > > Vinesh Kumar commented on FOP-1969: >

[jira] [Updated] (FOP-1969) Surrogate pairs not treated as single unicode codepoint for display purposes

[ https://issues.apache.org/jira/browse/FOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-1969: - Assignee: (was: Glenn Adams) > Surrogate pairs not treated as single unicode codepoint for display

[jira] [Commented] (FOP-2460) Subsetting OTF font leads to PDF errors when viewing / incorrect characters

[ https://issues.apache.org/jira/browse/FOP-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176838#comment-15176838 ] chunlinyao commented on FOP-2460: - [~rmeyer] can you confirm is this issue resolved by a patch in FOP-2557