Technical Issues
History | Edit

This topic contains information about error messages, possible known issues, and other things that you might want to be aware of in regards to Oxygen XML Web Author.

Browser Runs Out of Memory When Trying to Edit Large Files

When Oxygen XML Web Author renders documents, it causes the browser to consume more memory than the original document size. To work with large documents, you can configure Oxygen XML Web Author to fold some of the elements by default. To do this, you need to create a custom CSS file that specifies the folding (for example, specifying that all the sections are folded by default):
section{
    -oxy-foldable:true;
    -oxy-folded: true;
    -oxy-not-foldable-child: title;
}
Note: The -oxy-foldable property does not work with elements that contain: display: inline.
To test it, you can reference the CSS file in a processing instruction at the top of the document:
<?xml-stylesheet type="text/css" href="MyCustom.css"?>

For production purposes, you may want to configure a custom framework that associates the CSS file to large XML documents.

Image Rendering Issues

If your documents contain images that are in uncommon formats, you may encounter image rendering issues in Oxygen XML Web Author. If you encounter such issues, you can try downloading a plugin hosted on GitHub called web-author-imageio-plugin, and then upload it in Oxygen XML Web Author. It adds image rendering capabilities for formats such as: cur, db, dcx, ham, ham8, hdr, icns, ico, iff, ilbm, lbm, pam, pbm, pct, pcx, pdf, pfm, pgm, pic, pict, ppm, psd, rgbe, rle, sgi, tga, tif, tiff, tpic, xyze.