[
https://issues.apache.org/jira/browse/MESOS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297085#comment-15297085
]
Whitney Sorenson commented on MESOS-2013:
-----------------------------------------
We have just deployed 0.28.1 and I can report, that yes, this does help our
case. Thank you. We have to do some processing ourselves to handle utf-8
characters which have been chopped, but it is something we can work around.
As a note, earlier, when I asked if we should find a competent C++ developer I
meant to imply someone besides myself - not that anyone else was incompetent ;)
> Slave read endpoint doesn't encode non-ascii characters correctly
> -----------------------------------------------------------------
>
> Key: MESOS-2013
> URL: https://issues.apache.org/jira/browse/MESOS-2013
> Project: Mesos
> Issue Type: Bug
> Components: json api
> Reporter: Whitney Sorenson
> Assignee: Anand Mazumdar
>
> Create a file in a sandbox with a non-ascii character, like this one:
> http://www.fileformat.info/info/unicode/char/2018/index.htm
> Hit the read endpoint for that file.
> The response will have something like:
> data: "\u00E2\u0080\u0098"
> It should actually be:
> data: "\u2018"
> If you put either into JSON.parse() in the browser you will see the first
> does not render correctly but the second does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
