DITA publishing by WebHelp Classic
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 1
- Joined: Fri Jul 24, 2020 1:27 pm
DITA publishing by WebHelp Classic
Hello,
I'am just starting to work with DITA and Oxygen.
Could you help me with one publishing problem. I decided to use DITA WebHelp Classic Transformation scenario, but the build-in publisher has some problems with styles: so there are no border lines into tables, no icons for notes and so on. While WebHelp Responsive has good CSS styles. So the question is: can I combine this two transformation scenarios (use the CSS styles from Responsive in Classic)?
PS I've read about WebHelp Output Customization in docs and understand that is not an standard option to use Classic for DITA. But anyway, maybe is it possible to combine these scenarios?
I'am just starting to work with DITA and Oxygen.
Could you help me with one publishing problem. I decided to use DITA WebHelp Classic Transformation scenario, but the build-in publisher has some problems with styles: so there are no border lines into tables, no icons for notes and so on. While WebHelp Responsive has good CSS styles. So the question is: can I combine this two transformation scenarios (use the CSS styles from Responsive in Classic)?
PS I've read about WebHelp Output Customization in docs and understand that is not an standard option to use Classic for DITA. But anyway, maybe is it possible to combine these scenarios?
-
- Posts: 846
- Joined: Mon Dec 05, 2011 6:04 pm
Re: DITA publishing by WebHelp Classic
Hi pahom,
Please note that the WebHelp Classic transformation scenario became deprecated 2 versions ago and, currently, we only implement small fixes, but it will be most probably dropped in the near future versions of oXygen.
So, as long as you do not have a specific reason to use the deprecated WebHelp Classic transformation scenario, it is highly recommended to use the modern WebHelp Responsive scenario instead.
As the Responsive and Classic are two different WebHelp formats, the selectors may differ so even if you would use the WebHelp Responsive CSS styling on the Classic output, it may not have any impact or you might obtain results different than the expectations.
If, for any specific reason, you insist in running the Classic transformation, then you could develop and use your own CSS file, to customize the output.
For that, you should pass the file to the scenario, using two parameters:
- edit the WebHelp Classic transformation scenario and open the Parameters tab.
- set the args.css parameter to the path of your custom CSS file.
- set the args.copycss parameter to yes to automatically copy your custom CSS in the output folder when the transformation scenario is processed.
- click OK to save the changes to the transformation scenario.
- run the transformation scenario.
Your custom CSS will be applied as a final layer on top of any existing CSS rules and the output will reflect the changes you made.
Regards,
Costin
Please note that the WebHelp Classic transformation scenario became deprecated 2 versions ago and, currently, we only implement small fixes, but it will be most probably dropped in the near future versions of oXygen.
So, as long as you do not have a specific reason to use the deprecated WebHelp Classic transformation scenario, it is highly recommended to use the modern WebHelp Responsive scenario instead.
As the Responsive and Classic are two different WebHelp formats, the selectors may differ so even if you would use the WebHelp Responsive CSS styling on the Classic output, it may not have any impact or you might obtain results different than the expectations.
If, for any specific reason, you insist in running the Classic transformation, then you could develop and use your own CSS file, to customize the output.
For that, you should pass the file to the scenario, using two parameters:
- edit the WebHelp Classic transformation scenario and open the Parameters tab.
- set the args.css parameter to the path of your custom CSS file.
- set the args.copycss parameter to yes to automatically copy your custom CSS in the output folder when the transformation scenario is processed.
- click OK to save the changes to the transformation scenario.
- run the transformation scenario.
Your custom CSS will be applied as a final layer on top of any existing CSS rules and the output will reflect the changes you made.
Regards,
Costin
Costin Sandoi
oXygen XML Editor and Author Support
oXygen XML Editor and Author Support
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