[
https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348396#comment-14348396
]
ASF subversion and git services commented on PROTON-834:
--------------------------------------------------------
Commit c65e89730f67cd3a8aa31c0d0de491b20810c99f in qpid-proton's branch
refs/heads/master from [~dnwe]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=c65e897 ]
PROTON-834: modified UTF-8 encoder fixes
Commit 5069bb6 applied a modified version of a patch I submitted, to
ensure that the UTF-8 encoder (and UTF-8 byte length calculator) would
cope with surrogate pairs. This commit fixes an issue with three byte
characters in the <= 0xFFFF range being incorrectly detected as invalid
four byte surrogates.
Closes #10
> proton-j: UTF-8 encoder reporting some three byte characters as invalid
> surrogates
> ----------------------------------------------------------------------------------
>
> Key: PROTON-834
> URL: https://issues.apache.org/jira/browse/PROTON-834
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.8
> Reporter: Dominic Evans
> Fix For: 0.9
>
>
> Following on from the fixes made under PROTON-576, some UTF-8 characters were
> getting incorrectly reported as invalid surrogates, when they were valid
> 3-byte encodings.
> e.g.,
> ！！！
> (╯°□°)╯︵ ┻━┻
> etc.
> This is an issue when streaming variable content such as Twitter messages
> which can often contain such characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
