[Erik Reuter]

When I define a new J2EE module (ear, war ejb jar) or create a new xml file, the encoding for that file and the deployment descriptors always default to UTF-8, and not what has been setup as the default encoding under Preferences->Workbench->Editors.

MyEclipseIDE should pick up the default encoding from Preferences for any xml related file.

I’m in Europe and uses ISO-8859-1 as my default encoding.

Running MyEclipseIDE 3.7RC2 in Eclipse 3.0M6 on Fedora Core 1 Linux.

[Riyad Kalla]

erik,
while I can understand your desire to have your default encoding picked up (it makes sense) for most english windows users that means the default encoding picked up for the XML files would cp1252 which is far from standard on any platform. So I do not believe that simply picking up the workbench default is a good solution.

However there is a desire to open up some of the functionality of MyEclipse to user-intervention, maybe editing the XML templates in this case would serve your purpose?

Please let us know and we can mark this request appropriately.

[Erik Reuter]

I thought the default encoding for English Eclipse users would be UTF-8 if not touching the default. Isn’t cp1252 a Windows-derived codepage that’s not really an ISO standard?

In any case, editing the xml templates or being able to change the default encoding for all MyEclipseIDE created xml files would be nice to have.

[Riyad Kalla]

Ok I”ll pass the request on up the chain. As far as Windows/English Default, nope the workbench default is Microsoft’s very own cp1252. It *should* probably be UTF-8, but fortunately for us Microsoft has reinvented the wheel… again.

[Author]

Posts