Bug #25503
closedEditor does not respect charset settings while saving with AJAX
0%
Description
I tried entering some special characters in the Editor (eg äößé), then
saving (using AJAX), then reloading the template again. Characters are
garbled. Seems like the AJAX saving function has problems with the
charset settings (currently I'm not using UTF8).
(issue imported from #M6812)
Updated by Helmut Hummel almost 17 years ago
The normal saving is working fine. See:
http://img265.imageshack.us/img265/4564/diffgv1.gif
One is saved via AJAX, the other one the normal way (t3editor disabled)
It works, when using forceCharset = utf-8
Updated by Administrator Admin almost 17 years ago
with the new mochkitfree version (#0007238) it's much more worse than before:
now the complete code after the special char got cut off!
i'm working on this!
Updated by Administrator Admin over 16 years ago
Prototype uses the javascript function "encodeURIComponent" for encoding the ajax-posts.
this works fine, if the document charset is UTF-8 but causes encoding problems when using e.g. ISO-8859.
This snippet fixes the problem for the editor:
if (document.characterSet != "UTF-8") {
encodeURIComponent = escape;
}
I guess this can solve similar problems in other cases, too.
So we should keep this in mind for later :-)
Updated by Administrator Admin over 16 years ago
will be fixed (for the editor, not in general) in the next patch release
Updated by Administrator Admin over 16 years ago
finally fixed for the editor since rc2
Updated by Michael Stucki almost 11 years ago
- Project changed from 75 to TYPO3 Core
- Target version deleted (
0)