XML AUTHOR + Docbook5: Problems with using custom HTML chunk scenarios (parameters conflict with customization layer)
I have been having a persistent problem with doing HTML-chunk transformations with Docbook 5 and Oxygen 12. I think I had similar problems with Oxygen 11 too. I wrote a xsl customization layer rjstyle.xsl. Initially what I thought I could do was to duplicate the HTML-chunk scenario and change the XSL URL to rjstyle.xsl. But I discover that a few of my parameter settings are not working. That is because the parameter values I am giving in rjstyle.xsl are differing from the preset parameters in Oxygen's HTML chunk scenarios. Oxygen's parameter settings are overriding my own in rjstyle.xsl. QUESTION: Is there a way to tell your Edit Scenario dialog for the parameter settings in rjstyle.xsl to override whatever presets Oyxgen put into its out-of-the-box Docbook scenarios? The answer would seem to be to create a new scenario from scratch. However, whenever I do that, I seem to receive a lot of compiler errors. To give an example of what I mean by errors: 1)Engine name: Saxon6.5.5 Severity: error Description: ch01.html (Access is denied) Engine name: Saxon6.5.5 Severity: error Description: The system cannot find the path specified (With both types of errors, it works fine when I use the out-of-the-box docbook chunk scenarios. Also, I have torn out all the excess stuff from rjstyle.xsl except for: <xsl:import href="../../../1latest/docbook-xsl-1.76.1/html/chunk.xsl"/> 2)non-validating XHTML code. It won't show in the browser. (this is less common than the above two; might be a fluke with my current project). If I use Oxygen's chunk XSL defaults and add rjstyle.xsl as an additional XSLT stylesheet (an option in the Edit Scenario dialog), I get an error: SystemID: I:\My Documents\My Dropbox\xml\testbug2\index2.xml Engine name: Saxon6.5.5 Severity: error Description: Cannot apply cascading transformation. Reason: org.xml.sax.SAXParseException: A well-formed document requires a root element. One of the complicating factors here is that the Edit Scenario dialog (with 3 tags) has a lot of options. It's good that the Oxygen team can compress so many options into one dialog; on the other hand, it's hard to transfer settings into a New Scenario and be certain you have copied everything. QUESTION: Do you have any hints about creating Docbook transformations from scratch that avoid the Access is denied and system cannot find the path specified errors? I realize that I am not giving you enough information about my specific project. But I suspect that you may have some general ideas about what is wrong (besides, my brain is growing weary). By the way, you might be wondering why I am not content using an out-of-the-box chunk scenario. 1)I find it cumbersome to edit the parameter list (and don't have a way to save my settings in an easy-to-read format) and 2)It's easier for me to hard code the latest docbook xsl in a user directory rather than a system directory. -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info
Hi Robert, In the forums or somewhere I mentioned that I would like to have a generic ant-based transformation scenario (like the DITA one but generic and customizable). I believe the Oxygen folks replied that this is a planned feature. What I think is really needed is an easy way to create transformation scenarios that invoke an arbitrary executable (ant, maven, make, a script, whatever your build machine uses) and surface some command line options as check boxes, radio buttons, and text fields. The current DocBook transformation scenarios are good for demoing DocBook functionality, but in a production environment you usually wrap the build process in some other script. Often your build will do several passes on the document, generate olink databases, copy resources into place, zip/jar/war up the output, deploy it to nexus, and so on. You don't want all that build logic tied in to the editor but you do want an easy way to kick it off from the editor for local builds. For now, you can write a plugin that adds menu items and associated actions that kick off the external processes. I've experimented with that some with help from Oxygen support, but was having problems with the UI locking up until the ant process completed and I haven't come back to it yet. David
-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user- bounces@oxygenxml.com] On Behalf Of Robert Nagle Sent: Sunday, November 28, 2010 3:28 PM To: oxygen-user@oxygenxml.com Subject: [oXygen-user] XML AUTHOR + Docbook5: Problems with using custom HTML chunk scenarios (parameters conflict with customization layer)
I have been having a persistent problem with doing HTML-chunk transformations with Docbook 5 and Oxygen 12. I think I had similar problems with Oxygen 11 too.
I wrote a xsl customization layer rjstyle.xsl.
Initially what I thought I could do was to duplicate the HTML-chunk scenario and change the XSL URL to rjstyle.xsl. But I discover that a few of my parameter settings are not working. That is because the parameter values I am giving in rjstyle.xsl are differing from the preset parameters in Oxygen's HTML chunk scenarios. Oxygen's parameter settings are overriding my own in rjstyle.xsl.
QUESTION: Is there a way to tell your Edit Scenario dialog for the parameter settings in rjstyle.xsl to override whatever presets Oyxgen put into its out-of-the-box Docbook scenarios?
The answer would seem to be to create a new scenario from scratch. However, whenever I do that, I seem to receive a lot of compiler errors.
To give an example of what I mean by errors:
1)Engine name: Saxon6.5.5 Severity: error Description: ch01.html (Access is denied)
Engine name: Saxon6.5.5 Severity: error Description: The system cannot find the path specified
(With both types of errors, it works fine when I use the out-of-the-box docbook chunk scenarios. Also, I have torn out all the excess stuff from rjstyle.xsl except for: <xsl:import href="../../../1latest/docbook-xsl- 1.76.1/html/chunk.xsl"/>
2)non-validating XHTML code. It won't show in the browser. (this is less common than the above two; might be a fluke with my current project).
If I use Oxygen's chunk XSL defaults and add rjstyle.xsl as an additional XSLT stylesheet (an option in the Edit Scenario dialog), I get an error:
SystemID: I:\My Documents\My Dropbox\xml\testbug2\index2.xml Engine name: Saxon6.5.5 Severity: error Description: Cannot apply cascading transformation. Reason: org.xml.sax.SAXParseException: A well-formed document requires a root element.
One of the complicating factors here is that the Edit Scenario dialog (with 3 tags) has a lot of options. It's good that the Oxygen team can compress so many options into one dialog; on the other hand, it's hard to transfer settings into a New Scenario and be certain you have copied everything.
QUESTION: Do you have any hints about creating Docbook transformations from scratch that avoid the Access is denied and system cannot find the path specified errors?
I realize that I am not giving you enough information about my specific project. But I suspect that you may have some general ideas about what is wrong (besides, my brain is growing weary).
By the way, you might be wondering why I am not content using an out-of-the-box chunk scenario. 1)I find it cumbersome to edit the parameter list (and don't have a way to save my settings in an easy-to-read format) and 2)It's easier for me to hard code the latest docbook xsl in a user directory rather than a system directory.
-- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi David, I agree that as the need for output customization grows the process of generating output tends to become automated process with many and more complex processing steps. About the UI blocking when the ANT process gets started, you will probably need a new Java thread started and controlling the ANT process and leave the UI continue to work. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 11/30/2010 7:18 PM, Cramer, David W (David) wrote:
Hi Robert, In the forums or somewhere I mentioned that I would like to have a generic ant-based transformation scenario (like the DITA one but generic and customizable). I believe the Oxygen folks replied that this is a planned feature. What I think is really needed is an easy way to create transformation scenarios that invoke an arbitrary executable (ant, maven, make, a script, whatever your build machine uses) and surface some command line options as check boxes, radio buttons, and text fields.
The current DocBook transformation scenarios are good for demoing DocBook functionality, but in a production environment you usually wrap the build process in some other script. Often your build will do several passes on the document, generate olink databases, copy resources into place, zip/jar/war up the output, deploy it to nexus, and so on. You don't want all that build logic tied in to the editor but you do want an easy way to kick it off from the editor for local builds.
For now, you can write a plugin that adds menu items and associated actions that kick off the external processes. I've experimented with that some with help from Oxygen support, but was having problems with the UI locking up until the ant process completed and I haven't come back to it yet.
David
-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user- bounces@oxygenxml.com] On Behalf Of Robert Nagle Sent: Sunday, November 28, 2010 3:28 PM To: oxygen-user@oxygenxml.com Subject: [oXygen-user] XML AUTHOR + Docbook5: Problems with using custom HTML chunk scenarios (parameters conflict with customization layer)
I have been having a persistent problem with doing HTML-chunk transformations with Docbook 5 and Oxygen 12. I think I had similar problems with Oxygen 11 too.
I wrote a xsl customization layer rjstyle.xsl.
Initially what I thought I could do was to duplicate the HTML-chunk scenario and change the XSL URL to rjstyle.xsl. But I discover that a few of my parameter settings are not working. That is because the parameter values I am giving in rjstyle.xsl are differing from the preset parameters in Oxygen's HTML chunk scenarios. Oxygen's parameter settings are overriding my own in rjstyle.xsl.
QUESTION: Is there a way to tell your Edit Scenario dialog for the parameter settings in rjstyle.xsl to override whatever presets Oyxgen put into its out-of-the-box Docbook scenarios?
The answer would seem to be to create a new scenario from scratch. However, whenever I do that, I seem to receive a lot of compiler errors.
To give an example of what I mean by errors:
1)Engine name: Saxon6.5.5 Severity: error Description: ch01.html (Access is denied)
Engine name: Saxon6.5.5 Severity: error Description: The system cannot find the path specified
(With both types of errors, it works fine when I use the out-of-the-box docbook chunk scenarios. Also, I have torn out all the excess stuff from rjstyle.xsl except for: <xsl:import href="../../../1latest/docbook-xsl- 1.76.1/html/chunk.xsl"/>
2)non-validating XHTML code. It won't show in the browser. (this is less common than the above two; might be a fluke with my current project).
If I use Oxygen's chunk XSL defaults and add rjstyle.xsl as an additional XSLT stylesheet (an option in the Edit Scenario dialog), I get an error:
SystemID: I:\My Documents\My Dropbox\xml\testbug2\index2.xml Engine name: Saxon6.5.5 Severity: error Description: Cannot apply cascading transformation. Reason: org.xml.sax.SAXParseException: A well-formed document requires a root element.
One of the complicating factors here is that the Edit Scenario dialog (with 3 tags) has a lot of options. It's good that the Oxygen team can compress so many options into one dialog; on the other hand, it's hard to transfer settings into a New Scenario and be certain you have copied everything.
QUESTION: Do you have any hints about creating Docbook transformations from scratch that avoid the Access is denied and system cannot find the path specified errors?
I realize that I am not giving you enough information about my specific project. But I suspect that you may have some general ideas about what is wrong (besides, my brain is growing weary).
By the way, you might be wondering why I am not content using an out-of-the-box chunk scenario. 1)I find it cumbersome to edit the parameter list (and don't have a way to save my settings in an easy-to-read format) and 2)It's easier for me to hard code the latest docbook xsl in a user directory rather than a system directory.
-- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Ok, thanks Radhu. I'll try that (and probably be back in touch) when I get around to this piece again. In the mean time I've been busy modernizing other parts of our infrastructure to take advantage things like olinking, which oxygen supports so well. I'm getting by with external tools for now, but will want a nice menu or dialog for when I roll the new system out to other writers. David
-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user- bounces@oxygenxml.com] On Behalf Of Radu Coravu Sent: Thursday, December 02, 2010 2:12 AM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] XML AUTHOR + Docbook5: Problems with using custom HTML chunk scenarios (parameters conflict with customization layer)
Hi David,
I agree that as the need for output customization grows the process of generating output tends to become automated process with many and more complex processing steps.
About the UI blocking when the ANT process gets started, you will probably need a new Java thread started and controlling the ANT process and leave the UI continue to work.
Regards, Radu
Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
I have tried to force the XSLT debugger to stay on the toolbar (setting in in "Window" and in "Configure Toolbar"). Every time I return to the XML editor window, the debugger disappears from the toolbar. What am I doing wrong? Thanks, Mark
Hi Mark, So, if I understand correctly, you want to keep the Debugger toolbars(Debugger status, control and engine) when switching to the XML perspective? These toolbars are only available in the XSLT Debugger perspective. If you need these toolbars when editing, it is simpler to stay in the XSLT Debugger perspective and just make visible the other toolbars(Validate, Transformation, etc) and views(Project, Outliner, etc) that you need. You can show any view from the main menu: Window -> Show View -> ... When switching the perspective, the layout of the previous perspective(toolbars and views) is saved so you only have to configure it once. Let me know if I misunderstood and you were trying to achieve something else. Regards, Adrian Adrian Buza oXygen XML Editor and Author support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com http://www.oxygenxml.com Mark wrote:
I have tried to force the XSLT debugger to stay on the toolbar (setting in in "Window" and in "Configure Toolbar"). Every time I return to the XML editor window, the debugger disappears from the toolbar. What am I doing wrong?
Thanks, Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello Adrian, Thanks for your answer. Not quite: I want Perspective to appear in the menu as in earlier versions. I am using <oXygen/> XML Editor 12.0, build 2010091411 on Windows Vista. I have not set any options differently than I did for version 11. Oxygen opens in the editor. Unlike earlier versions, Perspective does not appear in the top menu, even though it is checked in the Configure Toolbars dialog. There are only two ways I can open the debugger: 1. Doing this makes the icons appear on the right end of the toolbar initially. If I left-click on the toolbar itself, the dropdown always shows Perspective without a yellow box and checkmark. If I click on the dropdown Perspective, the four perspective icons appear at the right of the toolbar, just after the Search icons. When I click on the debugger icon, the debugger opens and the four perspective icons immediately shift to the far left. When I finish with the debugger and click on the editor icon, the four icons disappear. Clicking on the toolbar again shows Perspective in the dropdown again without a yellow box and checkmark. The yellow box and checkmark remain only so long as the debugger is open. 2. Doing this makes the icons appear on the left end of the toolbar initially. Or, if from the editor, I click on Window->Open Perspective->XSLT Debugger, the four icons appear at the left end of the toolbar. In either case, clicking on the editor icon causes the icons for the other perspectives to disappear. In no case does the Perspective menu item ever appear in the top menu (as it did in earlier versions). What I have is: File Edit Find Project Options Tools Document Window Help. I use the editor and the debugger extensively when I am doing development and am finding this situation very awkward and clumsy. Hope this is clearer, Mark -----Original Message----- From: Adrian Buza Sent: Monday, December 13, 2010 12:14 AM To: Mark Cc: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] Perspective Hi Mark, So, if I understand correctly, you want to keep the Debugger toolbars(Debugger status, control and engine) when switching to the XML perspective? These toolbars are only available in the XSLT Debugger perspective. If you need these toolbars when editing, it is simpler to stay in the XSLT Debugger perspective and just make visible the other toolbars(Validate, Transformation, etc) and views(Project, Outliner, etc) that you need. You can show any view from the main menu: Window -> Show View -> ... When switching the perspective, the layout of the previous perspective(toolbars and views) is saved so you only have to configure it once. Let me know if I misunderstood and you were trying to achieve something else. Regards, Adrian Adrian Buza oXygen XML Editor and Author support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com http://www.oxygenxml.com Mark wrote:
I have tried to force the XSLT debugger to stay on the toolbar (setting in in "Window" and in "Configure Toolbar"). Every time I return to the XML editor window, the debugger disappears from the toolbar. What am I doing wrong?
Thanks, Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Mark, "Perspective" was both a a menu and a toolbar in v11.2. In v12 the actions from the "Perspective" menu were moved to the "Window" menu. The "Perspective" toolbar remained in v12. "Configure Toolbars" is used(as the name suggests) only for toolbars. It's true that some of the toolbar names there probably mirror menu names but that's just a coincidence, they are not the same. I'm guessing that what happens is that there are too many items in the toolbar on a row and they cannot all fit on that row so they get "compacted" and a drop down arrow appears and hides the toolbar icons that could not be fit. This way of cascading toolbars is a fallback for toolbars that won't fit so it's not exactly user friendly. Simply hide unused toolbars or spread them across several rows to resolve this. A screenshot would clarify the situation even better. If possible then please send one to support@oxygenxml.com if you want to keep it off the user-list. Adrian Buza oXygen XML Editor and Author support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com http://www.oxygenxml.com Mark wrote:
Hello Adrian, Thanks for your answer. Not quite: I want Perspective to appear in the menu as in earlier versions.
I am using <oXygen/> XML Editor 12.0, build 2010091411 on Windows Vista. I have not set any options differently than I did for version 11. Oxygen opens in the editor. Unlike earlier versions, Perspective does not appear in the top menu, even though it is checked in the Configure Toolbars dialog. There are only two ways I can open the debugger:
1. Doing this makes the icons appear on the right end of the toolbar initially. If I left-click on the toolbar itself, the dropdown always shows Perspective without a yellow box and checkmark. If I click on the dropdown Perspective, the four perspective icons appear at the right of the toolbar, just after the Search icons. When I click on the debugger icon, the debugger opens and the four perspective icons immediately shift to the far left. When I finish with the debugger and click on the editor icon, the four icons disappear. Clicking on the toolbar again shows Perspective in the dropdown again without a yellow box and checkmark. The yellow box and checkmark remain only so long as the debugger is open.
2. Doing this makes the icons appear on the left end of the toolbar initially. Or, if from the editor, I click on Window->Open Perspective->XSLT Debugger, the four icons appear at the left end of the toolbar.
In either case, clicking on the editor icon causes the icons for the other perspectives to disappear. In no case does the Perspective menu item ever appear in the top menu (as it did in earlier versions). What I have is: File Edit Find Project Options Tools Document Window Help.
I use the editor and the debugger extensively when I am doing development and am finding this situation very awkward and clumsy.
Hope this is clearer, Mark
-----Original Message----- From: Adrian Buza Sent: Monday, December 13, 2010 12:14 AM To: Mark Cc: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] Perspective
Hi Mark,
So, if I understand correctly, you want to keep the Debugger toolbars(Debugger status, control and engine) when switching to the XML perspective? These toolbars are only available in the XSLT Debugger perspective. If you need these toolbars when editing, it is simpler to stay in the XSLT Debugger perspective and just make visible the other toolbars(Validate, Transformation, etc) and views(Project, Outliner, etc) that you need. You can show any view from the main menu: Window -> Show View -> ... When switching the perspective, the layout of the previous perspective(toolbars and views) is saved so you only have to configure it once.
Let me know if I misunderstood and you were trying to achieve something else.
Regards, Adrian
Adrian Buza oXygen XML Editor and Author support
Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com http://www.oxygenxml.com
Mark wrote:
I have tried to force the XSLT debugger to stay on the toolbar (setting in in "Window" and in "Configure Toolbar"). Every time I return to the XML editor window, the debugger disappears from the toolbar. What am I doing wrong?
Thanks, Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi Robert, If I were you I'd start by duplicating the read-only "Docbook HTML - Chunk" transformation scenario, then press the "Parameters" button and add/remove/edit my custom parameter values. There is nothing stopping you to modify the parameters Oxygen sends by default to the stylesheet. When you look in the parameters list from the scenario edit dialog only the "bolded" parameter entries get transmitted to the XSLs. All the others represent the default values and are not sent to the XSL. But, nonetheless, if you create a new transformation scenario: The error that you get seems to indicate that the XSLT processor cannot create the HTML files in the chunk output directory. So a very important XSLT parameter which you must set in the Oxygen Scenario Edit Dialog "Parameters" list is the "base.dir" parameter. This directory points to the place where the HTML output will be set. If this parameter is not set (which is probably your case) the HTML output will be relative to the place where the XSL stylesheets are located (probably in C:\Program Files\...OXYGEN_INSTALL_DIR....) which most of the times is a read-only location. You should best set the value of "base.dir" to: ${cfd}/chunks/ this value will be automatically expanded to a "chunks" directory in the directory where the source XML file is located. This is the default value which is set in the Oxygen default "Docbook HTML - Chunk" read-only scenario. Adding your "rjstyle.xsl" as an additional "cascading" stylesheet in the transformation scenario is not a good idea because: The cascade added XSLT stylesheets are applied on the output generated by the default specified stylesheet. So your XSLT would be applied on the HTML files which were created by the default XSLT. In this case the problem is worse because if you have chunking then Oxygen really does not know where the first stylesheet has generated the HTML content. Hope this helps. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 11/28/2010 11:27 PM, Robert Nagle wrote:
I have been having a persistent problem with doing HTML-chunk transformations with Docbook 5 and Oxygen 12. I think I had similar problems with Oxygen 11 too.
I wrote a xsl customization layer rjstyle.xsl.
Initially what I thought I could do was to duplicate the HTML-chunk scenario and change the XSL URL to rjstyle.xsl. But I discover that a few of my parameter settings are not working. That is because the parameter values I am giving in rjstyle.xsl are differing from the preset parameters in Oxygen's HTML chunk scenarios. Oxygen's parameter settings are overriding my own in rjstyle.xsl.
QUESTION: Is there a way to tell your Edit Scenario dialog for the parameter settings in rjstyle.xsl to override whatever presets Oyxgen put into its out-of-the-box Docbook scenarios?
The answer would seem to be to create a new scenario from scratch. However, whenever I do that, I seem to receive a lot of compiler errors.
To give an example of what I mean by errors:
1)Engine name: Saxon6.5.5 Severity: error Description: ch01.html (Access is denied)
Engine name: Saxon6.5.5 Severity: error Description: The system cannot find the path specified
(With both types of errors, it works fine when I use the out-of-the-box docbook chunk scenarios. Also, I have torn out all the excess stuff from rjstyle.xsl except for: <xsl:import href="../../../1latest/docbook-xsl-1.76.1/html/chunk.xsl"/>
2)non-validating XHTML code. It won't show in the browser. (this is less common than the above two; might be a fluke with my current project).
If I use Oxygen's chunk XSL defaults and add rjstyle.xsl as an additional XSLT stylesheet (an option in the Edit Scenario dialog), I get an error:
SystemID: I:\My Documents\My Dropbox\xml\testbug2\index2.xml Engine name: Saxon6.5.5 Severity: error Description: Cannot apply cascading transformation. Reason: org.xml.sax.SAXParseException: A well-formed document requires a root element.
One of the complicating factors here is that the Edit Scenario dialog (with 3 tags) has a lot of options. It's good that the Oxygen team can compress so many options into one dialog; on the other hand, it's hard to transfer settings into a New Scenario and be certain you have copied everything.
QUESTION: Do you have any hints about creating Docbook transformations from scratch that avoid the Access is denied and system cannot find the path specified errors?
I realize that I am not giving you enough information about my specific project. But I suspect that you may have some general ideas about what is wrong (besides, my brain is growing weary).
By the way, you might be wondering why I am not content using an out-of-the-box chunk scenario. 1)I find it cumbersome to edit the parameter list (and don't have a way to save my settings in an easy-to-read format) and 2)It's easier for me to hard code the latest docbook xsl in a user directory rather than a system directory.
Radu, a followup. I just wanted to report my delight upon learning that your suggestion worked perfectly. I used a totally blank scenario and set the parameter of "base.dir" to: ${cfd}/chunks/ did the job. It is much easier to set the path using the alias in oxygen than to have to hard code it with a real path in the stylesheet. Everything is ok now. Thanks. Robert On Thu, Dec 2, 2010 at 2:06 AM, Radu Coravu <radu_coravu@sync.ro> wrote:
Hi Robert,
If I were you I'd start by duplicating the read-only "Docbook HTML - Chunk" transformation scenario, then press the "Parameters" button and add/remove/edit my custom parameter values. There is nothing stopping you to modify the parameters Oxygen sends by default to the stylesheet. When you look in the parameters list from the scenario edit dialog only the "bolded" parameter entries get transmitted to the XSLs. All the others represent the default values and are not sent to the XSL.
But, nonetheless, if you create a new transformation scenario: The error that you get seems to indicate that the XSLT processor cannot create the HTML files in the chunk output directory. So a very important XSLT parameter which you must set in the Oxygen Scenario Edit Dialog "Parameters" list is the "base.dir" parameter. This directory points to the place where the HTML output will be set. If this parameter is not set (which is probably your case) the HTML output will be relative to the place where the XSL stylesheets are located (probably in C:\Program Files\...OXYGEN_INSTALL_DIR....) which most of the times is a read-only location.
You should best set the value of "base.dir" to: ${cfd}/chunks/
this value will be automatically expanded to a "chunks" directory in the directory where the source XML file is located. This is the default value which is set in the Oxygen default "Docbook HTML - Chunk" read-only scenario.
Adding your "rjstyle.xsl" as an additional "cascading" stylesheet in the transformation scenario is not a good idea because: The cascade added XSLT stylesheets are applied on the output generated by the default specified stylesheet. So your XSLT would be applied on the HTML files which were created by the default XSLT. In this case the problem is worse because if you have chunking then Oxygen really does not know where the first stylesheet has generated the HTML content.
Hope this helps.
Regards, Radu
Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 11/28/2010 11:27 PM, Robert Nagle wrote:
I have been having a persistent problem with doing HTML-chunk transformations with Docbook 5 and Oxygen 12. I think I had similar problems with Oxygen 11 too.
I wrote a xsl customization layer rjstyle.xsl.
Initially what I thought I could do was to duplicate the HTML-chunk scenario and change the XSL URL to rjstyle.xsl. But I discover that a few of my parameter settings are not working. That is because the parameter values I am giving in rjstyle.xsl are differing from the preset parameters in Oxygen's HTML chunk scenarios. Oxygen's parameter settings are overriding my own in rjstyle.xsl.
QUESTION: Is there a way to tell your Edit Scenario dialog for the parameter settings in rjstyle.xsl to override whatever presets Oyxgen put into its out-of-the-box Docbook scenarios?
The answer would seem to be to create a new scenario from scratch. However, whenever I do that, I seem to receive a lot of compiler errors.
To give an example of what I mean by errors:
1)Engine name: Saxon6.5.5 Severity: error Description: ch01.html (Access is denied)
Engine name: Saxon6.5.5 Severity: error Description: The system cannot find the path specified
(With both types of errors, it works fine when I use the out-of-the-box docbook chunk scenarios. Also, I have torn out all the excess stuff from rjstyle.xsl except for: <xsl:import href="../../../1latest/docbook-xsl-1.76.1/html/chunk.xsl"/>
2)non-validating XHTML code. It won't show in the browser. (this is less common than the above two; might be a fluke with my current project).
If I use Oxygen's chunk XSL defaults and add rjstyle.xsl as an additional XSLT stylesheet (an option in the Edit Scenario dialog), I get an error:
SystemID: I:\My Documents\My Dropbox\xml\testbug2\index2.xml Engine name: Saxon6.5.5 Severity: error Description: Cannot apply cascading transformation. Reason: org.xml.sax.SAXParseException: A well-formed document requires a root element.
One of the complicating factors here is that the Edit Scenario dialog (with 3 tags) has a lot of options. It's good that the Oxygen team can compress so many options into one dialog; on the other hand, it's hard to transfer settings into a New Scenario and be certain you have copied everything.
QUESTION: Do you have any hints about creating Docbook transformations from scratch that avoid the Access is denied and system cannot find the path specified errors?
I realize that I am not giving you enough information about my specific project. But I suspect that you may have some general ideas about what is wrong (besides, my brain is growing weary).
By the way, you might be wondering why I am not content using an out-of-the-box chunk scenario. 1)I find it cumbersome to edit the parameter list (and don't have a way to save my settings in an easy-to-read format) and 2)It's easier for me to hard code the latest docbook xsl in a user directory rather than a system directory.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info
participants (5)
-
Adrian Buza -
Cramer, David W (David) -
Mark -
Radu Coravu -
Robert Nagle