Hello, This seems quite hard to realize: you can easily number the chapters before the TOC from a custom CSS stylesheet, but for the TOC itself that's different. By default the TOC doesn't include itself, which will lead to a different numbering inside and outside the TOC: The TOC will have: 1 Overv...

Hello Mikael, Unfortunately the processor use the font that allows it to render all the character, this is why DejaVu Sans is used for all the text. A workaround to this problem is to wrap the delta character into a <ph> element and to add the fallback font for this element only: *[class ~= "to...

Hello, This is a normal behavior, if you take a look at the DITA Specification for <mapref> element (same as setting format="ditamap") you will find: The hierarchy of the referenced map is merged into the container map at the position of the reference... One solution to create an additiona...

Hello,

If your string-sets should have different styles (color, font, etc.) you can't, the only solution is to have them in different page-margin boxes (top-left and top-center for example).

Regards,
Julien

Another solution could be to convert the ditamap into a bookmap using Oxygen's XML Refactoring tool or Oxygen XML Scripting if you have a publishing pipeline. Then add the frontmatter into the bookmap. Then using a small XSLT stylesheet you could be able to add the topic into the bookmap frontmatter...

Hello, One solution could be to add an SVG image containing some text after the frontmatter, like in this example: @page frontmatter-page { @top-left {content: none;} @top-right {content: none;} @bottom-center {content: none;} background-image: url("frontmatter.svg"); background-position: ...

Hello, From the topic Chris gave you, in the same note explaining the string() limitation, there's an example on how to style the dynamic text: You cannot use string() inside an oxy_label(). As a workaround, to apply styling on the dynamic text retrieved by a string() function you can define some ov...

Hello, Regarding the page numbering, you can take a look at the How to Reset Page Numbering at First Chapter/Part from our user-guide. Also, this topic was originally opened for the PDF2 transformation (DITA Map PDF - based on XSL-FO scenario) and is quite an old thread. Next time the best for this ...

Hi Chris,

The problem seems only happening with Oxygen 25.0, I added an issue on our side for fixing this problem.
I also added an issue on DITA-OT side, the problem also occur with HTML5 outputs: https://github.com/dita-ot/dita-ot/issues/4104

Regards,
Julien

Hello,

If you want your background-image to start 1cm from the top of the page, you need to change the background-position values: Where the first value is the X axis (from the left) and the second is the Y axis (from the top).

Regards,
Julien

Hello,

In order to make your sample work with PDF outputs, you need to add the print="yes" attribute on each <glossref>.
The abbreviated-forms will be resolved after that.

Regards,
Julien

Hello, You can't find anything about the back-page @page rule because the page is not declared by default. But you already started to declare one which I modified a little to obtain the desired result. Another thing you need to do is to add a rule indicating where this page should be used (at the en...

Hello,

You can take a look to the How to Change Link Styles topic from our user-guide. It should help you customizing the text displayed after cross references.
Also if you're not at ease with CSS, you can debug it in your favorite browser.

Regards,
Julien

Hello, The following fragment will do the trick: /* Title of the TOC page */ *[class ~= "toc/title"][empty]:before { content: "Agenda"; } There are more information about How to Customize CSS Strings in our user-guide. Also, these rules are easy to find by debugging the CSS in yo...

Hello,

Normally images should keep their original or scaled size (except if they are bigger than the page size), maybe you have a CSS rule setting their width to 100%.
For more information, you can also take a look at the Images and Figures topic from our user-guide.

Regards,
Julien

Hello, Which transformation scenario are you using? The attribute-sets solution is valid for the DITA Map PDF - based on XSL-FO scenario: <xsl:attribute-set name ="__lotf__heading" use-attribute-sets="__toc__header"> <xsl:attribute name="font-size">40pt</xsl:attribute> ...

Hello,

You need to activate accessibility in the plugins/org.dita.pdf2.fop/cfg/fop.xconf file: Regards,
Julien

Hello, There is a workaround, you can use the SVG method to add two links: <svg width="50" height="40" viewBox="0 0 50 40" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"> <a xlink:href="https://www.oxygenxml.com/&q...

Hello, It is of course possible to show dynamic content in the page headings. You can add metadata in your DITA content and gather it with the oxy_xpath() function. See How to Show Metadata in the Header or Footer from our user-guide for more information. You can also find other examples in the How ...

Hello,

You can check in our user-guide how to add a link in headers and footers (note there are two methods).
For the display, you can take a look at my answer on this post.

Regards,
Julien

Hello, You need to override the front-page built-in CSS rules and create a multi-line content . @page front-page { @bottom-right { content: "Doc No.-101 \A Version A.1 \A December 2022"; } } For the other pages, you will need to override the chapter page definition : @page chapter:first:le...

Hello, It mainly depends on your knowledge: if you don't have any of CSS or XSLT knowledge you should prefer the CSS transformation which is easier to learn. The XSL-FO transformation on the other side allow a more advanced customization but is harder to create. Besides that, if you are transforming...

Hello, Besides Oxygen Styles Basket, you can take a look at our webinars: Transforming XML and HTML documents to PDF using CSS Transforming DITA documents to PDF using CSS You can also access to all the CSS specification by searching the web with either MDN or W3C keyword. Here are some examples: &q...

Hi Chris, I added your vote to the issue, as a workaround you can create an additional plugin that overrides the 'whr-create-indexterms-page' Ant target. I already did such plugin, you can use it as a starting point: com.oxygenxml.webhelp.responsive.custom.zip If you want the indexterm page on some ...

Hello,

If you want to change standard DITA <note> element, you can follow this topic from our user-guide.
If this topic is unclear, don't hesitate to give your feedback, it will help us make the user-guide better!

Regards,
Julien

Hello, I added an issue related to reset inline elements in TOC, I will notify this thread once resolved. Until then you can repair it by using an XSLT extension, don't worry I already created it and the publishing template declaring it. I also created a custom.css stylesheet that change the TOC dep...

Hello, This happens because figurelist and tablelist inherit from topicref (see DITA specs for figurelist and tablelist ). You can override this by adding this rule to your CSS customization: *[class ~= "bookmap/figurelist"], *[class ~= "bookmap/tablelist"] { margin-left: 0 !impo...

Hello, I tried to create a sample with the given CSS and the numbering look correct to me. deep-chapter-scope.zip Could you indicate which structure your ditamap have, you can start from my sample and update it to reproduce the error. Then I will be able to analyze and fix any problem. Regards, Julien

Hi Cindy, I will answer here for visibility and because it is Oxygen related: By default we don't keep the tab character in the PDF transformation because in either PDF XSL-FO or PDF HTML5&CSS transformation the tab conversion is 1 to 1 (meaning that one tab in DITA will lead to one space in PDF...

Hello, Could you indicate which version of Oxygen you are currently using? Also if you can provide the sample you are using to obtain this output, it will help us analyzing the problem and fixing it. I tried with the following sample and the outputs look fine to me: <table frame="all" rows...