No need for convert ISO 8859-1 characters to entities on UTF-8 output.

  • 2
  • Problem
  • Updated 6 years ago
See for an example.

It returns ä as & auml; and it is impossible for TTS readers to read.

As output is already UTF-8 entitys are useless.
Photo of Keijo Mukku

Keijo Mukku

  • 2 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 2
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
I see what you mean, we can see if there's anything we can do about it.
Photo of John Celenza

John Celenza

  • 40 Posts
  • 21 Reply Likes

Those entities are in our language translation strings. Maybe the best option for us would be to un-encode entities when rendering the response.

Let me see how hard this would be to do.

Thank you for pointing out the issue!
Photo of arclance


  • 29 Posts
  • 0 Reply Likes
This may also be a problem with alerts in the United States.
They are filled with unicode newlines (an sometimes other things) like this.

\u000AUse common sense...and be extra cautious in the heat of this\u000Aafternoon and early this evening.\u000A\u000ALimit strenuous activities
Photo of Keijo Mukku

Keijo Mukku

  • 2 Posts
  • 0 Reply Likes

It seems like you have cleaned some of the strings already? Also there seems to be line break tags on strings too.

I hope you can find a solution to fix these problems.

Thanks for all your help...really appreciated!