[ 
https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512662#comment-14512662
 ] 

ASF subversion and git services commented on PROTON-834:
--------------------------------------------------------

Commit 810088b14dedcd12a9474687ba9cd05fc8297188 in qpid-proton's branch 
refs/heads/0.9.x from [~dnwe]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=810088b ]

PROTON-834: further UTF-8 encoder fixes

After commit c65e897 it turned out there were still some issues with
strings containing a codepoint >0xDBFF which was being incorrectly
treated as a surrogate pair in the calculateUTF8Length method.

Fixed this up and added some more test coverage.

Closes #13

(cherry picked from commit 7b9b516d445ab9e86a0313709c77218d901435b1)


> 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
>            Assignee: Dominic Evans
>
> 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)

Reply via email to