Chapter 25. Common problems

25.1. <oXygen/> opens a XML document after a long time. Why does it happen?
25.2. I am trying to open a file larger than 70 MB for editing in <oXygen/> but it keeps telling me it runs out of memory. What can I do?
25.3. My file was created with other application and it contains special characters like é, ©, ®, etc. Why does <oXygen/> display a square for these characters?
25.4. When I run a transformation in the XSLT Debugger perspective it is very slow. Can I increase the speed?
25.5. When I start <oXygen/> on Windows XP I get the following error. What can I do?
25.6. I tried to start <oXygen/> on Windows but it crashed with an error message about “Fault Module Name: nvoglv32.dll”. How can I start <oXygen/> on my computer?
25.7. <oXygen/> crashed the Apple JVM/<oXygen/> could not start up on my Mac OS X computer due to a JVM crash. What can I do?
25.8. When I do a keyword search in the User Manual the search highlights the wrong word in the text, often several words after the keyword. Is this a bug?
25.9. The keyboard shortcuts listed in Options -> Preferences -> Menu Shortcut Keys do not work. What can I do?
25.10. Before installing Oxygen XML Editor/Author I had no problems viewing XML files in Internet Explorer but now Internet Explorer opens an XML file in Oxygen XML Editor/Author. How can I view XML files in Internet Explorer again?
25.11. I cannot associate the <oXygen/> application with a file type on my Windows computer by right clicking on a file in Windows Explorer, selecting Open With -> Choose Program and browsing to the file oxygen.exe. When I select the file oxygen.exe in the Windows file browser dialog and I click the Open button of the dialog the <oXygen/> application is not added to the list of applications in the Open With dialog of Windows. What can I do?
25.12. When I close the <oXygen/> application with multiple files open and then restart it, every file opens in a split panel of the editing area instead of a tab sharing with the other opened files the same editing area which organizes the editors in a tabbed pane. I want to have the files arranged as a tabbed pane as they used to be arranged before this restart of <oXygen/>.
25.13. I try to run <oXygen/> on Linux with the Compiz / Beryl window manager but I get only a grey window which does not respond to user actions / after opening and closing an <oXygen/> dialog or after resizing the <oXygen/> window or a view of the <oXygen/> window the content of this window becomes grey and it does not respond to user actions. What is wrong?
25.14. When I try to drag with the mouse an unselected resource from the Project View/DITA Maps Manager, the drag never starts, it only selects the resource. I need to drag the resource again after it becomes selected. As a result any drag and drop without initial selection becomes a two step operation. How can I fix this?
25.15. How do I set the version X of the Java virtual machine for <oXygen/> on Mac OS X?
25.16. On my Mac OS X machine when I double-click on the <oXygen/> icon the application doesn't start / gives a Segmentation fault error.
25.17. After upgrading my OS X version to 10.4.x / my <oXygen/> version to 6.x <oXygen/> is not associated to the file types XML, XSL, XSD, etc. This worked in the previous version of <oXygen/>.
25.18. After upgrading my Mac OS X to version 10.4.1 Tiger I am not able to set all XML files to open with <oXygen/> when I click Change All in the Get Info dialog. This worked in OS X 10.3.x.
25.19. I cannot connect to a SVN repository from the Repository Browser view of SVN client. How can I find more data about the error?
25.20. What details can I add to my problem report that I enter on the Technical Support online form of the product website?
  25.1.

<oXygen/> opens a XML document after a long time. Why does it happen?

All the content of your document is on a single line or the document is very large. If the content is on a single line please enable the Format and indent the document on open preference from OptionsPreferences+Editor / Format / XML before opening the document. If the document is very large (above 10 MB) you should increase the memory available to <oXygen/>.

  25.2.

I am trying to open a file larger than 70 MB for editing in <oXygen/> but it keeps telling me it runs out of memory. What can I do?

Try to increase the memory used by <oXygen/> as described in section Performance problems. If you are still unable to open it you should consider using the Large File Viewer tool available both in the <oXygen/> application on the Tools menu and as a standalone tool on the shortcuts menu together with the <oXygen/> shortcut.

  25.3.

