I'm already doing that. However, in the server I must convert from one
charset to another programmaticaly.
The problem seems to be the use of "encodeURIComponent" function by
Encodes a Uniform Resource Identifier (URI) by replacing each instance of
> certain characters by one, two, or three escape sequences representing the
> UTF-8 encoding of the character.
Replacing all occurences of "encodeURIComponent" function by "escape"
function solved the problem. The question is whether using "escape" is worth
> escape and unescape
The escape and unescape functions let you encode and decode strings. The
> escape function returns the hexadecimal encoding of an argument in the ISO
> Latin character set. The unescape function returns the
string for the specified hexadecimal encoding value.
the differences between some functions to encode strings.
Is there any chance to enhance prototype to use the correct function based
on an "encoding" parameter?
Thanks a lot. (sorry my bad english) :D
2008/10/22 Baglan <[EMAIL PROTECTED]>
> The 'encoding' option seems not to be doing much. Request is sent in
> UTF-8 and response encoding is determined by the encoding conveyed in
> the HTTP header of the response.
> In practical terms, you can skip the 'encoding' parameter, expect data
> in UTF-8 on the server and set response content type and charset to:
> text/html; charset=iso-8859-1
> - Baglan
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at