Hello, There is no predefined plugin - you should create a custom DITA-OT plugin from scratch. More details on creating custom plugins available on the DITA-OT website: https://www.dita-ot.org/2.0/dev_ref/plugins-overview.html and also in the oXygen User-Guide (where you can find details on creating...

Hello, You should use the DITA Map PDF - based on HTML5 and CSS instead of the DITA Map PDF (based on XSL-FO) transformation scenario. That's because it is easier to fine tune how specific elements are rendered in the output, or if they would be rendered at all, by styling/hiding them through CSS pr...

Hi B-E-N, Indeed, there seems to be a discrepancy between the WebHelp output and PDF output. I logged this in our internal issues tracking system to investigate and see if there is something we could do on our side to improve this. Meanwhile, as a workaround you could use the "vertical-align: s...

Hi, I just tested this but could not reproduce the issue. To test, I set the importance="optional" attribute on the 2nd step of "pruning.dita" task in the "Growing Flowers" sample DITA Map in oXygen The "Optional" label is displayed just fine in the PDF. I use...

Hi, You should just add an additional "@bottom-left-corner" page-margin-box selector inside your "@page" rule. For the "@bottom-left-corner" you should set the same margin and border on its left side. More specific: @page { size: us-letter landscape; column-count: 2; co...

Hello, When using remote fonts (like the Google fonts from https://fonts.googleapis.com), in case there is any connectivity issue (you have an incorrect proxy configuration in oXygen or system, any other incorrect network settings configuration in oXygen, or if the server that oXygen tries to reach ...

No, changing the aspect (portrait / landscape) is not supposed rotate the page. It should just change the layout the content on a page would be displayed: horizontally or vertically, so the page-margin boxes should remain unchanged. You can easily test this yourself through a simple @page rule in yo...

Hello, You can use a rule in your customization CSS to style the element holding the file name. As a general rule, to identify the selectors appropriate to the elements you want to style, you could use your internet browser's CSS inspector. Once you identified the selector, the use it in your own ru...

Hi Catherine, We tested this behavior using oXygen XML version 20.1 (the latest available on our website) and could not reproduce the issue. Could you try installing the latest version, then use the predefined transformation scenario with a customization CSS that contains only the lines you tried al...

Hello, I'll add an improvement request in our internal issue/improvement tracking system so that our developers will analyze the possibility to add a predefined PDF based on CSS transformation also for separate topics, without a DITA Map context. We will update this thread when / if this functionali...

Hello, I just checked the image size and even the image in the PDF you obtained (in the output you sent us by email) has the right PPI - 300. BTW, "DPI" (which stands for Dots Per Inch and is only used to express how many dots of ink per inch can be printed, depending on the quality of eac...

Hi Kim, Despite this is the intended behavior of the "toc" attribute, we tried to see if we could make this configurable through a parameter. Unfortunately we reached to the conclusion that there is no parameter that could be used for this and also couldn't find a easy way to attain the de...

Hi daudvyd, Most of the CSS3 properties are supported in oXygen. For a complete list of the supported CSS3 elements, you should consult the Appendix available in the Chemistry User-Guide . And yes, Chemistry is our proprietary PDF engine. There is also the Oxygen DITA-OT CSS Publishing to PDF Plugin...

Hello, It is not clear if the source files you work with are general XML documents, or if they are one of the common XML specialization (like DITA or DocBook). It is also not clear which transformation scenario are you applying to publish your documents. Is it one of the scenarios that come predefin...

Hi, It is not so clear what exactly you need to achieve. The number of columns for a table should be declared in your source XML document, is not part of a specific transformation. The PDF based on CSS transformation scenarios just publish your source files to PDF, they does not alter their content ...

Hi, Tasks, concepts and references are DITA specializations, while "<example/>" is an element. It may be contained in the body of such specialization topics (like taskbody, conbody or refbody). More details available [url=OS/langspec/langref/example.html]in the OASIS DITA specification[/ur...

I'm afraid that, as we are not aware of such issues, without looking into your source file, we can not investigate this.
Therefore, please send on our support email (support@oxygenxml.com) address a sample file that you could reproduce the issue with and we will see what goes wrong.

Regards,
Costin

Hello,

Unfortunately not, as, like Dan said, the attribute is filtered at transformation time by the engine.

The only workaround is to set an outputclass attribute like advised.

Best Regards,
Costin

Hello, It is possible to add your custom translations and modify the already-existing translations for the WebHelp output. This can be done by creating a custom DITA-OT extension plugin, that would change the existing translated strings with your own. Detailed information on how to achieve this with...

Hi bloodnok, Unfortunately, we can not see the images to observe what happens. You could send the images on our support email support@oxygenxml.com However, please note that the <codeblock> elements are intentionally displayed as they appear in the source file. Therefore, if you have carriage return...

Hello, Please note that DITA-OT 1.8 was deprecated in v19 and is no longer supported starting with version 20 of oXygen XML. This was already mentioned in the "What's new" section . I'm afraid that, if you strictly need to use the old DITA OT v1.8, you should stick with oXygen XML 19. Rega...

Hi Mark, We are not aware of such issues with our default transformation output. Are you using the default transformation, as it comes out-of-the-box in oXygen, or are you using a customized transformation? If you are using a customized scenario, please try using the default DITA Map WebHelp Respons...

Hi Kim, This is how the @toc attribute works for the current implementation. If one sets its value to "no" for an/some element/s, then it means it is not intended to appear in the output so it is completely omitted from the TOC model and the breadcrumb hierarchy. I've logged your feedback ...

Hi Scott, We looked into this and unfortunately the the oxy_xpath function does not work for the page-margin box. It should though, so an improvement request was added internally. Therefore, this will be implemented in a future version of oXygen, but until then I'm afraid the only workaround is to w...

Hi Catherine, Indeed, the WebHelp Classic Mobile transformation was deprecated in version 19 and removed in the latest version (v20). However, could you please provide more details about what specifically does not look as you would expect in the WebHelp Responsive output or what you miss from the We...

Hi mdslup, There is no predefined action or parameter you could use in the transformation scenario to hide / disable the splitter in the WebHelp Classic output. However, there is a workaround which you could use to disable the splitter bar and make the side TOC fixed. Specifically, you should edit t...

Hi Scott, I already replied to this on the email you sent on our support email address, but I will also paste my reply on this thread. We only support transform: rotate(90deg); / rotate(-90deg); rules. However, you could either rotate the whole page containing the table or rotate the table in the pa...

Hi CarlosM, What version of oXygen are you using? Are you on the last version available? Also, what specific transformation scenario are you applying? Is it DITA Map PDF - based on HTML5 and CSS, or the DITA Map PDF - based on DITA and CSS (WYSIWYG)? Also, what type of reference do you have? Is it a...

This is currently not possible.
We have an improvement request logged in our system, so we will let you know when/if this will get implemented.

Costin

Hi Scott, Unfortunately, it is not very clear what is the specific context where you insert the image reference into your source DITA document. I am asking this as I find it a bit weird that the image you refer in your document ends up inside a <div/> element in the merged HTML document, instead of ...