More flexible tool chain selection
Are you missing a feature? Request its implementation here.
-
- Posts: 27
- Joined: Sat Jul 19, 2003 10:42 am
- Location: South Africa
- Contact:
More flexible tool chain selection
Oxy currently only allows users to select their choice of FO Processor. This is very limiting.
For example:
Xerces does not provide full support for XInclude as XPointer is not fully implemented. This means that, users wishing to use Oxy as an editor cannot use XInclude until Xerces has such support. The result is that they will use another editor. Rather than have users migrate to other tools, it would be better to let the user select the backend tool chain. Oxy can still distribute the defaults as it does today, but Oxy users will be able to change tools as required.
It would also promote Oxy's integration with other products and projects.
For example:
Xerces does not provide full support for XInclude as XPointer is not fully implemented. This means that, users wishing to use Oxy as an editor cannot use XInclude until Xerces has such support. The result is that they will use another editor. Rather than have users migrate to other tools, it would be better to let the user select the backend tool chain. Oxy can still distribute the defaults as it does today, but Oxy users will be able to change tools as required.
It would also promote Oxy's integration with other products and projects.
-
- Posts: 501
- Joined: Mon Feb 03, 2003 10:56 am
Hello Sean,
In the next release (2.0.4) we will integrate the Saxon XSL transformer. The user can choose between the Xalan and Saxon for XSLT.
We are also considering adding support for choosing the XML Parser used for validation. This will go in version 2.1.
About the XInclude: Xerces is adding supporting this feature, experimentally, starting with the version 2.5.0. (This is in the current Oxygen distribution)
In the next release (2.0.4) we will integrate the Saxon XSL transformer. The user can choose between the Xalan and Saxon for XSLT.
We are also considering adding support for choosing the XML Parser used for validation. This will go in version 2.1.
About the XInclude: Xerces is adding supporting this feature, experimentally, starting with the version 2.5.0. (This is in the current Oxygen distribution)
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