[
https://issues.apache.org/jira/browse/FOP-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746851#comment-17746851
]
Dave Roxburgh commented on FOP-2918:
------------------------------------
Hi [~kwilkerson]
How closely related was this issue to
https://issues.apache.org/jira/browse/FOP-2920, reported 2 days later?
Do you know if fixing FOP-2920 also fixed this one?
Thanks
> [PATCH] Surrogate pairs not handled in U+10800-U+1083F
> ------------------------------------------------------
>
> Key: FOP-2918
> URL: https://issues.apache.org/jira/browse/FOP-2918
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
> Affects Versions: 2.4
> Environment: Windows 10
> Reporter: Jan Driesen
> Priority: Major
> Attachments: 2918.patch, NotoSansCypriot-Regular.ttf, fop.xconf,
> input.fo
>
>
> Fop is not properly handling surrogate pairs for characters in Unicode Block
> 'Cypriot Syllabary' when rendering PDF.
> It tries to resolve the individual surrogate entities. This results in errors
> saying the glyphs cannot be found.
> The attached test shows a font that supports characters in this range, and an
> FO file holding the surrogate characters to be rendered.
> Similar issues arise with fonts "MPH 2b Damas"
> ([https://fedoraproject.org/wiki/MPH_2B_Damase_fonts]) and "Segoe UI
> Historic"
> ([https://docs.microsoft.com/en-us/typography/font-list/segoe_ui_historic),]
> but the error may differ. [I am unsure whether licensing allows me to add
> these)
> Some fonts (Damas & Noto) result in a "String index out of range". Other
> fonts (Segoe) deliver a "ill-formed UTF-16 sequence, contains isolated high
> surrogate at end of sequence" FOPException.
> We expected this to work thanks to FOP-1969 (fop 2.3).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
