– open xml-file with MyEclipse->File corrupted – opened xml-file with alternate editors (standard and oxygen editor)->File OK – opened xml-file with MyEclipse->File OK. – Edited the xml file using MyEclipse XML Editor – copied an existing xml file from another project over If I open the file with another editor, it looks ok still.įile myEclipse-XML-Encodingerror.jpg shows the faulty encodingįile oXygen-XML-Encoding-OK.jpg shows the correct content.Īlso, I provide file myeclipse-test.xml as a test case. Sorry you are and your team are running into this issue. 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?Īlso please provide a sample file so I can reproduce this locally and file the issue. (3.1.0) “Eclipse RCP Plug-in Developer Resources” (3.1.0) “Eclipse Platform Plug-in Developer Resources” (3.1.0) “Eclipse Plug-in Development Environment Developer Resources” (3.1.0) “Eclipse Plug-in Development Environment” (3.1.0) “Eclipse Java Development Tools SDK” (3.1.0) “Eclipse Java Development Tools” Net.sf.eclipsensis.installoptions (0.9.3) “EclipseNSIS InstallOptions Editor” Java.vm.specification.vendor=Sun Microsystems Inc.Ĭom. (4.0.3) “MyEclipse Application Server Tooling”Ĭom. (4.0.0) “MyEclipse Bugzilla Feature”Ĭom. (4.0.3) “MyEclipse Core Feature”Ĭom. (4.0.1) “MyEclipse Database Feature”Ĭom. (4.0.3) “MyEclipse Enterprise Workbench Feature”Ĭom. (4.0.3) “MyEclipse Help Feature”Ĭom. (4.0.1) “MyEclipse Hibernate Feature”Ĭom. (4.0.1) “MyEclipse JSF Feature”Ĭom. (4.0.3) “MyEclipse JSP Design Feature”Ĭom. (4.0.0) “MyEclipse Base Platform Feature”Ĭom. (4.0.2) “MyEclipse Spring Feature”Ĭom. (4.0.1) “MyEclipse Struts Feature”Ĭom. (4.0.3) “MyEclipse Tapestry / Spindle Feature”Ĭom. (4.0.1) “MyEclipse UML Feature”Ĭom. (4.0.3) “MyEclipse Web Development Feature”Ĭom.oxygenxml.editor (6.2.4) “oXygen XML Editor” Java.vm.specification.name=Java Virtual Machine Specification =Java(TM) 2 Runtime Environment, Standard Edition Java.io.tmpdir=C:\DOKUME~1\roos\LOKALE~1\Temp\ Dosgi.splashLocation=C:\Programme\MyEclipse4\MyEclipseSplash.bmp 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.Ĭom.=ArgoUMLĬom.=file:/c:/eclipse_3.1/plugins/_6.2.4/Įclipse.application=.ide.workbench oXygen XML-Editor or the Text-Editor) the file is as it should be. If opening and saving with another editor (e.g. Maybe we got to change a setting, we tried almost everything we can think of. This seems to be an UTF-8 encoding problem of the XML-Editor. checked out from cvs) with the MyEclipse XML Editor and save the file, all umlauts are mangled. We came across a serious problem with XML-File editing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |