Side navigation
#116 closed enhancement (invalid)
Opened July 31, 2006 10:27PM UTC
Closed October 03, 2006 08:58AM UTC
Last modified June 20, 2007 05:22AM UTC
Different Encodings for AJAX
| Reported by: | john | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | ajax | Version: | |
| Keywords: | iso-8859-1 | Cc: | |
| Blocked by: | Blocking: |
Description
AJAX requests should have an option to support multiple file encodings (for i18n support).
Attachments (0)
Change History (3)
Changed August 02, 2006 12:06AM UTC by comment:1
| keywords: | → iso-8859-1 |
|---|
Changed August 04, 2006 02:58AM UTC by comment:2
I dont know much about this but...
In jQuery we are using: encodeURIComponent().
At http://xkr.us/articles/javascript/encode-compare/, It says which one is best to use in which condition.
It says this:
The escape() method does not encode the + character which is interpreted as a space on the server side as well as generated by forms with spaces in their fields. Due to this shortcoming, you should avoid use of escape() whenever possible. The best alternative is usually encodeURIComponent().
Now this limitation can be bad in many cases. If the problem is being created by encoding... can't it just be removed so that users can use appropriate coding depending on thr need?
Changed October 03, 2006 08:58AM UTC by comment:3
| resolution: | → invalid |
|---|---|
| status: | new → closed |
fyi: in prototype.js other encoding than uft-8 works if one uses the escape() method instead of the encodeURI() method