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 Options → Preferences+Editor / Format / XML before opening the document. If the document is very large (above 10 MB) you should increase the memory available to <oXygen/>.

Files larger than 70 MB should not be opened in <oXygen/>for editing as this requires a very large amount of memory which exceeds the maximum amount of memory allowed for a Java process. Such files should be opened only for viewing (read-only access) 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.

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.

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/> XML Author with the author.bat script just add the parameter

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

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

Java applications can't do this. The problem is a bug in the JVM. Depending of your platform, there is information logged about what caused the crash. For Unix type systems you will get an error in the console (and for Mac OS X you may also get a report in ~/Library/Logs/CrashReporter/JavaApplicationStub.crash.log).

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 we recommend to use Java 1.6.0_01.

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.

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()

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.

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 Perspectives → Reset 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 Options → Preferences+Perspectives Layout+Use fixed layout.

Sun Microsystems' Java virtual machine does not support the Compiz window manager and the Beryl one very well. We are expecting better support for Compiz / Beryl 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.

This happens with the Sun's Java virtual machine version 1.6.0_02 and later due to a bug introduced by JVM 1.6.0_02. Please run the <oXygen/> application with a different JVM version. See the installation instructions for setting a specific JVM version for running the <oXygen/> application.

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.

<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.

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

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.

On Mac OS X Tiger you must add an entry to the Info.plist file. Tiger was released after <oXygen/> version 6.0 so we could not include the change in the 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.