[
https://issues.apache.org/jira/browse/TAPESTRY-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506772
]
Lionel Touati commented on TAPESTRY-1591:
-----------------------------------------
In the form.js file, in method submitAsync, the arguments passed to the binding
method of dojo use the following arguments:
var kwArgs={
formNode:form,
content:content,
useCache:true,
preventCache:true,
error: (function(){tapestry.error.apply(this, arguments);}),
encoding: "UTF-8"
};
My problem is that the rest of the application is rendered with another
encoding. So when the data is posted to the server, a conversion occurs, with
misinterpret the data. By changing to
var kwArgs={
formNode:form,
content:content,
useCache:true,
preventCache:true,
error: (function(){tapestry.error.apply(this, arguments);}),
encoding: "ISO-8859-1"
};
My problem is gone, as ISO-8859-1 is the encoding I use.
The is the same issue in the bind method of the core.js file
To reproduce the issue, put org.apache.tapestry.output-encoding as 8859-1 and
enter the following character é
the has not the same position in the 2 charsets. When the data is submitted
using ajax to the server, the data will be wrongly converted
Hope this helps
> Encoding for Ajax Request is always UTF-8
> -----------------------------------------
>
> Key: TAPESTRY-1591
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1591
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 4.1.2
> Reporter: Lionel Touati
>
> Ajax request encoding should match template content type.
> It should follow:
> org.apache.tapestry.output-encoding
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
