- This topic has 9 replies, 2 voices, and was last updated 18 years, 9 months ago by
.
-
Posts
-
.jsp files are associated with the JSP designer. fine.
.tag files are associated with the JSP designer. fine..jspf files (JSP fragments) are associated with the JSP designer. fine.
.tagf files (tag fragments) are not associated with the JSP designer. bad.And if force a .tagf file to be openend with the JSP designer (or with the “classic JSP editor”), it reports strange problems like tag not closing on line
<%@ tag language="java" pageEncoding="UTF-8" %>And I get strange colors (wrong syntax highlighting) on the code …
Can I do something about this? I think it’s an ugly workaround to rename all my .tagf files to .jspf …
What you need to do is navigate to Window > Prefs > General > Content Types > Text > MyEclipse JSP Content Types > click Add and add *.tagf, hit OK and reopen your file. You should be cooking with oil.
Great! Thank you!
But why is “Default encoding” ISO-8859-1 and not equal to the setting in Window > Prefs > General > Editors > Text file encoding? (in my case UTF-8)
@support-rkalla wrote:
Not sure, it might be set by the plugin, I’ll check.
What did you find out?
Even worse, the setting that I did (“UTF-8” is ignored! The properties of my JSP files say “Default (determined from content: ISO-8859-1), even if I create new ones. Tag files the same.
Please help!
Thank you. I see. The problem is: This does not work for .tag and .tagf. There you have:
<%@ tag language=”java” pageEncoding=”UTF-8″ %>
And this is obviously not parsed by MyEclipse 🙁
Right, support for this hasn’t been added yet. We appologize for the issue, I have filed this as a bug.
