Hi Sean,

Dan's suggestion with ulimit was an workaround that worked for us on Mac OS X. You may try a larger parameter for ulimit.

I do not know what parser they are using, it may be Xerces but a different version. We are using the latest version.

Best Regards,
George

Sean, Sure it is a Xerces problem, please review my first post. This is a Xerces problem, we made a test showing that this problem appears on a simple parsing of a file that includes a lot of external entities and post this in a bugzilla entry for Xerces: http://nagoya.apache.org/bugzilla/show_bug.c...

Hi Sean,

Have you tried running that command as root ?

Best Regards,
George

Hi Sean, We also got into this problem on Mac OS X trying to edit the oxygen user guide :wink: . This is a Xerces problem, we made a test showing that this problem appears on a simple parsing of a file that includes a lot of external entities and post this in a bugzilla entry for Xerces: http://nago...

Dear Holger, Please do not use file when you specify a relative location. Imagine that you publish your documents on a web server, there you have http instead of file and I guess you expect the relative reference to work also there. Try with xsi:noNamespaceSchemaLocation="../schema/reportDefini...

Hi Sean,

Try to set the com.oxygenxml.editor.plugins.dir to the plugin directory in your start script: We will release at the beginning of next week the 2.0.4 version which should work without any changes.

Best Regards,
George

Hi Tobias,

Please get the http://www.oxygenxml.com/update/oxygen.jar and replace the one from the 2.0.4 beta1 plugin. This should work with Xalan extensions - at least it worked in our tests. Let us know if it works also for you.

Best Regards,
George

Hi Olivier, Oxygen has a stronger dependence on the XML parser, I guess this is something normal for an XML editor. We always ship the latest version of Xerces at the moment of release, that is oXygen 2.0.3 comes with Xerces 2.5.0. There were some changes indeed between Xerces 2.4.0 and Xerces 2.5.0...

Hi Tobias,

We tested the latest development version and it works with Java 1.3... anyway we will look closer into this and provide a solution to this problem in the next release planned for the beginning of next week. Watch this forum entry for updates.

Best Regards,
George

Hi Olivier, Oxygen does not depend on a specific version of Xalan, it loads it through JAXP so you can replace the xalan.jar from the plugin lib directory with the 2.5.0 version. Let us know if you get the same problem when putting Xalan 2.5.0 both in the endorsed directory and in the plugin lib. Th...

Hi, btw does oxygen work for eclipse 3.0, bcoz it doesnt seem to work for me... We tested it without problems with Eclipse 3.0 M1, M2 and M3. Please provide more information about this, like Eclipse version/build, platform, error message, exception trace if any, a description of what happens, etc. B...

Dear Olivier, Please try to see if you get the same problem with the latest available version: http://www.oxygenxml.com/update/com.oxygenxml.editor_2.0.4.beta1.zip If you still have problems then please let us know what eclipse version are you using and on what platform. Also it will be interesting ...

Hi Ross, In order not to get these errors you can either remove the well formedness check when documents are saved (Windows->Preferences--oXygen->Check wellformedness on save) or you can use the "Clear validation markers" from the oXygen toolbar or XML menu. There should not be signifiant ...

Dear Tobias, The difference between Java 1.3 and Java 1.4 is that the later comes with a Xalan distribution. Thus the Xalan shipped with the JVM gets used and it is loaded with the system class loader while the extensions are loaded with the plugin class loader. We made some changes in the current d...

Hi, got the temp license and moved the license.key file to the place specified. Please refer to the registration message, it says to place the license.zip not the license.key file in the oXygen plugin directory. Please do not extract the license.key out of the zip, use license.zip as it is. Best Reg...

Hi,

The "light indenting" option is available on a selection from the contextual menu. It is the last option called "Indent selection".

Best Regards,
George

Hi, We do some content generation only that we do not take any guess on choices. We generate only the required content if it is possible to generate it without ambiguity. For instance if you create a new XML document and specify the personal.xsd schema from the samples directory and select personnel...

Dear Ivan, Please follow the following simple steps: - get the eclipse plugin archive (I suppose you already have it) - extract it in the eclipse/plugins folder - get an oXygen license (you can request a trial license from the registration page for instance) - copy the license.zip file in the oxygen...

Hi,

There should be an oXygen XSL editor.
We cannot reproduce this problem on any of our platforms.

Regards,
George

Hi, autocompletion is nice but has a few missing attribute for some nodes type The content assistant offers only the valid entries on the given context. For instance the ref attribute cannot appear in a top level element while it is allowed in a local element declaration. If you think oXygen does no...

Hi, Oxygen offers support for XML Schema authoring offering an XML Schema text editor with context sensitive content assistant and XML Schema validation. The project stucture is logical and has no link with the disk structure. The import directory operation is a shortcut for adding a logical folder ...

Hi,

We will look into this but you might consider printing the PDF version of the help that is the user guide: http://www.oxygenxml.com/OxygenUserGuide.zip.

Best Regards,
George

Ian, AFAIK there are no font problems when using Java 1.3.1, therefore you might consider configuring oXygen to use Java 1.3.1 instead of Java 1.4 (the default behaviour). To do this you should edit the Info.plist file and look for the following entries: <key>JVMVersion</key> <string>1.3+</string> a...

Hi Ian, We cannot reproduce this problem. Do you get this behaviour in a consistent way ? Please verify and let us know. Also if you can do a very simple test eventually on the samples/sample.xpr project so we can reproduce the same steps that will be helpful. Best Regards, George P.S. The titles ar...

Dear Ian,

There are some problems with the fonts since Apple's Java 1.4, please see the font problems on OS X topic for more details and workarounds.

Best Regards,
George

Hi, You can do this from the standalone version. There you have more alternatives, the simplest one is to use the "Save structure" action. You can find this near the "Learn document structure" on the toolbar. This will save a DTD and will also add the DOCTYPE declaration in the e...

Hi,

After we analysed the trace it seems that the only problem is in the configuration files. Please go into your home folder and delete the com.oxygenxml directory then start oXygen.

Let us know how is going.

Best Regards,
George

Hi,

Please make sure you place your permanent license file as license.zip in the plugin directory where there is also a file called "put-license-file-here.txt". If you still have problems with this send us the license file to support@oxygenxml.com.

Best Regards,
George

Hi, The current solution is to use a CDATA section to mark the programlisting content, something like: <programlisting><![CDATA[ your program listing here... ]]> </programlisting> An alternative is to use xml:space="preserve" attribute on the programlisting element but unfortunatelly Docbo...

Hi,

Have a look at Window/Preferences - Workbench/File Associations. There you should be able to define new extensions and configure what editors should be available for each extension.

Best Regards,
George