[
https://issues.apache.org/jira/browse/FOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357932#comment-15357932
]
Simone Rondelli commented on FOP-1969:
--------------------------------------
Hi Glenn,
Thanks for replying. Let me ask a couple of more clarifications: regarding
these 2 options
# If I change the method signature using int instead of char (Eg. starting from
the Typeface interface) then lot of code will need to be changed. I can see
more than 20 direct/indirect subclasses which are used quite broadly in the
project. I'm fine in changing them all but I want to be sure that this is what
you (or the ApzcheFOP maintainers wants).
# Otherwise I can add overloaded methods at some point deeper in the hierarchy
in order to reduce the number of changed classes (most of them would not even
need to support code points since they are not meant to show such a big range
of characters). I think the right place were to put the overloaded methods
would be either MultiByteFont or CIDFont and then change accordingly the client
of the chosen class.
Could you tell me which approach do you think is the best for the Project?
As soon as I'll have a working version I'll create a fork and branch the
Project.
Thanks
Simone
> 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: 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.3.4#6332)