My file was created with other application and it contains special characters like é, ©, ®, etc. Why does <oXygen/> display a square for these characters?

You must set a font able to render the special characters from Font preferences. If it is a text file you must set also the encoding used for non XML files. If a TrueType font installed on the computer is not accessible in the Font preferences the Java virtual machine is not able to load the system fonts. It is a problem of the Java virtual machine and a possible solution is to copy the files of the font in the [JVM-home-folder]/lib/fonts folder.

  25.4.

When I run a transformation in the XSLT Debugger perspective it is very slow. Can I increase the speed?

Disable rendering of output to the XHTML Output view during the transformation process if the transformation produces HTML or XHTML output. In order to view the output result run the transformation in the Editor perspective with the option "Open in browser" or run it in the Debugger perspective, save the Text output area to a file and use an external browser for viewing.

  25.5.

When I start <oXygen/> on Windows XP I get the following error. What can I do?

Cannot start <oXygen/>.
Due to:java.lang.NullPointerException
java.lang.NullPointerException
at com.sun.java.swing.plaf.windows.XPStyle.getString(Unknown Source)
at com.sun.java.swing.plaf.windows.XPStyle.getString(Unknown Source)
at com.sun.java.swing.plaf.windows.XPStyle.getDimension(Unknown Source)
at com.sun.java.swing.plaf.windows.WindowsProgressBarUI.
getPreferredInnerHorizontal(Unknown Source)

The error is cause by a a bug in the Java runtime from Sun Microsystems. You can avoid it by setting the Java system property com.oxygenxml.no.xp.theme to the value true in the startup script. If you start <oXygen/> with the oxygen.bat script just add the parameter

-Dcom.oxygenxml.no.xp.theme=true

to the java command in the script. If you start <oXygen/> from the Start menu shortcut add the same parameter on a new line in the file [oXygen-install-folder]\oxygen.vmoptions .

  25.6.

I tried to start <oXygen/> on Windows but it crashed with an error message about “Fault Module Name: nvoglv32.dll”. How can I start <oXygen/> on my computer?

It is an OpenGL driver issue that can be avoided by creating an empty file called opengl32.dll in the <oXygen/> install folder if you start it with the shortcut created by the installer on the Start menu or on Desktop or in the subfolder bin of the home folder of the default Java virtual machine if you start <oXygen/> with the oxygen.bat script. The default Java virtual machine is the one that is started by a command

java -version

executed in a command line console.

  25.7.

<oXygen/> crashed the Apple JVM/<oXygen/> could not start up on my Mac OS X computer due to a JVM crash. What can I do?

Usually it is an incompatibility between the JVM and a native library of the host system. Depending on your platform, a crash log file is generated with more data about the problem. For Unix type systems you will get an error in the console. For Windows and Mac OS X the path of the crash log file is displayed on screen.

On Mac OS X 10.5 and later there is an more stable JVM called SoyLatte that can be downloaded and installed for avoiding the crash. For running <oXygen/> with the SoyLatte JVM just set the path to the JVM startup executable (SoyLatte-install-folder/bin/java) in the java command at the end of the script oxygenMac.sh and start <oXygen/> from a command line with the command:

sh oxygenMac.sh
  25.8.

When I do a keyword search in the User Manual the search highlights the wrong word in the text, often several words after the keyword. Is this a bug?

You get wrong highlights when <oXygen/> runs with some Java virtual machines. The search highlights are correct when <oXygen/> runs with a stable Java 1.6 virtual machine. It is a problem of the JavaHelp indexer supplied by Sun Microsystems. In order to see correct highlights it is recommended to use Java 1.6.0_01 or later.

  25.9.

The keyboard shortcuts listed in Options -> Preferences -> Menu Shortcut Keys do not work. What can I do?

Usually this happens when a special keyboard layout is set in the operating system which generates other characters than the usual ones for the keys of a standard keyboard. For example if you set the extended Greek layout for your keyboard you should return to the default Greek layout or to the English one. Otherwise the Java virtual machine that runs the application will receive other key codes than the usual ones for a standard keyboard.

  25.10.

