Hi,

A assume that you are using the WebHelp Responsive transformation.

In this case, please follow the Rel. Links Displaying Above Hierarchy Links forum thread that treats the same problem.

Hi, Do you want to create a link to the Index section? If this is your case, I think you should use the fo:basic-link/@internal-destination attribute to create a link inside the PDF document. More precisely, to create a link to the Index section, you can try something like this: <fo:basic-link inter...

Hi, Yes, the PDF produced by the default DITA-OT PDF transformation uses a double-sided page numbering style. This means that chapters will always start on odd numbered pages and blank pages will be added when a chapter does not end on an even page number. This behavior is implemented in XSL-FO by s...

Hi, Did you try to use the @action="passthrought" value in your DITAVAL? <prop action="passthrough" att="platform"/> In this case, the profiled DITA content will be included in output together with the profiling conditions. The profiling conditions can be found in the o...

Hi, When an XSLT script is executed from the XML Refactoring tool, the XSLT transformation is executed in a safe mode. This implies the following: The DOCTYPE will be preserved. The DTD entities will be preserved as they are in the original document when the document is saved. The attribute values w...

Hi, Yes, you are right. A topic that is referenced from your publication using one of the DITA referencing mechanism (conref, xref or reltable) will be published(converted to HTML) even if it is filtered from the DITA map. In this case, the topic is also processed when the WebHelp indexterms page is...

Hi, Yes, I think it is possible by extending the default processing with a PDF customization plugin . The list item numbering is implemented in the following XSLT stylesheet: {DITA-OT-folder}/plugins/org.dita.pdf2/xsl/fo/lists.xsl More precisely, in the template: <xsl:template match="*[contains...

Hi,

What output format are you trying to customize? PDF or HTML?

Hi, Another solution to investigate your problem is to send us the folder where WebHelp Search index is stored. This folder contains an index with all words from your publication and the relative paths to topics that contain them. The location of this folder is: {webhelp-output}\oxygen-webhelp\searc...

Hi,

Yes, the WebHelp search function is critical for us.

It would be easier to fix your problem if we have a sample to reproduce it.

So, could you send us a small DITA Map sample together with referenced topics to reproduce your problem at support@oxygenxml.com?

Hi, Thank you for reporting this issue. It seems the Home label is not translated in the WebHelp translation files. If you have a translation for it, you can fix this problem by opening the translation files from the DITA_OT_DIR/plugins/com.oxygenxml.webhelp/oxygen-webhelp/resources/localization fol...

Hi, At this moment, it is not possible to filter the WebHelp content for a certain product. We have plans to implement this functionality in a future WebHelp version. I'm not sure if the WebHelp output is ready to implement this feature. - how to add script code IMMEDIATELY following the body tag of...

Hi, When WebHelp Responsive output is generated by Oxygen XML Editor, the transformation process produces an XML mapping file called context-help-map.xml and copies it in the output folder of the transformation. This XML file maps an ID to a corresponding HTML page through an appContext element, as ...

Hi, I cannot reproduce your problem using oXygen Author 18.1. I've configured two transformation scenarios, each transformation scenario with its own DITAVAL file and output folder. I did not find any problem in the WebHelp output folders after I run the transformation scenarios. Both WebHelp output...

Hi, Did you know about DITA Map to PDF WYSIWYG Transformation? Oxygen XML Editor comes bundled with a DITA-OT plugin that converts DITA maps to PDF using a CSS layout processor. This plugin and the Author page use the same set of CSS stylesheeets, so a change in these CSSs will affect the rendering ...

Hi,

Thank you for sharing with us your solution.

Hi,

I forgot to say I've tested with a regular DITA map. For a DITA bookmap the temporary file structure and XPath expressions might be little different.

Hi, I am trying to change the note icon used for pdf generation from oxygen Author using the default org.dita.pdf2 plugin. I see that it is using Code: Select all \Oxygen XML Author 18.1\frameworks\dita\DITA-OT2.x\plugins\com.oxygenxml.pdf.custom\custom.xsl and Code: Select all \Oxygen XML Author 18...

Hi, First of all, please note that my response is based on DITA-OT 1.8.5 . Few words about PDF 2 plugin development Whenever you develop a PDF2 plugin customization, it is useful to explore the temporary files produced by the DITA-OT PDF2 transformation. These files are usually generated in the temp...

Hi, Please note that my response is compatible with DITA-OT 2.3.3 that is bundled with oXygen 18.1 . To render a note image, the DITA-OT PDF2 plugin generates a fo:table with one row and two cells. On the first cell is drawn the note image and in the second its text. This is implemented in the DITA-...

Hi,

You can contribute additional JavaScript resources to change the default WebHelp behavior.

You can find more information about this task our user manual:
* Adding Custom HTML Content in WebHelp Responsive Output
* Copying Additional Resources to WebHelp Output Directory

Hi, We have choosen to disable the titles numbering because it is done in the context of the topic that includes the figure, and not in the context of the DITA map. So, if you have two topics that contains figures then the numbering will be reset in the second topic. To disable this customization yo...

Hi, A DITA-OT PDF2 customization plugin that can be configured to generates numbers before topic's title is available on GITHUB: https://github.com/radu-pisoi/org.dita.pdf2.topic.numbering. It was tested with DITA-OT 2.4. To install this plugin please follow the next steps: Download DITA-OT 2.4 Copy...

Hi, This is a known issue and it is related to the fact that Apache FOP processor does not support the XSL-FO elements for indexing, see the Formatting Objects for Indexing section from the Apache FOP documentation https://xmlgraphics.apache.org/fop/compliance.html#fo-object-index-page-number-prefix...

Hi,

This problem seems to be related with the Antenna House processor because it cannot be reproduced with Apache FOP or RenderX XEP.

Thus, I think the best place to address this question is the Antenna House support, see: https://www.antennahouse.com/antenna1/c ... uidelines/.

Hi, The WebHelp search function relies on a small collection of files that store all the words from the HTML files included in the WebHelp output folder. These configuration files are generated by the WebHep Indexer task at build time by searching for HTML files in the output folder. Therefore, a so...

Hello,

Could you give us more details about your use case?

Do you have a collection of HTML files already generated that you want to be queried when you use the WebHelp search function?

Where are these HTML files located? Are they in the same folder with the DITA map?

Hi, You can control the names generated by the Docbook chunking mechanism by using the dbhtml processing instruction embedded in the element: <chapter><?dbhtml filename="intro.html" ?> <title>Introduction</title> ... Another solution is to specify the id attribute for all elements that sta...

Hi, I don't see any problem, your XSLT customization seems to impose the 'content-width' and 'content-height' traits to 50% when @scale, @width and @height attributes are not set. Maybe you should also handle the case when the @scale attribute is set. For cases like this, I think you can try the nex...

Hi,

You can add the above XSLT customization stylesheet in the cfg/fo/xsl/custom.xsl file. See the step 6 from the procedure you refer, http://www.dita-ot.org/dev/dev_ref/pdf- ... ample.html.