For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 14 replies, 5 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
There is a bug in JSP Editor with ISO-8859-2 encoding.
Polish fonts are saved with wrong encoding (possible ISO- 8859-1).Can you send a sample JSP page to support@genuitec.com that we can attach to a bug report as a test case?
Also please referenec this thread for us so we know why we are getting the attachment.
Try use somthing like this (in every JSP file):
<%@ page language=”java” pageEncoding=”UTF-8″%>
or use ISO-8859-2
Yes, Lukas has a good point, specifying the pageEncoding value will be honored by the editor if other ways are not working.
Also we have an open bug with the default encoding of the JSP editor always being Latin no matter what the user sets, so hopefully that will be fixed in 3.8.3 for you.
Doesn’t helped do me.
I heave this problem on 3.8.4 for Eclipse 3.1M6 and 3.8.4 for Eclipse 3.0Pawel.
Pawel,
You have set the pageEncoding and MyEclipse is still mangling the non-latin characters?This fix WILL be in the next release, I worked with the dev that found/fixed it and he did quite a thurough job of it.
Thanks for response.
Problem still exists and there is no way to put any lang specific letters. UTF-8 doesn’t work too. (for HTML files works OK)
In preferences/MyEclipse/Editors/JSP/Encoding: Central/East Europen (Slavic)
Here is header of my jsp file:<%@ taglib uri=”/WEB-INF/struts-html.tld” prefix=”html” %>
<%@ taglib uri=”/WEB-INF/struts-bean.tld” prefix=”bean” %>
<%@ taglib uri=”/WEB-INF/struts-logic.tld” prefix=”logic” %><%@page import=”java.util.*”%>
<%@page language=”java” pageEncoding=”ISO-8859-2″%><!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”>
<html:html locale=”true”>
<head>
<html:base />
<title>MyJsp.jsp</title>
<META http-equiv=”Content-Type” content=”text/html; charset=ISO-8859-2″>
<meta http-equiv=”pragma” content=”no-cache”>
<meta http-equiv=”cache-control” content=”no-cache”>
<meta http-equiv=”expires” content=”0″>
</head>Pawel
Pawel,
This might be a long shot, but @page directives typically come first, and @taglib directives after, that is how we have always tested, try changing their order.Also, to clarify, you are saying that if you enter Slavic characters, save, close and reopen the file, they are mangled, correct? (I still don’t know EXACTLY what your situation is, sometimes the littlest detail can make the difference. So please let me know)
OK, I think now I know where is the problem.
As you said, @page must be the first, but @page with pageEncoding parameter must be the FIRST line of file.
When I did this, there heppens something strange, I could corect edit every one my jsp file (even with @page as last). But after reboot MyElcipse those one with @page as last, were edited wrong. Puting @page with pageEncode as first line solved problem.Thank you very much for your help.
My previous project I realized in WSAD and there doesn’t metter order of @taglib, @page.I hope my little work let you make MyEclipse better.
Best regards
PawelThere is another bug.
From time to time editing jsp file (with correct inserted @page) Editor starts behavior strange….
When I type, cursor doesn’t move with text but stay in his position, so I type in reverse!!!!
When I press del, I get alert “The command for the key you preseed failed. Reason: The command for the key you preseed failed”
Only restart of MyEclipse helps.Pawel
Pawel,
I will file the first bug you mentioned (the order of @page) this was previously an unknown bug and I thank you for finding it. The 2nd bug (backwards typing) is a known issue that we are investigating for 4.0, it seems to happen when users try and use the designer, are you using the page designer a lot?When editing HTML pages, there is a “Design” tab at the bottom of the editor that takes you to a WYSIWYG page editor (drag and drop). If you aren’t using this then it’s no problem, I am just trying to nail down what causes the backwards typing for our users.
