Information provided is not enough to reproduce the problem.
Please tell what encoding you are using? And I have no
korean keyboard... So, please attach example JSP file if
possible
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get the same problem with Japanese Kanji (MS932) but
have workaround. You can reproduce the error by following
sequence:
1. create test.jsp (or whatever) file which contains several 2-
byte characters encoded in MS932
2. drop test.jsp in a project in Ecplise worlkspace
3. issue Refresh for the project (test.jsp appears)
4. open test.jsp with JSP Source Editor
Now you see corrupted data. But actual file is not broken
yet. In the Editor, select Edit > Encoding > MS932 and
close the editor window (no file save occurs). Then reopen
the file. You will see correct data.
Note that this workaround works only the first time you open
the file. If you save the file with incorrect encoding, you
actually break it!
Makoto Ohtoh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also get same problem with Japanese Kanji (MS932).
Will this problem be solved in the near future?
Would you please let me know whether this problem
is planned to be solved or not?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't you use
<%@page contentType="text/html; charset=MS932"%>
or
<%@page pageEncoding="MS932"%>
directive?
For JSP 1.x any page that is not ISO-8859-1 must have
explicit encoding declaration (per JSP spec.). Actually JSP
2.0 changed that and now encoding could be declared in
externally through web.xml application descriptor. This
scenario is not supported jet, and you could use contentType
or pageEncoding declarations in all your JSPs as workaround
(this is good practice anyway). Tell me if this workaround
is not working! And if it is working tell too!!! I will help
isolate the problem!
JSP 2.0 way is not supported yet and should be fixed. I'll
make a new release soon, so any feedback on this issue would
be wery welcome!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=346040
Information provided is not enough to reproduce the problem.
Please tell what encoding you are using? And I have no
korean keyboard... So, please attach example JSP file if
possible
Logged In: NO
I get the same problem with Japanese Kanji (MS932) but
have workaround. You can reproduce the error by following
sequence:
1. create test.jsp (or whatever) file which contains several 2-
byte characters encoded in MS932
2. drop test.jsp in a project in Ecplise worlkspace
3. issue Refresh for the project (test.jsp appears)
4. open test.jsp with JSP Source Editor
Now you see corrupted data. But actual file is not broken
yet. In the Editor, select Edit > Encoding > MS932 and
close the editor window (no file save occurs). Then reopen
the file. You will see correct data.
Note that this workaround works only the first time you open
the file. If you save the file with incorrect encoding, you
actually break it!
Makoto Ohtoh
Logged In: NO
I also get same problem with Japanese Kanji (MS932).
Will this problem be solved in the near future?
Would you please let me know whether this problem
is planned to be solved or not?
Thanks.
Logged In: YES
user_id=346040
Don't you use
<%@page contentType="text/html; charset=MS932"%>
or
<%@page pageEncoding="MS932"%>
directive?
For JSP 1.x any page that is not ISO-8859-1 must have
explicit encoding declaration (per JSP spec.). Actually JSP
2.0 changed that and now encoding could be declared in
externally through web.xml application descriptor. This
scenario is not supported jet, and you could use contentType
or pageEncoding declarations in all your JSPs as workaround
(this is good practice anyway). Tell me if this workaround
is not working! And if it is working tell too!!! I will help
isolate the problem!
JSP 2.0 way is not supported yet and should be fixed. I'll
make a new release soon, so any feedback on this issue would
be wery welcome!
Logged In: YES
user_id=346040
Uhm... a bit messy comment... sorry, copy&pasted several
times and don't verified final text... But I hope meaning is
not lost :)