Does the server actually send a Content-Type header that contains the
correct encoding? e.g.:
Content-type: text/x-json; charset=utf8
Of course, you can always send unicode strings as escaped via JSON,
making them entirely ASCII safe.
-bob
On Dec 6, 2005, at 6:44 AM, Kevin Dangoor wrote:
Hmm... Safari does have a bug where it ignores the encodings of
XMLHttpRequests. TurboGears employs a workaround for Kid templates
but, now that I think about it, it may not use that workaround for
JSON output. Can you open a ticket in the TurboGears trac? I see no
reason to not implement the same trick for JSON output.
http://trac.turbogears.org
(AFAIK, there's nothing that can be done within MochiKit to work
around this because the data's already mangled when MochiKit gets its
hands on it.)
Kevin
On 12/6/05, Rune Hansen <[EMAIL PROTECTED]> wrote:
The norwegian characters "ר,ז,ו" are displayed raw in Safari using
json methods from turbogears:
"Lillestrרm" is "Lillestrøm" (Firefox OSX/WIN, IE WIN shows it
correctly as "ר").
Is this a Safari bug?
regards
/rune
--
Kevin Dangoor
Author of the Zesty News RSS newsreader
email: [EMAIL PROTECTED]
company: http://www.BlazingThings.com
blog: http://www.BlueSkyOnMars.com
