Where is oxygen.ini
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Post by sorin_ristache »
Hello,
What kind of extension functions do you try to configure? If you want to set extension functions for an XSLT transformation or an XQuery one you should do that in the Extensions dialog opened by pressing the Extensions button of the transformation scenario edit dialog.
The oxygen.ini file was replaced by oxygen.vmoptions because we changed the installer application.
Regards,
Sorin
What kind of extension functions do you try to configure? If you want to set extension functions for an XSLT transformation or an XQuery one you should do that in the Extensions dialog opened by pressing the Extensions button of the transformation scenario edit dialog.
The oxygen.ini file was replaced by oxygen.vmoptions because we changed the installer application.
Regards,
Sorin
-
- Posts: 3
- Joined: Thu Oct 25, 2007 1:53 pm
Was looking for oxygen.ini too, and finally found the answer in this post.
My reason for adding extension paths to the startup is to avoid getting error messages in the XSLT editor. If I add the extension path in the transformation configuration the transformation will find the extension, but the the XSLT window shows a red underline where the extension functions are used. I have only tested this with Saxon.
The documentation should be updated to correct this - would have saved me some time.
The best solution is of course to be able to use the transformation configuration for this without getting the incorrect error in the automatic validation.
Best regards,
Trond
My reason for adding extension paths to the startup is to avoid getting error messages in the XSLT editor. If I add the extension path in the transformation configuration the transformation will find the extension, but the the XSLT window shows a red underline where the extension functions are used. I have only tested this with Saxon.
The documentation should be updated to correct this - would have saved me some time.
The best solution is of course to be able to use the transformation configuration for this without getting the incorrect error in the automatic validation.
Best regards,
Trond
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Post by sorin_ristache »
You have to create a validation scenario for the XSLT stylesheet, set the extension jar there and check the Validate as you type checkbox to apply the scenario also for the background validation.trondaal wrote:If I add the extension path in the transformation configuration the transformation will find the extension, but the the XSLT window shows a red underline where the extension functions are used.
We updated the documentation. You have to set the parameter in the file oxygen.vmoptions instead of oxygen.ini because we changed the installer application.trondaal wrote:The documentation should be updated to correct this - would have saved me some time.
Regards,
Sorin
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service