Opened 14 years ago
Closed 13 years ago
#2628 closed defect (wontfix)
IframeIO uses wrong charset
Reported by: | joose | Owned by: | alex |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | IO | Version: | 0.4.2 |
Keywords: | IframeIO | Cc: | |
Blocked By: | Blocking: |
Description
IframeIO is doing stuff in latin-1.
This is easy to test, just add Ä to tests/io/IframeIOResponse.html file...
normal dojo.io.bind does things using utf8
Change History (3)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
This is what I found:
- If you specify you page as UTF-8 and specify that responde is also UTF-8 == seems to work ok
- If you don't specify your page as UTF-8 but respond is UTF-8 == does not work
- filename is not converted to UTF-8, it's send as Latin-1
- content: -values from dojo.io.bind are sent as utf-8
- if you specify your page as utf-8 but not the respond:
- everything is sent as utf-8 but resulting stuff is latin-1
- if you don't specify content as utf-8 anywhere
- static and content value is not ok, filename is ok
example outputs:
Filename: Screenshöt_1.png value specified in io.bind: ä static value in returning value: ä
Format: <static> = <value> = <filename>
case 1)
DEBUG: First H1 tag text: ä = ä = Screenshöt_1.png
case 2)
DEBUG: First H1 tag text: ä = ä = Screensh�t_1.png
case 3)
DEBUG: First H1 tag text: ä = ä = Screenshöt_1.png
case 4)
DEBUG: First H1 tag text: ä = ä = Screenshöt_1.png
comment:3 Changed 13 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
go with UTF-8. Thanks.
Punt.
Note: See
TracTickets for help on using
tickets.
the resulting latin-1 <-> utf8 might be something we can't do in dojo, but it also sends data in latin-1 and that is something we can do about.. I try to make a bug fix soon if I am able to.