Working directory for Transformation Scenario
Are you missing a feature? Request its implementation here.
-
- Posts: 2
- Joined: Mon Jul 31, 2006 11:42 am
- Location: Bratislava, Slovakia
- Contact:
Working directory for Transformation Scenario
Hello,
I am writing some XSLT 2.0 transforms that reference local files and generate multiple output documents. Before, when invoking Saxon from command line, I was using paths relative to the directory where I ran the processor. The advantage of having a working directory and not using absolute paths is that your stylesheets can be executed without change on both Unix and Windows systems.
Would it be possible to add a working directory setting for Transformation Scenarios, so that the directory paths used in XSLT are relative to the directory you configure?
Best regards,
Boris
I am writing some XSLT 2.0 transforms that reference local files and generate multiple output documents. Before, when invoking Saxon from command line, I was using paths relative to the directory where I ran the processor. The advantage of having a working directory and not using absolute paths is that your stylesheets can be executed without change on both Unix and Windows systems.
Would it be possible to add a working directory setting for Transformation Scenarios, so that the directory paths used in XSLT are relative to the directory you configure?
Best regards,
Boris
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Post by sorin_ristache »
Hello,
The transformation scenario does not restrict you to absolute paths. A relative path in the scenario specified for the input file, the output file or for an additional XSLT stylesheet is resolved relative to the URL of the document to which the scenario is associated, that is the currently edited document when the scenario is executed. This possibility to use relative paths together with the macros available from the Insert macros button present for many fields of the scenario make the scenario independent of the location of the document associated with the scenario. This enables you to export the scenario on one platform/computer, import it on another one and execute it without any change to the scenario parameters.
Relative paths in the XSLT stylesheet itself are resolved relative to the base URI of the element containing the relative path. This is required by the XSLT specification. Usually that base URI is the URI of the stylesheet.
Regards,
Sorin
The transformation scenario does not restrict you to absolute paths. A relative path in the scenario specified for the input file, the output file or for an additional XSLT stylesheet is resolved relative to the URL of the document to which the scenario is associated, that is the currently edited document when the scenario is executed. This possibility to use relative paths together with the macros available from the Insert macros button present for many fields of the scenario make the scenario independent of the location of the document associated with the scenario. This enables you to export the scenario on one platform/computer, import it on another one and execute it without any change to the scenario parameters.
Relative paths in the XSLT stylesheet itself are resolved relative to the base URI of the element containing the relative path. This is required by the XSLT specification. Usually that base URI is the URI of the stylesheet.
Regards,
Sorin
-
- Posts: 2
- Joined: Mon Jul 31, 2006 11:42 am
- Location: Bratislava, Slovakia
- Contact:
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ 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