|
| Iniciado por guest, 27,jul. 2017 12:17 - 4 respuestas |
| |
| | | |
|
| |
| Publicado el 27,julio 2017 - 12:17 |
Hi All
I have a weird issue. If a client includes the ">" character in a notification Android apps display it as "\x3E". Does anyone know how to resolve this?
Cheers
André |
| |
| |
| | | |
|
| | |
| |
| Publicado el 27,julio 2017 - 14:20 |
Hi
a google search says that \x3E is an UTF8 escape sequence.
That makes me thing that you are sending your notifications from
somewhere in ANSI, and as Android works in unicode, you have characters
translations problem that will be solved if you send your notification
in either unicode or utf8 directly.
Best regards
--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting
Ready for you: WXShowroom.com, WXReplication (open source) and now WXEDM
(open source)
More information on http://www.fabriceharari.com
Le 7/27/2017 à 4:17 AM, "ÿÿÿÿÿÿÿÿÿÿÿÿ" a écrit :
Hi All
I have a weird issue. If a client includes the ">" character in a
notification Android apps display it as "\x3E". Does anyone know how to
resolve this?
Cheers
André |
| |
| |
| | | |
|
| | |
| |
| Publicado el 27,julio 2017 - 14:26 |
Hi
a google search says that \x3E is an UTF8 escape sequence.
That makes me thing that you are sending your notifications from somewhere in ANSI, and as Android works in unicode, you have characters translations problem that will be solved if you send your notification in either unicode or utf8 directly.
Best regards |
| |
| |
| | | |
|
| | |
| |
| Publicado el 27,julio 2017 - 15:49 |
Hi Fabrice
I saw that. Will check how I am sending the data.
Cheers
André |
| |
| |
| | | |
|
| | |
| |
| Publicado el 27,julio 2017 - 18:58 |
Well, I give up - I have tried AnsiToUnicode and StringToUTF8 and still does not work. How do I pass an ANSI string to Android Push notifications? How do I change it to the format that Android requires?
Hope someone has managed to do this. |
| |
| |
| | | |
|
| | | | |
| | |
|