Stefano Mazzocchi wrote: ...
On the other hand, by placing
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
the server creates an HTTP header that instructs the user-agent about the encoding. This solved the encoding problem on *all* browsers.
Why not simply patch the serializer to set proper content-type header?
D'oh! You're soooooo right. :))
I'll put it on my impossibly long todo list.
S.
