Are you using a publishing template (selected in the first page of the DITA transformation scenrio dialog)? Probably the CSS rules from it are more specific. You can use more specific selectors like: @page :left, chapter:left, chapter:first:left { .. } Or you can use the !important specifier: font-f...

Hello,
Please use the property: This will make the text bleed out to the left and right space and avoid line breaking. The text will be still centered.

Many regards,
Dan

Yes. the structure is different for the titles in the main content. You can use a CSS like this one: *[class ~= "topic/topic"] > *[class ~= "topic/title"]:before{ color:red; display:block; position:absolute; top:0; left:0; width:50px; background-color:silver; } *[class ~= "topic/topic"] > *[class ~=...

There are some limitations in the Chemistry we are trying to solve. Until then, you could try the following CSS snippet: *[class ~= "map/map"][numbering^='deep'] *[class ~= "map/topicref"] > *[class ~= "map/topicmeta"]:before { display:inline-block; background-color: pink; vertical-align: top; } *[c...

Hello Anton, This is caused by a series of built-in CSS selectors that remove the "on page" text that appears after the link text (in case of external links) and are quite specific. The solution is to increase the specificity of your selector, like: *[class ~= "topic/xref"][href]::after, *[class ~= ...

Please read here:
post55679.html#p55679

The idea is to add to the metadata section of the bookmap data elements that expand the needed keys. We are not pushing all the defined keys in the merged map because there are cases of large key pools (thousands).

The main condition is to have this key referenced from the content (either topic or map). If you do not have it referenced, you may force a reference by using the topicmeta or bookmeta section of your map and a data element. This has no effect on the published content, but allows the CSS rules to us...

Please read this topic from the CSS customization guide:
https://www.oxygenxml.com/doc/versions/ ... aid-title2

Many regards,
Dan

Maybe you can use some XSLT extensions for the webhelp. Please see an example here: https://www.oxygenxml.com/doc/versions/21.1/ug-webhelp-responsive/topics/wht-task-pt-xslt-import.html The full customization manual is here: https://www.oxygenxml.com/doc/versions/21.1/ug-webhelp-responsive/topics/wh...

The title element of a bookmap is quite complex, and contains elements for the book library and an alternate title: <booktitle> <booklibrary>Retro Tools</booklibrary> <mainbooktitle>Main Book Title</mainbooktitle> <booktitlealt>Book Title Alternative</booktitlealt> </booktitle> The builtin CSS uses ...

If this simplifies the work for your writers, I think you should go on with this CSS+XPath approach. However, if you plan to publish this to other formats, like WebHelp or plain HTML, you will not benefit of this customization, so please take care.
Many regards,
Dan

Please read about changing the numbering using a transformation parameter (args.css.param.numbering) here: https://www.oxygenxml.com/doc/versions/21.1/ug-editor/topics/dcpp_numbering_types.html Another way is shown here (for Chapters, for Parts is similar): https://www.oxygenxml.com/doc/versions/21....

Please read about changing the numbering using a transformation parameter (args.css.param.numbering) here: https://www.oxygenxml.com/doc/versions/21.1/ug-pdf-css/topics/dcpp_numbering_types.html Another way is shown here: https://www.oxygenxml.com/doc/versions/21.1/ug-pdf-css/topics/dcpp_remove_pref...

It looks like transformation is trying to start a chemistry executable that is not embedded into the oXygen installation. This may have two causes: 1. A corrupt chemistry installation is specified in the PATH environment variable. 2. An incorrect chemistry installation is specified in the transforma...

To forward all the othermeta elements information to the document properties, you can use a this CSS rule:
Many regards,
Dan

Here are some hints: 1. Use a simple table (simpletable DITA element), or a hierarchy of simple tables. As far as I know, these are not counted in the list of tables. 2. The front matter sections are rendered by default without headers. You can read more about the structure and customization possibi...

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...