Hi felixliu, There is no out-of-the-box support for this in the current implementation of WebHelp . What you could do, would be to generate separate WebHelp output for each language in part, then you could try aggregating the outputs. As for the language toggle, this may be added through a customiz...

Hi, is there any way to add a feature of toggling languages to the webhelp responsive output?
That feature is commonly seen on other document websites, such as the language toggle near the upper right corner on this Google document website (https://cloud.google.com/docs).

Hi, We know about this problem and it's registered to be resolved in our system. This is a benign problem which should be ignored by you for now. We will work on our side to make some fixes in order to avoid presenting this message to our users. More details: When using a WebHelp publishing templat...

Hi Costin, Thanks for your support. I clicked the "Validate and Check for Completeness" button and no issue found. BTW, such error occurs right after the upgrade of version 26.1, build 2024031806. I'm not sure if there are any new software-level rules added to the WebHelp transformation pr...

Hi, when generating Webhelp Responsive files, an error of "content is not allowed in prolog" is displayed. I clicked the error message, and it directs to the ditamap file. I cannot figure out what is wrong here, and the generated Webhelp Responsive files look just fine. Should I overlook t...

Hi felixliu, Bu default, Oxygen WebHelp generates only a single version of the output. As there is no out-of-the-box support for managing different output versions, this could most probably done through a customization which you should develop on your own. We already have a feature request logged i...

Hi, I am wondering whether there is a way to implement documentation version switch (for example, this documentation site has a version switch in the upper-left corner) on the WebHelp output?
Thanks.

chrispitude wrote: ↑Fri Sep 16, 2022 2:24 pm Hi Felix,

On the pages where it does not stick, is it vertically larger such that it does not entirely fit in the browser view?

Hi chrispitude,
You are right. It is vertically larger than the browser view. Now I understand why it does not stick. Thanks for your help.

Regards.

Hi, when I generate WebHelp output, the table of contents part on the right (with a title of "On this page:") of some topic page will not stick at the top of the page when I scroll down the web page while other pages work fine. I am wondering is there any way to find out what's wrong here?

marius wrote: ↑Mon Sep 12, 2022 2:19 pm Hello,
It looks like a bug, however it is fixed in the current development stream, and the fix will be available in the next version of Oxygen XML WebHelp which will be released in a couple of weeks.
Regards,
Marius

Hi Marius, thanks for the information.

chrispitude wrote: ↑Mon Sep 12, 2022 2:56 pm

felixliu wrote: ↑Sun Sep 11, 2022 12:52 pmHi Alin,
I found a solution to this issue. Thanks for your reply anyway.

Hi Felix,

Just curious - what was your solution?

Hi, I insert a simple table in a CALS table, and then everything works just fine.

Hi, when I insert a code block in a table cell and transform the topic into WebHelp output, the table cell with the code block will go beyond the page to the right because the code block contains long text. Is there any way to solve this issue? Thanks.

Hello, I have tested your use case and I couldn't find any problem with the way the nested tables are displayed. https://www.oxygenxml.com/forum/files/nested-tables.png Can you please provide a minimal DITA sample (map + topic) and a screenshot that would emphasize the layout problem? Regards, Alin...

Hi, I inserted a table in a cell of the other table, and the inserted table looks just fine in the Author mode. But after transforming the topic into WebHelp output, the right border of the inserted table goes over its parent table. Can anyone help me understand what is wrong here and how to fix thi...

Costin wrote: ↑Wed Jul 06, 2022 11:47 am Hi felixliu,

This is intended behavior - only images with down-scaling are opened in a pop-up.
More specific, this functionality occurs only when you click an image whose display size is lower than the natural size of the source image.

Regards,
Costin

Got it, thanks.

When I insert images into a topic and transform it into WebHelp Output, why some images can be clicked and opened in a pop-up manner, but some images cannot be clicked? BTW, I use all default attributes for images and didn't make any changes to the attributes.

Hi Felix, If you want to exclude the topic from the navigation/TOC but keep the topic itself in the output, you could try setting the @toc="no" attribute on the topic reference in the map. If you want to exclude the topic completely from the output, then you could set a profiling attribut...

Taking this page as an example, is there any way to hide some topics under Publishing? For example, if I want to hide Transformation Scenarios and all the topics under it, how can I achieve that?

Hi Felix, If you just want to omit the header, maybe you could apply a "display: none" CSS property to the header content (if it is completely contained in its own element). Here is some documentation on how to identify the correct selector: How to Use CSS Styling to Customize the Output ...

Hi Felix, There are several YouTube videos that cover WebHelp customization: oxygenxml on YouTube - "customize webhelp" I am currently partway through the most recent video posted two months ago. Basically, you use your browser's CSS inspector to find the class of the element you want to ...

Hi Felix, I believe those are automatically generated child topic links. Here is another page that also has <related-links> at the bottom (with the heading): Home > Publishing > WebHelp Output Customization > WebHelp Responsive Output for DITA > Publishing Templates - Chris Hi Chris, Thanks for the...

I guess the documents list shown on this page is achieved by the <related-links> element. Just wondering how the title of Related information for that specific element is removed?

Hi Felix, DITA supports only a single level of <section> ; nested sections are not allowed. The page you referenced uses nested topics, then sections in those: https://github.com/oxygenxml/userguide/blob/0c5afbd2c1c28059490158c6043e2ad04eaf7d2f/DITA/topics/whr-html5-pages.dita Hi chrispitude, Thank...

Still wondering how to make H2, H3, even H4 titles on a single web page as on this web page. Help~

Hi felixliu, You can find my answers below: 1. How to achieve the same output as in this web page where multiple levels of headings exist in a single topic, and those headings are shown in the right-side TOC? For sections with ids the component is called topic Table of contents - A table of content...

Hi Cosmin,
Thanks for your help.

Regards.
Felix

Hi, I am new to DITA and oXygen, and have encountered a few puzzles. Wondering anyone know the answer to the following: 1. How to achieve the same output as on this web page where multiple levels of headings exist in a single topic, and those headings are shown in the right-side TOC? 2. Is there any...