Using the APE server inlinepush, if I try and push a string containing
an accented character I get BAD_JSON back from the server, for
example:
http://ape.server:6969/?[{"cmd":"inlinepush","params":{"raw":"postmsg","data":{"dots":[{"name":"Café"}]},"password":"testpasswd","channel":"testchannel"}}]
[{"time":"1337987563","raw":"ERR","data":
{"code":"005","value":"BAD_JSON"}}]
change that to:
http://ape.server:6969/??[{"cmd":"inlinepush","params":{"raw":"postmsg","data":{"dots":[{"name":"Cafe"}]},"password":"testpasswd","channel":"testchannel"}}]
[{"time":"1337987858","raw":"pushed","data":{"value":"ok"}}]
and all is okay.
So the accented é in Café seems to be a problem even though it gets
encoded as Caf%C3%A9% by the browser before being pushed.
I've seen the discussion is this group "Does APE supports UNICODE?"
from Dec 2011 but wasn't clear from the description if this it the
same issue.
I downloaded and compiled the APE server from the GIT repository on
Fedeora 15 (Linux).