-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not really a Prototype problem, but given the fact its approach is to
use this (in)famous "X-JSON" HTTP header, I wonder how (if any) you
succeeded to pass on Unicode data without encoding it to UCS.
At first sight it looks like a Gecko problem, but nevertheless, I'm
still curious of other workarounds besides this clumsy UCS encoding.
Gecko seems to parse headers properly (NSPR nsHttp debugging), but
something "in the middle" (on the way to JavaScript) messes all the data
(testes with LiveHTTPHeaders, firebug & XMLHttpRequest).
For instance:
JSON: {"a":"ß","b":"ç" }
response:
X-JSON: {"a":"Ã","b":"ç"}
X-JSON-UCS: {"a":"\u00df","b":"\u00e7"}
("X-JSON" is obviously the erroneously parsed one)
TIA
- --
Marius Feraru
-----BEGIN PGP SIGNATURE-----
iD8DBQFFEC0ptZHp/AYZiNkRAnGwAJ0UKDjtzWh4YuZGD4BBC9Z51ekmtwCgmNEL
6kF43MFUYJNiC16rOGHjIO8=
=wxWz
-----END PGP SIGNATURE-----
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
