[symentiseclipse]

We came across a serious problem with XML-File editing.
When opening an existing file (i.e. checked out from cvs) with the MyEclipse XML Editor and save the file, all umlauts are mangled.
This seems to be an UTF-8 encoding problem of the XML-Editor. Maybe we got to change a setting, we tried almost everything we can think of.
If opening and saving with another editor (e.g. oXygen XML-Editor or the Text-Editor) the file is as it should be.

We also tried to change the encoding of the XML-File to fixed UTF-8 (it was UTF-8 automatically) but this has no change in the result from MyEclipse XML Editor.

*** System properties:
apple.laf.useScreenMenuBar=true
awt.toolkit=sun.awt.windows.WToolkit
com.apple.mrj.application.apple.menu.about.name=ArgoUML
com.oxygenxml.editor.home.url=file:/c:/eclipse_3.1/plugins/com.oxygenxml.editor_6.2.4/
com.oxygenxml.is.eclipse.plugin=true
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=I20050627-1435
eclipse.commands=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse_3.1\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
1690_60
-vm
C:\WINDOWS\system32\javaw.exe
eclipse.product=org.eclipse.sdk.ide
eclipse.startTime=1130505803381
eclipse.vm=C:\WINDOWS\system32\javaw.exe
eclipse.vmargs=-Xmx256M
-Dosgi.splashLocation=C:\Programme\MyEclipse4\MyEclipseSplash.bmp
-jar
C:\eclipse_3.1\startup.jar
eof=eof
file.encoding=Cp1252
file.encoding.pkg=sun.io
file.separator=\
gef.imageLocation=/org/argouml/Images
java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
java.awt.printerjob=sun.awt.windows.WPrinterJob
java.class.path=C:\eclipse_3.1\startup.jar
java.class.version=49.0
java.endorsed.dirs=C:\Programme\Java\jre1.5.0_04\lib\endorsed
java.ext.dirs=C:\Programme\Java\jre1.5.0_04\lib\ext
java.home=C:\Programme\Java\jre1.5.0_04
java.io.tmpdir=C:\DOKUME~1\roos\LOKALE~1\Temp\
java.library.path=C:\WINDOWS\system32;.;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\system32;
C:\WINDOWS;C:\WINDOWS\System32\Wbem;

java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=1.5.0_04-b05
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.5
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.5.0_04
java.vm.info=mixed mode, sharing
java.vm.name=Java HotSpot(TM) Client VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=1.5.0_04-b05
line.separator=

…
*** Features:
com.genuitec.myeclipse.ast (4.0.3) “MyEclipse Application Server Tooling”
com.genuitec.myeclipse.bugzilla (4.0.0) “MyEclipse Bugzilla Feature”
com.genuitec.myeclipse.core (4.0.3) “MyEclipse Core Feature”
com.genuitec.myeclipse.database (4.0.1) “MyEclipse Database Feature”
com.genuitec.myeclipse.enterprise.workbench (4.0.3) “MyEclipse Enterprise Workbench Feature”
com.genuitec.myeclipse.help (4.0.3) “MyEclipse Help Feature”
com.genuitec.myeclipse.hibernate (4.0.1) “MyEclipse Hibernate Feature”
com.genuitec.myeclipse.jsf (4.0.1) “MyEclipse JSF Feature”
com.genuitec.myeclipse.jspdesign (4.0.3) “MyEclipse JSP Design Feature”
com.genuitec.myeclipse.platform (4.0.0) “MyEclipse Base Platform Feature”
com.genuitec.myeclipse.spring (4.0.2) “MyEclipse Spring Feature”
com.genuitec.myeclipse.struts (4.0.1) “MyEclipse Struts Feature”
com.genuitec.myeclipse.tapestry (4.0.3) “MyEclipse Tapestry / Spindle Feature”
com.genuitec.myeclipse.uml (4.0.1) “MyEclipse UML Feature”
com.genuitec.myeclipse.wdt (4.0.3) “MyEclipse Web Development Feature”
com.oxygenxml.editor (6.2.4) “oXygen XML Editor”
net.sf.eclipsensis (0.9.3) “EclipseNSIS”
net.sf.eclipsensis.installoptions (0.9.3) “EclipseNSIS InstallOptions Editor”
org.eclipse.jdt (3.1.0) “Eclipse Java Development Tools”
org.eclipse.jdt.source (3.1.0) “Eclipse Java Development Tools SDK”
org.eclipse.pde (3.1.0) “Eclipse Plug-in Development Environment”
org.eclipse.pde.source (3.1.0) “Eclipse Plug-in Development Environment Developer Resources”
org.eclipse.platform (3.1.0) “Eclipse Platform”
org.eclipse.platform.source (3.1.0) “Eclipse Platform Plug-in Developer Resources”
org.eclipse.rcp (3.1.0) “Eclipse RCP”
org.eclipse.rcp.source (3.1.0) “Eclipse RCP Plug-in Developer Resources”
org.eclipse.sdk (3.1.0) “Eclipse Project SDK”
org.eclipse.team.extras (3.0.0) “Eclipse FTP and WebDAV Support”

