Hello, I've reviewed the topic you referenced but couldn't see a fix to avoid the blank space between the topic title and the table. Please send us a sample (PDF and .style.xml file from the output folder) to the support@oxygenxml.com email address. We will try to see the exact situation. To overrid...

Publishing individual topics is always more tricky because there might be references that are not processed (especially if not having a key context for it). Anyway, with fix.external.refs.com.oxygenxml parameter it should work for simple cases. The other problem you noticed, the direct link to an im...

Hello, This is just a warning, has no effect on the publishing. In any case, there is a chemistry-fop.xconf file (you can try a recursive search in the installation folder) in which you can change the way the system fonts are scanned. You can remove the <auto-detect/> element from it. Be aware that ...

I see that the image is outside the folder containing the transformed topic.
Please set the transformation parameter:
Many regards,
Dan

Can you try transforming using the classic PDF transformation, one based on XSL-FO? Do the images appear in this case? Can you move the image next to the topic, change its reference and give it a try?

Regards,
Dan

Hello, For landscape tables, please read this topic: https://www.oxygenxml.com/doc/versions/21.1/ug-pdf-css/topics/dcpp_tables.html#ariaid-title3 The other issues may be already fixed on the development stream. In case you want to test the fixes, please write us on support (support@oxygenxml.com) in...

Yes, the property to change is -oxy-page-group. You should set the value of "auto" to merge the current element with the opened chapter page sequence. *[class ~= "topic/topic"][is-chapter] { /* Each chapter starts a new page sequence, so the :first selector applies to each of them. */ -oxy-page-grou...

This is a bug. It will be fixed in the next version (22). As a workaround, you can create a "config/fonts" directory in the working directory of the transformation process, and place the fonts there.

Thank you for reporting the problem!
Many regards,
Dan

Ok, I tried with your CSS: 1. You can simply use: *[class ~= "topic/thead"] *[class ~= "topic/entry"] { border:none; } I added at the end of your rules and it worked. For this kind of customizations, please read the documentation: https://www.oxygenxml.com/doc/versions/21.1/ug-pdf-css/topics/dcpp_de...

For CSS please read:
https://www.oxygenxml.com/doc/versions/ ... aid-title5
Many regards,
Dan

For point 1 could you post a snippet with the exact XML structure of your table? I noticed you have used rowsep and colsep attributes in your CSS.

For point 2, I used just the selector: *[class ~= "front-page/front-page-title"]:after(1) { content: "January 1, 2019"; } And it worked fine. The page is already defined for the front-page, so just use the :after selector. See also: https://www.oxygenxml.com/doc/versions/21.1/ug-pdf-css/topics/dcpp_...

For the point 3, please take a look at:
https://www.oxygenxml.com/doc/versions/ ... f4_np5_cbb
It explains how to use the :marker pseudo-class.

For the others, I will come back with details.

Many regards,
Dan

Hello, This GitHub project is compatible with older DITA-OT versions (1.8 and 2.0) and is not actively maintained by the Oxygen team. Starting with version 21.0 Oxygen bundles DITA-OT 3.x, whith a modified version of this plugin. If you want to publish with DITA-OT 3.x, we can give you access to a c...

Hello, For debugging your CSS we recommend using the development tools from a browser. (You can open the .merged.html file from the output folder in the browser.) See: https://www.oxygenxml.com/doc/versions/21.1/ug-pdf-css/topics/dcpp_debugging_the_css.html#dcpp_debugging_the_css Please use a select...

In case you want to replace all fonts in your publication with a single Sans Serif font, you can increase the importance of your CSS rule: * { font-family: Arial, Verdana, Tahoma, Helvetica, sans-serif !important; } In case you want to change the font for all code sections, you should create rules t...

Hello, Please read about fine tuning your CSS using the browser CSS inspectors: https://www.oxygenxml.com/doc/versions/21.1/ug-pdf-css/topics/dcpp_debugging_the_css.html#dcpp_debugging_the_css The idea is to determine the element or pseudo element that generates the default warning icon, and set it ...

Hello,

I think there is a mistake in your CSS.
I think you need to match both tokens from the CSS class attribute.

Please try:
Many regards,
Dan

Hello, Indeed, we need to update the documentation. Please read "Oxygen installation directory" instead of "Chemistry installation directory". So, please follow these steps: 1. Download (https://sourceforge.net/projects/offo/files/) and extract the offo-hyphenation-compiled.zip file. 2. Copy the fop...

The page numbers are reset to one in two cases: On the first topic that follows the TOC On the first topic from the index To avoid the page counter being reset, you can use in your customization: *[class ~= "map/map"] > *[class ~= "toc/toc"] + *[class ~= "topic/topic"], *[class ~= "index/groups"] { ...

Hello,
The PDF processor does not support the CSS variables, but it supports LESS (http://lesscss.org/). The extension of the customization file should be .less.
Many regards,
Dan

You might find useful this topic:

https://www.oxygenxml.com/doc/versions/ ... aid-title5

It shows how to style some topic depending on the role it has in the map.

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