Files open empty
Posted: Tue Dec 06, 2011 10:08 am
Hello,
I'm working in a linguistic project where we use oXygen to annotate corpus files in XML format. So far everything worked fine, but recently the following problem occurred. When one of my colleagues tries to open certain files in oXygen, the main window shows up empty. The XML tree can be accessed via the Outline window, but no text appears in the main window. When opening such a file while other files are open, strange things happen (seemingly at random) once one closes one of these files, for instance, the text of the other files disappears, too, the toolbar disappears or gets doubled, or a Java error message ("unhandled errors encountered. [ AWT-EventQueue-0 ] - java.lang.NullPointerException") pops up.
My colleague is using Windows 7 Professional. I myself am using Mac OS X 10.6.8 and do not have any problems opening the same files. What's more, he himself can open most files, including some that are completely parallel to the problematic files with respect to encoding, used DTD, XML header, and structure (as far as I can see). Does anybody have an idea how to deal with this?
Robert
I'm working in a linguistic project where we use oXygen to annotate corpus files in XML format. So far everything worked fine, but recently the following problem occurred. When one of my colleagues tries to open certain files in oXygen, the main window shows up empty. The XML tree can be accessed via the Outline window, but no text appears in the main window. When opening such a file while other files are open, strange things happen (seemingly at random) once one closes one of these files, for instance, the text of the other files disappears, too, the toolbar disappears or gets doubled, or a Java error message ("unhandled errors encountered. [ AWT-EventQueue-0 ] - java.lang.NullPointerException") pops up.
My colleague is using Windows 7 Professional. I myself am using Mac OS X 10.6.8 and do not have any problems opening the same files. What's more, he himself can open most files, including some that are completely parallel to the problematic files with respect to encoding, used DTD, XML header, and structure (as far as I can see). Does anybody have an idea how to deal with this?
Robert