Before installing Oxygen XML Editor/Author I had no problems viewing XML files in Internet Explorer but now Internet Explorer opens an XML file in Oxygen XML Editor/Author. How can I view XML files in Internet Explorer again?

XML files are opened in Oxygen because Internet Explorer uses the Windows file associations for opening files and you associated XML files with Oxygen XML Editor/Author in the installer panel called File Associations. This installer panel displays a warning above the XML file association that XML files will not be viewed correctly in Internet Explorer if you associate them with Oxygen XML Editor/Author.

For viewing XML files in Internet Explorer again you have to associate XML files with IE by right-clicking on an XML file in Windows Explorer, selecting Open With -> Choose Program, selecting IE in the list of applications and checking the checkbox "Always use the selected program". Also you have to run the following command from a command line:

wscript revert.vbs

where revert.vbs is a text file with the following content:

  function revert()
    Set objShell = CreateObject("WScript.Shell")
    objShell.RegWrite "HKCR\.xml\", "xmlfile", "REG_SZ"
    objShell.RegWrite "HKCR\.xml\Content Type", "text/xml", "REG_SZ"
  end function
                        
  revert()
  25.11.

I cannot associate the <oXygen/> application with a file type on my Windows computer by right clicking on a file in Windows Explorer, selecting Open With -> Choose Program and browsing to the file oxygen.exe. When I select the file oxygen.exe in the Windows file browser dialog and I click the Open button of the dialog the <oXygen/> application is not added to the list of applications in the Open With dialog of Windows. What can I do?

The problem is due to some garbage Windows registry entries remained from old versions of <oXygen/> Please uninstall all your installed versions of <oXygen/> and run a registry cleaner application for cleaning these entries. Reinstalling a recent version of <oXygen/> will not generate this problem anymore.

  25.12.

When I close the <oXygen/> application with multiple files open and then restart it, every file opens in a split panel of the editing area instead of a tab sharing with the other opened files the same editing area which organizes the editors in a tabbed pane. I want to have the files arranged as a tabbed pane as they used to be arranged before this restart of <oXygen/>.

This happens randomly when several files are opened automatically on startup. It is a problem of the JIDE docking views library used in <oXygen/> for docking and floatable views. The workaround is to run the action PerspectivesReset Layout. If you have a specific layout of the <oXygen/> views which you want to preserve when running this action you should set your layout in OptionsPreferences+Perspectives Layout+Use fixed layout.

  25.13.

I try to run <oXygen/> on Linux with the Compiz / Beryl window manager but I get only a grey window which does not respond to user actions / after opening and closing an <oXygen/> dialog or after resizing the <oXygen/> window or a view of the <oXygen/> window the content of this window becomes grey and it does not respond to user actions. What is wrong?

Sun Microsystems' Java virtual machine does not support the Compiz window manager and the Beryl one very well. It is expected better support for Compiz / Beryl will be added in future versions of their Java virtual machine. You should turn off the special effects of the Compiz / Beryl window manager before starting the <oXygen/> application or switch to other window manager.

  25.14.

When I try to drag with the mouse an unselected resource from the Project View/DITA Maps Manager, the drag never starts, it only selects the resource. I need to drag the resource again after it becomes selected. As a result any drag and drop without initial selection becomes a two step operation. How can I fix this?

This is a bug present in JVM versions prior to 1.5.0_09. This issue is fixed in 1.5.0_09 and newer versions(including 1.6). See the installation instructions for setting a specific JVM version for running the <oXygen/> application.

  25.15.

How do I set the version X of the Java virtual machine for <oXygen/> on Mac OS X?

<oXygen/> uses the first JVM from the list of preferred JVM versions set on your Mac computer that has the version number not less than 1.5.0. You can move your desired JVM version up in the preferred list by dragging it with the mouse on a higher position in the list of JVMs available from Applications -> Utilities -> Java -> Java Preferences.

  25.16.

On my Mac OS X machine when I double-click on the <oXygen/> icon the application doesn't start / gives a Segmentation fault error.

Install the latest Java update from the Apple website. If that doesn't solve the problem copy the file JavaApplicationStub from the /System/Frameworks folder to the oxygen.app/Contents/MacOS folder. For browsing the folder oxygen.app Meta + click on the <oXygen/> icon and select Show Package Contents

  25.17.

