[
https://issues.apache.org/jira/browse/XALANJ-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819808#comment-17819808
]
Joe Kesselman commented on XALANJ-2730:
---------------------------------------
Copied from that previous work item:
{quote}ISSUE: Note that if a characters() call ending with a High Surrogate is
issued unintentionally, we don't currently detect the isolated High Surrogate
until the next characters() call, at which point the error indication (illegal
Numeric Character Entity for the surrogate) gets dumped in as the first
non-whitespace rather than appearing at the end of the characters() block it
belonged to. To do otherwise seems to require that all the other events check
`m_pendingUTF16HighSurrogate` and force it out before running their own logic.
Which we could do, but that's a lot of overhead for a rare error, even if the
test itself is a relatively cheap one.
{quote}
> Review handling of isolated UTF16 surrogate characters in serializer
> --------------------------------------------------------------------
>
> Key: XALANJ-2730
> URL: https://issues.apache.org/jira/browse/XALANJ-2730
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Reporter: Joe Kesselman
> Assignee: Gary D. Gregory
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
