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

I think you should use the outputclass="before-toc" attribute on the topic refs in the DITA Map that you want them to move before the TOC, plus the @toc="no" for the topics you want excluded from the TOC. Have you tried this?

Many regards,
Dan

Looking closer in the pugin source, I found an hidden parameter that can be used for the purpose. You should set it manually, as it is not shown in the list of parameters in the transformation scenario dialog: outputFile: ${ask('Enter the full path for the pdf:')} Be aware that oXygen will not open ...

Hello, I checked the plugin. In PDF2 (the DITA-OT default plugin for PDF) there is an args.output.base parameter that lets you specify the name of the file without extension. I added an issue for that, we should add support for this parameter in the CSS to PDF based transformation as well. Many rega...

Yes, the "copy" element will simply copy the oxy: element from the merged map to the HTML output. You should replace it by a div or other element: <xsl:template match="*[contains(@class, ' front-page/front-page-title ')]" mode="#all"> <div class="doctype">Datasheet</div> <div> <xsl:copy-of select="@...

Let the XSL extend the merged2html5 extesion point. Try adding a mode="#all" on the template. <xsl:template match="*[contains(@class, ' front-page/front-page-title ')]" mode="#all"> <div class="doctype">Datasheet</div> <xsl:copy> <xsl:copy-of select="@*"/> <xsl:apply-templates/> </xsl:copy> </xsl:te...

Thank you for the details!
We will check if it is possible to change the name of the output file.

Many regards,
Dan

The extension should be bound to the last transformation, the merge2html5. it is currenlty bound to merged2merged in your publishing template, so please correct to: <xslt> <extension id="com.oxygenxml.pdf.css.xsl.merged2html5" file="xslt/document-type.xsl"/> </xslt> In this way the XSLT template wil...

If you need to transform multiple documents (the JIRA output for each product version) to PDF, I recommend creating a script that invokes the DITA-OT multiple times. If you are using an oxygen publishing template to store the customization, you can use the pdf.publishing.template parameter to point ...

Maybe you take a look at the messages from the transformation console (Options/Preferences/DITA/Logging/Console). It might show up that the DITA-OT is processing more resources than expected.

Regards,
Dan

Hello, If you set the margins of a page size to zero, the page margin boxes from that side will not be visible. In general, if you want to style the header of the page, we recommend using a background image set on the entire page, as explained here: https://www.oxygenxml.com/doc/versions/20.1/ug-che...

In theory this should work: .... <!-- Declare the ID as named destination --> <fox:destination internal-destination="circle"/> .... <fo:block color="green"> <fo:basic-link external-destination="#circle"> Go to circle. </fo:basic-link> </fo:block> ... In the SVG you should have: <circle id="circle" ....

I have not tested it, but you can easily try the reverse.
In the SVG sample put an ID on the circle, then add an fo:external-link (or internal) in the FO document having the target that ID.

Many regards,
Dan

Hello David, I set up an example, but it works with mixed results. Assuming that in the XSL FO you have a block with the id "my_block_id": <?xml version="1.0" encoding="UTF-8"?> <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:fox="http://xmlgraphics.apache.org/fop/extensions"> <fo:layout...

Hello David,

As far as I know, the XSL-FO supports only one flow declaration. Please try to contact a commercial XSL-FO processor vendor, like Antenna House or Xep, they may have the needed extensions and expertise.

Many regards,
Dan

When applying the DITA Map to PDF (WYSIWIG or HTML5 based) transformation scenario, (having Chemistry as CSS processor ) you should automatically get links with a "(on page NN)" text following them. Are the links working (i.e. are clickable and navigate correctly)? What oXygen version are you using?...