To fix this you will need to use a fallback font. If you are using Times New Roman for the entire publication, you may consider adding Symbol as a fallback. In your customization CSS add: *[class ~= "topic/dlentry"] { font-family: "Times New Roman", Symbol; } Or other font that can render the charac...

I am glad it worked! I added more info about your usecase to the userguide of the DITA CSS PDF plugin, it will be available when we release the next version. The built-in CSS rules contain something like: *[class~='topic/topic'][is-chapter] { -oxy-page-group : start; } The "start" value makes the ch...

It looks like Saxon HE is limited by design: https://sourceforge.net/p/saxon/mailman/message/26849522/ The only workaround is to format the date like this: ... content: oxy_xpath("let $cm:= format-date(current-date(), '[MNn]') \ return concat( \ if ($cm= 'January') then 'JAN' else \ if ($cm= 'Februa...

Yes, indeed, I tested the expression using the Saxon SA XPath processor, while the Chemistry distribution contains Saxon HE. I will check what happens.

Thank you for the feedback!
Dan

Yes, it was an incomplete post. Now the details are here: post49050.html#p49050

Dan

Regular DITA maps do not have the concept of a copyright notice. This is available only in the DITA bookmap structure. If you are constrained to using a regular map and you need to add a copyright page between the front cover and the TOC, use the following technique: In your customization CSS, decla...

I tested again a snippet from a previous post, and the empty page dissapears if adding the last selector: *[class ~= 'map/map'] > *[class ~= 'toc/toc'] { display:none !important; } *[class ~= 'map/map'] > *[class ~= 'front-page/front-page']{ display:none !important; } *[class~='topic/topic'][is-chap...

Please add to your customization CSS the following snippet: *[class~='topic/topic'][is-chapter] { -oxy-page-group : auto; } This should fix the page breaking problem. The customization CSS can be referred from the template descriptor, or passed as the args.css parameter to the transformation scenari...

There is a syntax error in your XPath expression, it misses a comma and you should use singe quotes around the 'ru' token, since the entire expression is already enclosed in double quotes: The correct form is: ... content: oxy_xpath("format-date(current-date(), '[MNn] [Y0001]', 'ru', (), ())"); ... ...

Hello,

This is caused by a compatibility mode that sets the HTML tables font size to "medium". In fact this should not apply, as the format is HTML 5. I will log a bug about this. Meantime, you should add also this selector:
Many regards,
Dan

What scenario are you using to transform your documents? Your SVGs have information about their size? A small sample would be good to determine the fix.

Many regards,
Dan

Hello Mr. Kim, I think you should write your CSS customization rules as: *[class~="hazard-d/hazardstatement"][type="notice"]:before { content: oxy_uppercase(attr(type)); } *[class~="hazard-d/hazardstatement"][type="notice"] { display:block; background-color:blue; border-bottom: 2pt solid; padding:0....

The selectors you pointed to apply to the WYSYWIG PDF transformation only. In the HTML based transformation, the intermediate merged DITA map is transformed to HTML5 using the DITA-OT built-in support, so the generation of the static strings (the labels for chapters, parts, figures, tables, notes, e...

Hello, What image format are you using? Can you send us a sample image file? You are using it in the topic content, or to decorate the page background or headers? We have tested with PNG images (created with GIMP) and it works fine. For more information see the "Image Resolution" section from https:...

Hello Paul, Fist you should use instead of "otherprops" attribute the "outputclass" attribute. The "otherprops" attribute is filetered out during the processing of the merged map. You can use the oXygen refactoring actions to make this change (or a simple find/replace in files across the project). I...

I understand that you need in fact the title of the product to be placed a the top of the bookmarks tree. The booktitlealt is duplicated by the transformation process in the TOC structure so that it can be shown there if needed. Your selector matches both the element from the front page and the one ...

There are two solutions: 1. You are using the pdf-css-html5 transformation. With this you should get automatically the numbers of the tables before the table titles, with no change in your CSS file. However, I just learned that there is a "com.oxygenxml.html.custom" plugin in the DITA-OT directory t...

If you plan to reuse styles between the WebHelp output, which is HTML5 based, I recommend to use the DITA to PDF based on HTML5 and CSS.
See the video presentation for details:
https://www.oxygenxml.com/demo/opt.html

Many regards,
Dan

Is hard to tell what is wrong. We are not doing XSLT customization but we will try to help you by taking a look at your plugin. Please use the https://www.oxygenxml.com/techSupport.html form to send it to us.

Many regards,
Dan

The page break processing instructions should be placed inside the topic files, not in the map between topic references.
Many regards,
Dan

I think there is no such class on the body element. You will need to use a more complex strategy. The approved element is located in the bookmeta/bookchangehistory element. <bookmeta> <author>Howe Tuduit</author> <critdates> <created date="1/1/2015"/> <revised modified="3/4/2016"/> <revised modified...

In case you are using the WYSIWIG transformation scenario you can add the template to the file: [DITA-OT-DIR]/plugins/com.oxygenxml.pdf.css/xsl/merged2merged/merged.xsl In case you are using the HTML5 based PDF transformation (not WYSIWYG), this is the recommended transformation now, you may use an ...

The attr() function applies to the element matched by the CSS rule selector. In this case it matches the booktitle. If your attributes are on the root element "bookmap", you will need to use XPath to extract the values from this element. Here is a snippet for this: *[class ~= "bookmap/booktitle"]:af...

This expression worked for me: :root { string-set: author oxy_xpath('//*[contains(@class, "front-page/front-page")]/*[contains(@class, "map/topicmeta")]/*[contains(@class, "topic/author")]/text()'); } In the map there was: <map> <title>The Art of Bike Repair</title> <topicmeta> <author>John Doe</aut...

You can collect the metadata and keep it into a string variable. For example, to collect the value of the "author" element : :root { string-set: author oxy_xpath('//*[contains(@class, "bookmap/bookmeta")]/*[contains(@class, "topic/author")]/text()'); } Please note that the string-set property accept...

See the response from: post48027.html#p48027

Hello Scott, To define multiple string sets for an element, please use a single string-set property with a list of comma separated definitions: :root { string-set: prodname oxy_xpath("//bookmeta//prodinfo/prodname"), prodversion oxy_xpath("//bookmeta//prodinfo/vrmlist/vrm/@version") "." oxy_xpath("/...

It is relative to the CSS. Unfortunately, the !important modifier does not work in the page rule. We have an issue on our tracking system, it will be resolved in the next version. I think there is a more specific selector in the p-front-page.css that clears the @top-right page margin box: @page fron...

We fixed the problem, it will enter the next major version.
Let us know if the above CSS snippet is working for you, if not, we can provide a Chemistry PDF CSS processor nightly build.

Thank you for the feedback,
Dan

A better solution is to add to your customization CSS the following rule: *[class~="topic/table"] > *[class~="topic/tgroup"] { table-layout: auto; } This makes the table automatically stretch as much as the columns. We will investigate further the problem with the fixed layout table and specified co...