<removed rest of config logfile because it doesn’t fit here in the post – too large>

Thanks,
Robert

[Riyad Kalla]

Robert,
When you say the umlats are mangled do you mean they are mangled visually or they are mangled in the file itself, so if you opened it with another editor, they are still mangled? Also please provide a sample file so I can reproduce this locally and file the issue. Sorry you are and your team are running into this issue.

[symentiseclipse]

@support-rkalla wrote:

Robert,
When you say the umlats are mangled do you mean they are mangled visually or they are mangled in the file itself, so if you opened it with another editor, they are still mangled?
Also please provide a sample file so I can reproduce this locally and file the issue. Sorry you are and your team are running into this issue.

It seems only the view gets corrupted. If I open the file with another editor, it looks ok still.
I’ve added two screenshots.
File myEclipse-XML-Encodingerror.jpg shows the faulty encoding
File oXygen-XML-Encoding-OK.jpg shows the correct content.

Also, I provide file myeclipse-test.xml as a test case.

We reproduced the fault this way:
– Created a new Java-Project´
– copied an existing xml file from another project over
– Edited the xml file using MyEclipse XML Editor
– saved the file
– opened xml-file with MyEclipse->File OK.
– opened xml-file with alternate editors (standard and oxygen editor)->File OK
– Restart Eclipse
– open xml-file with MyEclipse->File corrupted
– opened xml-file with alternate editors (standard and oxygen editor)->File still OK.

Robert

Update: Files will be emailed as attachments are not allowed here. (Would be nice if you enable it in the future)

[Riyad Kalla]

Robert,
Did you mean you emails us this information? (you said you added two screenshots and a test file, I don’t know where exactly). If you did email them to us, be sure to include a link to this forum post so we know why we are getting the files, support@genuitec.com ATTN Riyad.

[Riyad Kalla]

Robert,
Sorry for the delay, I recieved your test file and tried quite a few different versions of the actions you outlined above and was unable to reproduce the problem. The external editors I tried were Notepad and Textpad… are you sure the corruption isn’t from your Oxygen editor? Try using Notepad to see if the same error occurs.

[awuertz]

The problem really exists. I also have a test version of oXygen installed, but the problem occured before that. Every time you save close and reopen the file, it gets worse. So I’d say it is a model problem, not a view problem. The simplest example I found:
<?xml version=”1.0″ encoding=”UTF-8″?>
<root attr=”ü”/> (This is a u-umlaut, in case we get an encoding problem in this post)
Enter this into MyEclipse XML-Editor, save the file and reopen it using the XML-Editor. You’ll end up with
<?xml version=”1.0″ encoding=”UTF-8″?>
<root attr=”ü”/>
which looks to me as if it was opened using ISO-8859-1 encoding. Save it again, close and reopen it and you’ll end up with even more garbage.

The above also happens if the file is created using encoding=”ISO-8859-1″.

Funnily I cannot change the encoding of an existsing file from UTF-8 to ISO-8859-1 (then it tells me this encoding is not supported)

PLEASE look into this bug. It makes the XML Editor useless for us, since we always have some Umlauts in the xml-Attributes

[awuertz]

More details: if you bind a doc-extension to the MyEclipse XML Editor, it makes the mistake. Before installing oXygen, MyEclipse only had a problem with our documents with extension *.form (which contain XML). After installing oXygen, MyEclipse had problems with all kinds of XML-files.

The reason seems to lie somewhere in the eclipse prefs concerning content-types. If I deinstall oXygen, *.xml is handled correctly by MyEclipse again. If I enter *.form as content-type XML, MyEclipse even handles these correctly.

So the question ist: why does MyEclipse insist on a content type entry? Should be the fact, that *.form ist bound to the MyEclipse XML Editor, be enough? At the moment it is impossible to have both (MyEclipse and oXygen) installed. This is not good, since we need features from both softwares.

[Riyad Kalla]

awuertz,
Please download Eclipse 3.2M7 from the Eclipse.org site and unzip it to a new directory. Then download MyEclipse 5.0 Milestone 1 from our Developmental Releases area and install it to a new location against your new Eclipse 3.2M7 install. Then start it up. Try your same example again, trying it locally looks like the bug was fixed in 5.0, saving and reopening the file with the umlaut works fine.

I hope we squashed this bug in our upcomming 5.0 release.

[Author]

Posts