Hello, What scenario are you using? The one based on HTML? I tested with: *[class ~= 'topic/entry'] { padding-top:0.5em; padding-bottom:0.25em; color:green; } and I see that the text is aligned correctly on the baseline of the table row. I recommend to try a transformation without a CSS customizatio...

You can send an email to support@oxygenxml.com.
Thank you,
Dan

Make sure you set a navtitle on your appendix in the DITA map: Many regards,
Dan

Is it the PDF CSS based on HTML transformation?

Regards,
Dan

Hello, There are some counters that are managed already by the builtin CSS: toc-section1, section1. You can use them like this: @namespace oxy "http://www.oxygenxml.com/extensions/author"; /* TOC */ /* * Start with a cleanup: remove all befores for all topicrefs in the appendix, no matter the depth....

Hello,

Chemistry does not support PDF change bars - yet.

Can you post a screenshot with what you want to obtain? Maybe we can help.

Many regards,
Dan

Hello,

Please try: Many regards,
Dan

If you are using the PDF CSS based on HTML, in the output folder you will find a HTML file representing the merged map. You can open it in a browser (Chrome for instance) and use the browser development tools to inspect the elements and styles. Please read: https://www.oxygenxml.com/doc/versions/21....

Ok, I see now you are using the HTML5 based transformation. The fix I gave earlier is for the direct transformation, where the CSS is applied on the merged map. As a workaround, you can hide the "Note: " label: *[class ~= "glossentry/glossUsage"] > .note__title { display: none; } If you want to show...

Hello, Thank you for the feedback! Indeed, this is a bug. The "glossary" CSS selectors in the -i18n.css should be after the "note" ones. We will fix this in the new version. As a workaround, copy the selector in your customization CSS: *[class ~= "glossentry/glossUsage"]:before { content: "Usage: ";...

Hello, This thread is about the CSS PDF customization (oXygen Specific), not about the standard transformation provided by the PDF2 DITA-OT plugin. If you have problems with the PDF2 plugin you can: - request details on the DITA users list: https://groups.google.com/forum/#!forum/dita-ot-users - fil...

Hello, Yes, this is a bug, i will record it. The IDs are generating anchor elements that separate the adjacent margins of the siblings. For instance, the empty context element will generate an inline that inhibits the automatic collapse of the margins of the prereq (the element before) and steps (th...

Hello, Thank you for the examples. First, make sure you remove the quotes from the hyphenation properties: -oxy-hyphenation-push-character-count: 6 !important; /* Minimum 3 characters pushed to next line */ -oxy-hyphenation-remain-character-count: 2 !important; /* Minimum 4 characters remain on prev...

Do you mean a background image for the task? Set an outputclass on the tasks you want to have that background and write a CSS rule to match it and set the background to the element. Another way would be to have a special page and associate it to the tasks class. Read about page backgrounds here: htt...

Can you send us to support some sample API words that are not hyphenated?

Many regards,
Dan

I verified the current implementation (from oXygen 21) and it does hyphenation at the case change. Do you use oXygen 20.1? If running with oXygen 21 and you still have problems, please send us using the transformation console log: https://www.oxygenxml.com/techSupport.html You can also download and ...

Hello,

Ok. We will send you a download link when we will have the fix ready.

Many regards,
Dan

I think you can safely remove them from your customization.

Many regards,
Dan

Another idea: If your API names are wrapped in an element, like a codeph, you can set overflow-wrap: break-word; on this element, and leave the parent table with the hyphenation settings.

Many regards,
Dan

The problem is that we implemented overflow wrap using hyphenation. Anyway, is not a good idea to mix both of them, as there is no priority defined in the standard. Your situation is like this: - Some of the table cells contain API names, that are long, without dashes or underscores, but having a ca...

Hello Carl, Starting with version 21.0 the DITA publishing respects the DITA specification for the bookmaps. A bookmap will have the frontmatter and backmatter shown in the table of contents, bookmarks tree, etc.. To avoid the frontmatter and backmatter topics being listed in the TOC, you need to se...

Please open a new post for the WebHelp problems.
Thank you,
Dan

Hello Rick, This is a known issue that we already solved on the development branch. If you want to beta-test it, we have a nightly build that packages a DITA-OT with our publishing plugins available here: https://mirror.oxygenxml.com/maven-nightly/com/oxygenxml/oxygen-publishing-engine-2.x/21.0-SNAP...

Hello Benny, Please try the following: First approach (using position:fixed) 1. Group all the footer topics under a single parent topic, under the last topic from your map. For example you can have: ... End topic Footer parent topic Footer content topic 1 Footer content topic 2. 2. Put an outputclas...

Hello, Can you give us more details? - the language you are using - what scenario are you using, the one named "DITA Map PDF - based on HTML5 & CSS", or "DITA Map PDF - based on DITA & CSS (WYSIWYG) "? The first one uses the i18n support provided by DITA-OT, and has a good coverage for many language...

The layout engine figures out how many dots are entering in the leader that links the text to the numbers. The text width of the titles seem to vary a bit and sometimes the dot does not fit. Unfortunately there is no setting to control that..

All the best,
Dan

To reset the page on the first chapter, please add this to the customization CSS: *[class ~= "map/map"] > *[class ~= "placeholder/toc"] + *[class ~= "topic/topic"][is-chapter]:not([is-part]) { counter-reset: page section1; } So it will reset both the page and the section counters. Let me know if it ...

I see that the numbering of the chapter starts with 1. Do you refer to the page number of the first chapter?
From your message I understood that you have succeeded in resetting the page, but the sub-sections numbers were wrong (after the fix). Is this correct?

Hello Stanislav, I think a counter-reset used to reset the page on the first chapter has overwritten other counter-reset properties that reset other counters as well. (The counter-reset property can affect multiple counters at once.) If you cannot detect the problem, please send us your CSS using th...

My mistake, please add a mode="#current" on the apply-templates: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> <xsl:template match="*[contains(@class, ' f...