-
21 Feb 2008 8:44 AM #1
UTF-8 character problems in the ISO-8859-15 environment
UTF-8 character problems in the ISO-8859-15 environment
Hi,
We use the ExtJS-Window in our application which works fine if its charset is UTF-8! The special characters are messed up in the ISO-8859-15 charset environment (especially when dealing with the [B]
-
21 Feb 2008 11:17 AM #2
Or may be it is possible to have "Accept-Charset" as "ISO-8859-15" ?!
At present, firebug shows:
Code:Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
-
11 Mar 2008 1:00 PM #3
I have posted several times (please search mainly Premium Help for more details) that best solution is to have everything in UTF-8. Since I've done it for server, server filesystem, mysql, mysql data and browser page (<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> in the head of page, I have had no single problem with characters sets.
Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
22 Jul 2008 6:36 AM #4
Stuck in same problem
Stuck in same problem
Hello,
I stuck almost in the same problem. I have to work with an ISO-8859-1 Web Application Server and it is not scheduled to change that. I developed my application (a simple grid, 2 simple forms) reading xml-data from the server.
In IE all seems to be fine - but when I use Firefox (2.x) the special chars (umlauts) were converted into strange characters.
When I save the form to the database I have also these wrong chars.
I searched this forum almost 4 days for a solution. But I did not see one. I am almost sure there is one simple solution, but I cannot see it at the moment.
If you got any suggestion please let me know.
Thanks a lot
Norbert
-
24 Jul 2008 2:33 AM #5
If you cannot change the server encoding you need a UTF8/ISO-8859-1 conversion layer so the client "thinks" it is talking to a UTF8 server. For example:
DB data (ISO) -> conversion -> send to client (UTF8)
client data (UTF8) -> conversion -> save to database (ISO)Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
26 Jul 2008 12:51 AM #6
Thanks a lot, jsakalos. In fact I found that is the only way to solve the problem. It works almost fine, I am using the Ext.util.Utf8 extension, but I have to struggle with some german umlauts, i.e. the umlauts in capital letters.
Another problem is to change the form requests from form.submit() to Ajax.request to have a possibility to convert the umlauts according to the browser, because in IE everything works fine.
I you or anybody else can provide some helping ideas please let me know them.
Thank you in advance.
-
26 Jul 2008 8:54 AM #7
I've never done such conversion layer myself as servers I use are under my control so my solution has always been to configure servers for utf8.
BTW, strange is that encoding is browser dependent. Which charset do you specify in the page head?Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
28 Jul 2008 11:15 AM #8
I discovered that FF changes the codepage when sending an Ajax request to utf-8, just for the request, I think. IE doesn't, although the codepage selection is set to "automatic" in both browsers.
We discussed it today and we will go the hard way to convert the received data on the server side, but it is not so easy doing this on a SAP R/3 Web Application Server which is not unicode...
Thank you for your ideas and your compassion.
Norbert


Reply With Quote