Community
Participate
Working Groups
WTP 1.0M3 (with Web Services), Eclipse 3.1M5, JDK 1.4 I'm not sure if this is the right place to report this bug, but since the problem just occures on files used by the WTP editors, it seems to be a WTP problem. The WTP editors ignore the encoding setting of the workspace or the project. The file's property dialog says for the text file encoding: "Default (determined from content: ...)" instead of "Default (inherited from container: ...)" (as e.g. used by the java editor). So the workspace's or project's encoding setting has no effect on any file managed by the WTP and there is no way to e.g. determine a general text encoding for a project. This behaviour is especcially a big problem in combination with bug# 90241 - that all js files get determined as US-ASCII, which garbles their umlauts and other special characters.
I think this depends on the content type of the file. XML, HTML, JSP all have ways to specify the encoding in the file, so they should be determined by content. So I don't think "Default (determined from content: ...)" should be replaced with "Default (inherited from container: ...)" Perhaps instead, a bug should be opened on the base to offer both options, so you have: Determine from content Determine from container Other There is a way to change some default encoding behaviour, like encoding to use when creating files. These can be found in Preferences=>Web and XML=>xxx Files. Javascript is a special issue. Since there is a specific bug opened on that, i'll add my comment to bug# 90241.
(In reply to comment #1) I think having the option to generally setting the default encoding to all files of a workspace or project is still a good idea - like the suggestion you made on that new feature bug (options "Determine from content", "Determine from container", "Other").
I think between the comments here, and in bug 90241, this issue is resolved. M6/WTPm4 should allow the kind of control you want over 'javascript', and for XML and JSPs, there really is supposed to be a standard assumed if not specified in file (always better to specify in file!) Let us know if next milestone behaves as expected.
Changed Version field given new release numbering.
Marking as verified as I know this issue is fixed (or correctly categorized). If, as originator, you disagree or still see, please re-open, or open a new bug. Thanks very much for reporting and helping make WTP better.
Reassinging bug to wst-inbox@eclipse.org.
This is part of a mass update to close out all stale WTP defects already verified by the reporter but awaiting closure by the assignee. If you feel this defect was closed inappropriately, please reopen. Thanks, John Lanuti
