Customizing com.oxygenxml.pdf.css DITA-OT plugin
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 8
- Joined: Thu Sep 10, 2020 7:03 pm
Customizing com.oxygenxml.pdf.css DITA-OT plugin
Hi,
I have been trying to figure out why my custom HTML5 DITA-OT plugin works properly in a straight HTML5 build, but this same HTML5 plugin does not seem to be called at all during execution of the oxygenxml.pdf.css plugin (which uses DITA-OT's HTML5 plugin).
I saw that the com.oxygenxml.pdf.css plugin defines its own extension point, so I tried making another plugin to hook in my HTML5 customizations that way - it still doesn't work.
I took a closer look at the com.oxygenxml.pdf.css plugin, and it seems that it explicitly imports all its own XSL using relative paths into the org.dita.html5 plugin. In other words, it doesn't seem to participate in DITA-OT's usual "make a new plugin and copy-the-template-to-override-behavior" approach.
So my first question is this: Is my assessment of this situation correct?
Next question: If I'm correct, then what is the best strategy for customizing the HTML5 part of the com.oxygenxml.pdf.css plugin? It seems like we must either directly edit the XSL in the oxygenxml.pdf.css plugin (in this case it's the file html5-figures.xsl), or, we can duplicate the entire com.oxygenxml.pdf.css plugin and make our customizations. This way we leave the base plugin intact. Is there another, better way that I'm missing?
If I'm correct, I'm very curious to understand why the com.oxygenxml.pdf.css plugin seems to skirt the usual DITA-OT plugin override mechanism. The plugin does use the override mechanism for its own customizations of the HTML5 build, however, it seems to put up a wall that prevents other plugins from customization of HTML5. Was there a technical reason that necessitated this design?
Thanks,
John
I have been trying to figure out why my custom HTML5 DITA-OT plugin works properly in a straight HTML5 build, but this same HTML5 plugin does not seem to be called at all during execution of the oxygenxml.pdf.css plugin (which uses DITA-OT's HTML5 plugin).
I saw that the com.oxygenxml.pdf.css plugin defines its own extension point, so I tried making another plugin to hook in my HTML5 customizations that way - it still doesn't work.
I took a closer look at the com.oxygenxml.pdf.css plugin, and it seems that it explicitly imports all its own XSL using relative paths into the org.dita.html5 plugin. In other words, it doesn't seem to participate in DITA-OT's usual "make a new plugin and copy-the-template-to-override-behavior" approach.
So my first question is this: Is my assessment of this situation correct?
Next question: If I'm correct, then what is the best strategy for customizing the HTML5 part of the com.oxygenxml.pdf.css plugin? It seems like we must either directly edit the XSL in the oxygenxml.pdf.css plugin (in this case it's the file html5-figures.xsl), or, we can duplicate the entire com.oxygenxml.pdf.css plugin and make our customizations. This way we leave the base plugin intact. Is there another, better way that I'm missing?
If I'm correct, I'm very curious to understand why the com.oxygenxml.pdf.css plugin seems to skirt the usual DITA-OT plugin override mechanism. The plugin does use the override mechanism for its own customizations of the HTML5 build, however, it seems to put up a wall that prevents other plugins from customization of HTML5. Was there a technical reason that necessitated this design?
Thanks,
John
-
- Posts: 501
- Joined: Mon Feb 03, 2003 10:56 am
Re: Customizing com.oxygenxml.pdf.css DITA-OT plugin
Hello John,
The HTML5 based transformation can be customized using XSLT templates, but is not recommended to do it through a DITA-OT plugin (it would work only if you change the DITA-OT, which for an installed Oxygen editor can be hard), but instead using an Oxygen Publishing Template. Please read more about it here:
https://www.oxygenxml.com/doc/versions/ ... ation.html
https://www.oxygenxml.com/doc/versions/ ... sions.html
Let us know if you have more questions.
Many regards,
Dan
The HTML5 based transformation can be customized using XSLT templates, but is not recommended to do it through a DITA-OT plugin (it would work only if you change the DITA-OT, which for an installed Oxygen editor can be hard), but instead using an Oxygen Publishing Template. Please read more about it here:
https://www.oxygenxml.com/doc/versions/ ... ation.html
https://www.oxygenxml.com/doc/versions/ ... sions.html
Let us know if you have more questions.
Many regards,
Dan
Return to “DITA (Editing and Publishing DITA Content)”
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