I have an edit-in-place plugin I've created for my employer. We *need* to use iso-8859-1*
I understand we can set the *response* to be in iso-8859-1 in ajax, but I also need the request to be, so that it's posted properly to our database. So, I'm posting with jsonp, and then getting the updated content via ajax. Two requests is sloppy, but the amount of network strain we'll save from edit-in-place makes this an acceptable reality. The problem being, on my test page, I send out some test data: a lowercase a with a grave accent above it. On my test page, looking in firebug, it sends it out as %E0, which is the correct hexcode for this character. When I use it in a production page however, it gets sent out as %C3%A0, which is a capital A with a tilde, followed by a space. has anyone else come across this? *I know the arguments for unicode, but frankly two developers aren't going to convince 75 editorial staff that they need to change the way they've done things for 10+ years. Java isn't available on the server and won't be anytime soon.
