Hello, Regarding the first issue: The documentation was a bit outdated, thank you for reporting the problem! That topic was referring only to the direct transformation, not to the one based on HTML5. I changed the samples, the documentation will be updated soon. Until that, please used the following...

Hello Duncan, I run a test and I changed the XPath expression. You are using the HTML5 based transformation and in this case the othermeta is changed to a div having the topic/othermeta - the example above works for the direct transformation. Here is the updated version: @page :left:right, chapter:f...

Hello Duncan, I corrected the quotes in the example above, it should work now... The XPath is a powerful way to extract content from an XML document. You can use it in CSS to collect metadata, do calculus, etc.. In the example above, the document function parses the original DITA Map (referred by th...

We will try to find a way to pass the meta information from the merged map to the merged HTML, so you can use it further in the CSS customization. As a workaround, you can use the oxy_xpath function run over the original map file. You can extract any element value or attribute from the original proc...

Why not using oxy_xpath CSS extension function, instead of the attr one, like explained in this example:
https://www.oxygenxml.com/doc/versions/ ... aid-title5
Many regards,
Dan

Hello Dmitry, I think those selectors have a lower specificity than the ones from the built-in CSSs. Depending on the numbering parameter from the transformation scenario, one of the built-in CSSs are used: p-numbering-deep-chapter-scope-no-page-reset.css p-numbering-deep-chapter-scope.css p-numberi...

Hi Niels, Can you tell me what oXygen version are you using? We had a lot of fixes in the latest release, including one regarding extra structures left over after applying display:none. I tried your CSS rule with oXygen 21.1, HTML transformation and it works fine. If you are still having these probl...

Hello Niels, I tried reproducing your problem using the CSS rules you provided with oXygen 21.1 and it works fine. Can you tell me what version are you using? Do you get the same errors for the tables? Another thing: I am not sure if you are using the HTML5 based PDF transformation. If you are, in t...

Hello Michael,

This looks like a bug. Can you tell us what element is following the p element? A DITA snipped would be good.

Many regards,
Dan

Hello Michael, We have prepared a nightly build here: http://mirror.oxygenxml.com/maven-nightly/com/oxygenxml/oxygen-publishing-engine-3.x/22.0-SNAPSHOT/oxygen-publishing-engine-3.x-22.0-SNAPSHOT-package-full.zip Extract it to a folder, then configure oXygen to use it (Preferences/DITA/ DITA Open To...

Hello Michael,
We are preparing a nightly build of the publishing engine, with a new parameter that will allow you to control the discarding of the top/bottom margins for elements that are at the top or bottom of a page. Costin will give you more details when the build is ready.
Many regards,
Dan

Hello,

I think one workaround is to use the padding-top property instead of margin. The margin is discarded, but the padding not.

Many regards,
Dan

The margins of the first block in the page are now discarded. This is desirable, to make the sections titles align properly in the page when they are at the beginning. The front-page-title is not the first block in the page, there are others with no content. Those are losing the top margin. A workar...

Thank you for the details! The problem is caused by the padding-right="4px" . This looks like either our fix from the built-in CSS is not working, or you have such padding set in the customization CSS. Please open the merged HTML file in a browser (Chrome for instance), and using the developer tools...

Hello Michael, I tried to use the DITA sample: [Oxygen Install Dir]\samples\dita\it-book\taskbook.ditamap and the standard HTML transformation using the 'ashes' template but I cannot reproduce the problem. Please try to use a standard publishing template (the first tab in the transformation scenario...

We have made the necessary changes. The fix will be available in oXygen/Chemistry 21.1.

Thank you for reporting this issue, the page layout has improved!

Many regards,
Dan

Thank you for reporting this! Yes, this is a limitation, we will try to find a solution for this. For the moment I see no easy workaround, except trying to alter all the SVG from the documentation using the oXygen refactoring actions in a form that is acceptable for both the print and web formats. A...

Hello Michael, The transformation add a code inside the pre element. This is an inline element, that has some padding set from the built-in CSS. You should remove its padding: pre{ padding:2px 4px; } pre > code{ padding:0; } I fixed this in the default CSSs. If you encounter more problems, please co...

Hello Adam, Please use: *[class ~= "topic/xref"][href]:after, *[class ~= "topic/link"][href]:after { content: none !important; } The documentation about link styling is here https://www.oxygenxml.com/doc/ug-pdf-css/topics/dcpp_links.html#dcpp_links In the current documentation the !important qualifi...

We found something, we could use the space-before and space-after FO attributes instead of margin-top and margin-bottom in the intermediate FO file. We will notify you when we have a build.

Avoid using [1], it means the first item from its parent. Use (..)[1] to select the first item returned by the inner expression. I would write the expression like: //*[contains(@class, " front-page/front-page ")]//*[contains(@class, " topic/category ")]/*[contains(@class, "topic/keyword")]/text() Us...

Hello Chris,
This is interesting, than you for reporting it. We will try to find a solution.

Many regards,
Dan

Hello Bridget,

Please try different PDF Readers.
I see that the one from Chrome works completely different from the Acrobat Reader.
The first one sets newlines after each visual line, while Acrobat is putting the entire codeblock on a single line, that is bad also.

Many regards,
Dan

Can you post a DITA snippet?
Thank you,
Dan

We do not have this page defined in the default CSS, but you do have a workaround: You have to use a DITA bookmap and add a backmatter to it. In this backmatter add a reference to a topic that contains the back-page content. That topic must be marked with a special outputclass attribute value, like ...

Hello Chris,
Thank you for sharing your scripts!
Many regards,
Dan

What transformation are you using? If you are using the CSS based PDF transformation, please see:
https://www.oxygenxml.com/doc/ug-pdf-cs ... e_breaking
The main documentation is here:
https://www.oxygenxml.com/doc/ug-pdf-css/

Many regards,
Dan

Oxygen folks - is there a way to run Chemistry PDF with only my CSS applied? I will gladly take responsibility for all counters, page and elements formats, etc.

No, there is no such option. You can try to change the build.xml file from the com.oxygenxml.pdf.css DITA plugin.

Many regards,
Dan

Yes, there is a tutorial about customizing the CSS based DITA transformations. You can read more here:

https://www.oxygenxml.com/doc/ug-pdf-css/

We will redesing the website layout to make this resource easier to find.

Many regards,
Dan

There is no simple way to achieve this by CSS layout, but is an workaround. You should create a series of simple background images for the hazard statement headers. These background images should replace the normal header coloring, and have the left part empty - on this part the danger symbol is pla...