Oxygen Eclipse Editor Not Getting Correct Encoding

Suggestion on the Eclipse plug-in docs: it would be helpful to mention that you may need to explicitly set the encoding for XML documents that have a non-standard extension and that are being reported as ASCII rather than UTF-8 by Eclipse. It took me a while to figure this out (and I might never have if I didn't dimly remember being able to set the encoding in the package explorer). Cheers, Eliot -- W. Eliot Kimber Professional Services Innodata Isogen 9390 Research Blvd, #410 Austin, TX 78759 (214) 954-5198 ekimber@innodata-isogen.com www.innodata-isogen.com

Hello, You just have to associate the non-standard extension with the Oxygen XML Editor in Window -> Preferences -> General -> Editors -> File Associations and with the oXygen XML content type in Window -> Preferences -> General -> Content Types -> Text -> XML -> oXygen XML as described in the User Manual for the Eclipse plugin: http://projects.sync.ro/doc/ug-eclipse/common-problems.html If you associate the extension with oXygen Eclipse as described above and the file does not have an encoding declaration in the document prolog then oXygen applies the UTF-8 encoding by default. There was a problem with the default encoding when it was not declared in the document prolog but version 8.1 which will be released probably next week will fix that, it will use UTF-8 by default. Regards, Sorin W. Eliot Kimber wrote:
Suggestion on the Eclipse plug-in docs: it would be helpful to mention that you may need to explicitly set the encoding for XML documents that have a non-standard extension and that are being reported as ASCII rather than UTF-8 by Eclipse.
It took me a while to figure this out (and I might never have if I didn't dimly remember being able to set the encoding in the package explorer).
Cheers,
Eliot

Sorin Ristache wrote:
Hello,
You just have to associate the non-standard extension with the Oxygen XML Editor in Window -> Preferences -> General -> Editors -> File Associations and with the oXygen XML content type in Window -> Preferences -> General -> Content Types -> Text -> XML -> oXygen XML as described in the User Manual for the Eclipse plugin:
Ah--I had done the file associations but didn't know about the content types association.
http://projects.sync.ro/doc/ug-eclipse/common-problems.html
If you associate the extension with oXygen Eclipse as described above and the file does not have an encoding declaration in the document prolog then oXygen applies the UTF-8 encoding by default. There was a problem with the default encoding when it was not declared in the document prolog but version 8.1 which will be released probably next week will fix that, it will use UTF-8 by default.
That sounds cool. Cheers, E. -- W. Eliot Kimber Professional Services Innodata Isogen 9390 Research Blvd, #410 Austin, TX 78759 (214) 954-5198 ekimber@innodata-isogen.com www.innodata-isogen.com

Sorry, the correct link for the manual page is: http://www.oxygenxml.com/doc/ug-eclipse/common-problems.html Regards, Sorin Sorin Ristache wrote:
Hello,
You just have to associate the non-standard extension with the Oxygen XML Editor in Window -> Preferences -> General -> Editors -> File Associations and with the oXygen XML content type in Window -> Preferences -> General -> Content Types -> Text -> XML -> oXygen XML as described in the User Manual for the Eclipse plugin:
http://projects.sync.ro/doc/ug-eclipse/common-problems.html
If you associate the extension with oXygen Eclipse as described above and the file does not have an encoding declaration in the document prolog then oXygen applies the UTF-8 encoding by default. There was a problem with the default encoding when it was not declared in the document prolog but version 8.1 which will be released probably next week will fix that, it will use UTF-8 by default.
Regards, Sorin
W. Eliot Kimber wrote:
Suggestion on the Eclipse plug-in docs: it would be helpful to mention that you may need to explicitly set the encoding for XML documents that have a non-standard extension and that are being reported as ASCII rather than UTF-8 by Eclipse.
It took me a while to figure this out (and I might never have if I didn't dimly remember being able to set the encoding in the package explorer).
Cheers,
Eliot
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (2)
-
Sorin Ristache
-
W. Eliot Kimber