You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Simone Rondelli (JIRA)" <ji...@apache.org> on 2016/07/28 15:38:20 UTC

[jira] [Comment Edited] (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&focusedCommentId=15397694#comment-15397694 ] 

Simone Rondelli edited comment on FOP-1969 at 7/28/16 3:37 PM:
---------------------------------------------------------------

Would it be a problem if I change the variable names? I found pretty hard to understand the flow with abbreviations and maybe it would help a bit future developers.


EG:

{code:java}
CharSequence  ncs = normalize(cs, associations); //normalizedCharSeq
GlyphSequence igs = mapCharsToGlyphs(ncs, associations); //glyphSeq
GlyphSequence ogs = gsub.substitute(igs, script, language); //substitutedGlyphSeq
{code}



was (Author: rondelli):
Would it be a problem if I change the variable names? I found pretty hard to understand the flow with abbreviations and maybe it would help a bit future developers.


EG:

{code:java}
CharSequence  ncs = normalize(cs, associations); //normalizeCharSeq
GlyphSequence igs = mapCharsToGlyphs(ncs, associations); //glyphSeq
GlyphSequence ogs = gsub.substitute(igs, script, language); //substitutedGlyphSeq
{code}


> 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)