Hello,
I've just deleted your other post, as it seems you were asking exactly the same questions there as well, so I will reply to this one instead.
Our proprietary Chemistry engine comes bundled in all of the standalone GUI products (Editor/Author/Developer). As you already figured out, the DITA Map PDF based on HTML5 and CSS trasnformation scenario uses the Chemistry engine to output the PDF and you could fine tune the resulted PDF using your own CSS customization.
There is also the PDF Chemistry standalone product indeed, which is a separate product needing a separate license and comes at a different price.
That specific product is used to produce PDF output based on HTML5 and CSS out of oXygen GUI software products. For example, companies could automate the process using command line scripts. More details on the accepted command line parameters available
in the Chemistry User-Guide.
Both the bundled Chemistry and the standalone one are complex engines, based on the Apache FOP XSL-FO engine and tweaked by us to meet even more complex publishing standards.
- So, to answer your first question, like I was saying, this is only needed if you generate PDF outside of oXygen, but if you are OK with manually applying transformation scenarios from inside oXygen GUI and won't need to automate the publishing process, then most probably you won't need the separate product.
- Now, regarding your 2nd question, about the location of the predefined CSS, I'm afraid the answer is not as simple as you might have expected.
There are many default CSS files, in different locations inside the oXygen installation folder.
That's because the CSS files are organized based on their purpose (each default CSS file is used to style a specific page / section / element layout in the resulted PDF).
Basically, the folders that contain the default CSS files are located in Oxygen_Install_Dir\frameworks\dita\DITA-OT3.x\plugins\com.oxygenxml.pdf.css\css
One way to identify what rules are applied and which CSS do they come from is to use your internet browser inspector to inspect the styles applied on the intermediary .html file resulted in the output folder. Please see
the Debugging the CSS section from the oXygen User-Guide.
However, please note that editing the default CSS files from the oXygen installation folder is discouraged, because it may lead to issues and the changes could not be reversed. Instead, it is good practice to inspect the intermediate style (as advised above) to identify the correct selectors you need to use to tune the output, then use your own customization CSS file, either directly, through the "
args.css" parameter from the transformation scenario configuration, or inside a publishing template.
More details also in the User-Guide, in
the Customization CSS section.
I hope this helps and happy publishing!
Regards,
Costin