After upgrading my OS X version to 10.4.x / my <oXygen/> version to 6.x <oXygen/> is not associated to the file types XML, XSL, XSD, etc. This worked in the previous version of <oXygen/>.

The upgrade damaged the file associations in the LaunchService Database on your Mac OS X machine. Please rebuild the LaunchService Database with the following procedure. This will reset all file associations and will rescan the entire file system searching for applications that declare file associations and collecting them in a database used by Finder.

 

Procedure 25.1. Rebuild file associations of the LaunchService Database

  1. Find all the <oXygen/> installations on your hard drive.

  2. Delete them by dragging them to the Trash.

  3. Clear the Trash.

  4. Unpack the installation kit on your desktop.

  5. Copy the contents of the archive into the folder /Applications/Oxygen.

  6. Run the command

    /System/Library/Frameworks/CoreServices.framework/Frameworks/ LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user -dump

    from the Terminal.

  7. Restart Finder with

    killall Finder

    from the Terminal.

  8. Create a XML or XSD file on your desktop. It should take the <oXygen/> icon.

  9. Double click it. After accepting the confirmation dialog <oXygen/> will be start up.

  25.18.

After upgrading my Mac OS X to version 10.4.1 Tiger I am not able to set all XML files to open with <oXygen/> when I click Change All in the Get Info dialog. This worked in OS X 10.3.x.

On Mac OS X Tiger you must add an entry to the Info.plist file. Tiger was released after <oXygen/> version 6.0 so the change could not be included in the <oXygen/> 6.0 release. Please close <oXygen/>, press Meta + click on the <oXygen/> icon, select Show package contents, go to Contents, edit the Info.plist file, add the entry

    <key>CFBundleIdentifier</key>
    <string>ro.sync.exml.Oxygen</string>

and restart <oXygen/>. Select Change All in the Get Info dialog to make the association.

  25.19.

I cannot connect to a SVN repository from the Repository Browser view of SVN client. How can I find more data about the error?

First check that you entered the correct URL of the repository in the Repository Browser view. Also check that a SVN server is running on the server machine specified in the repository URL and and is accepting connections from SVN clients. You can check that the SVN server accepts connections with the command line SVN client from CollabNet.

If you try to access the repository with a svn+ssh URL also check that a SSH server is running on port 22 on the server machine specified in the URL.

If the above conditions are checked and you cannot connect to the SVN repository please generate a logging file on your computer and send the logging file to . For generating a logging file you need to create a text file called log4j.properties in the install directory with the following content:

log4j.rootCategory= debug, R2

log4j.appender.R2=org.apache.log4j.RollingFileAppender
log4j.appender.R2.File=logging.log
log4j.appender.R2.MaxFileSize=12000KB
log4j.appender.R2.MaxBackupIndex=20
log4j.appender.R2.layout=org.apache.log4j.PatternLayout
log4j.appender.R2.layout.ConversionPattern=%r %p [ %t ] %c - %m%n

Restart the application, reproduce the error, close the application and send the file logging.log generated in the install directory to .

  25.20.

What details can I add to my problem report that I enter on the Technical Support online form of the product website?

For problems like server connection error, unexpected delay while editing a document, a crash of the application, etc for which the usual details provided on the Technical Support online form are not enough you can generate an log file and attach it to the problem report. In case of crash you should also attach the crash report file generated by your operating system. For generating a logging file you need to create a text file called log4j.properties in the install directory with the following content:

  log4j.rootCategory= debug, R2
  
  log4j.appender.R2=org.apache.log4j.RollingFileAppender
  log4j.appender.R2.File=logging.log
  log4j.appender.R2.MaxFileSize=12000KB
  log4j.appender.R2.MaxBackupIndex=20
  log4j.appender.R2.layout=org.apache.log4j.PatternLayout
  log4j.appender.R2.layout.ConversionPattern=%r %p [ %t ] %c - %m%n

Restart the application, reproduce the error, close the application. The log file is called logging.log and is located in the install directory.