Hello, If you want to transform the chapters separately, you need to have a ditamap for each of them. You can have as many ditamaps as necessary in your structure, for example: Userguide.ditamap Chapter_A.ditamap Chapter_B.ditamap Chapter_C.ditamap etc. Also, as a side note, when asking questions th...

Hello Ian,

You're right, the problem has returned. I added an issue on our side to fix it again.
I will notify this thread once a fix will be available. Thank you for reporting the issue.

Regards,
Julien

Hello, If you want to display the XML tags, you can add the following rules in your CSS stylesheet(s): *:not([class ~= "topic/table"]):not([class ~= "topic/row"])::before(1000) { display: inline; content: "<" oxy_name() ">"; } *:not([class ~= "topic/table...

Hello, The second rule (with break-inside: avoid) indicates that a page break isn't possible inside a table cell, but it is still possible to break between two different rows. I think you can keep this rule for all cells inside a table. If you want to control page breaks as "exceptions", y...

Hello, You need to insert the above rule in a CSS stylesheet, then you need to use this stylesheet in the DITA Map PDF - based on HTML5 & CSS transformation scenario. For more information you can read this topic from our user guide. To block page breaking inside rows you can use the following ru...

Hello,

Are your "merged rows" merged on multiple columns, multiple rows or both?
If they are expanding on multiple columns, you can use the following CSS rule: Regards,
Julien

Hello,

You can check the class of any DITA elements by selecting it in Oxygen and checking the Attributes view: You can also check the Inheritance section of the DITA Specification (e.g. <keyword> element)

Regards,
Julien

Hello,

A new maintenance build for Oxygen 26.1 is available on our website, in this build the "[Fatal Error] :1:1: Content is not allowed in prolog." error will not be displayed anymore in WebHelp Responsive transformation.

Regards,
Julien

Hello,

A new maintenance build for Oxygen 26.1 is available, this version contains the fix for this null error in centered context.

Regards,
Julien

Hi Frank, From what I tested in <oXygen/> XML Editor 26.1, build 2024031806, if the template is inside OXYGEN_INSTALL_DIR\frameworks, the ${frameworksDir} variable expands correctly and the template is displayed in the dialog. Could you confirm this work on your case too? However, if the template is...

If this is not what you are trying to achieve, could you give us more information or even the files you are using?

Regards,
Julien

Hi Frank, The type="filePath" attribute is for publishing templates only, not for frameworks extensions. To create an additional WebHelp transformation scenario I did the following steps: Create a ditamap-custom directory in OXYGEN_INSTALL_DIR\frameworks\dita Create a custom scenario calle...

Hello, The child links description are wrapped into a <div> element: <li class="- topic/link link ulchildlink"> <strong> <a href="first.html">First</a> </strong> <div class="- topic/desc desc">A short description of the task.</div> </li> So to remove them it is possible...

Hello, The problem is browser related, our default CSS rules already indicate that no column break should occur between and indexterm and its children: .wh_term > ul > .wh_term:first-child { break-before: avoid-column; } But the "avoid-column" value is not supported by Firefox as you can s...

Hello, One solution could be to set the image width based on DITA-OT extracted image width: @namespace dita-ot url('http://dita-ot.sourceforge.net/ns/201007/dita-ot'); *[class ~= "topic/fig"] *[class ~= "topic/image"] { margin-top: 0; border: 1px solid black; padding: 1em; } *[cl...

Hello, You can check these hrefs by using the Validate and Check for Completeness tool in the DITA Maps Manager view: image.png You will obtain errors similar to this one: Reference "https://www.oxygenxml.com/non/existing/path" not found. Cause: 404 Not Found for: https://www.oxygenxml.com...

Hello,

Could you indicate which Oxygen version and which transformation scenario you are using?
Is the broken link intended in your publication or is this the origin of the problem?

Regards,
Julien

Hello, I think the problem is the following: you have a language selected for your codeblock, for example Python, so the element will have the outputclass="language-python" attribute set. With your custom outputclass, the final attribute value will be outputclass="language-python gree...

Hello, You're right, by default the crop marks will cut the margins out and you're right again if you want to include the margin boxes in the finished cut, the bleed or -oxy-crop-offset value should be the same as the page margins. Regarding bleed vs -oxy-crop-offset, when using media-box (default) ...

Hello, You can change the page definition for before-toc topics using the following rule: *[class ~= "topic/topic"][outputclass ~= "before-toc"] { page: matter-page; } In this example I used the predefined matter-page which uses lower-roman numbering. To reset the page number for...

Hello Tanja, The problem is that the monospace blocks (like DITA <codeblock> or <codeph>) override the body rule, this is why the error appear. If you set your custom monospace font for these elements, the problem will disappear: *[class ~= "pr-d/codeph"], *[class ~= "pr-d/codeblock&q...

Hello,

Starting with Oxygen 26.1 (already available on our website) it is possible to control the marks display from the CSS.
For more information you can check the Page Boundaries topic from our user guide.

Regards,
Julien

Hello,

We just released Oxygen 26.1, in this version these errors should not appear on SVGs anymore and the image should display in Author mode.

Regards,
Julien

Hello,

I reproduced the problem and added an issue on our tracking system, as you mentioned the problem is related to the centered text context.
I will notify this thread when the bug will be fixed. Thank you for the sample files.

Regards,
Julien

Hello Vincent, Unfortunately I think yes, I don't have this font on my side and I don't know from where you have it. I need at least this font and the topic concerned by this problem as it could be related to the text to be displayed. If you can isolate the topic and it contains no sensitive informa...

Hello Vincent, In order to analyze this I need a small sample where this problem occurs: usually one or more topics and the publishing template or at least the CSS stylesheet(s). Is it possible for you to send this at support@oxygenxml.com? Note: If your DITA documents contain some sensitive content...

Hello,

You can follow the How to Convert Definition Lists into Tables topic from our user guide to realize this customization, it explains step by step how to create the publishing template and the XSLT stylesheet that transforms <dl> into tables.

Regards,
Julien

Hello Heidi, 1. To take the callout attribute value into account, you need to change a little bit the stylesheets: <?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&quo...

Hi Frank,

I also added an issue to change the exception into an error message, I will notify this thread when it will be fixed.

Regards,
Julien

Hello Frank, The problem is that you declare the CSS variables (like --margin-above) under the :root pseudo-class but use them under the @page rules. The :root class is at document level where @page is "above" it: if you use the variables in @page you should declare them in @page too. Rega...