Hi belinda, Unfortunately, filtering the comments by specific users / reviewers is not supported in the current implementation of Oxygen Feedback. The only filters available are the ones from the top side of the view, which you already found. I've just added a feature request in our internal trackin...

Hi Belinda, Even if adding comments for a specific selection is not supported, Oxygen Feedback supports block-level comments. This feature allows users to add and manage comments contextually at a specific location within the output page where block elements appear, such as sections, paragraphs, lis...

Hi,

This is not supported in the current version of Feedback,
However, as we have a feature request already logged, I've just added your vote for it. We will get back to this thread when user mentioning will become available in a future version of the software.

Regards,
Costin

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

Hi Konrad, Thank you for the feedback you provided! We are aware of this issue and we have it already logged in our internal tracking system. Therefore, I've just added your feedback to it and tried to prioritize it. We will notify you by replying back on this thread whenever a fix will be implement...

Hi felixliu, In case there are elements whose syntax is not correct in one of the files in your DITA Map, the " content is not allowed in prolog " error may be thrown. It is recommended to open the DITA Map in the DITA Maps Manager view and validate it by running the " Validate and Ch...

Hi galanohan, This could be achieved by my manually editing of the DITA sources. Please follow the steps I described below: 1 - surround the fragment you want to be skipped from selection with a <ph> element 2 - add the @outputclass="ignoreSelection" class to the <ph> element which you jus...

Hi Naoki, As there were many versions released inbetween v21 and v26 and a lot of changes were implemented the WebHelp implementation with each newer version (if you would need a list of which specific changes were implemented between those versions, you could write us on our official technical supp...

Hi horisonten, We are aware of this issue which occurs on the latest version of WebHelp (26) and we have it logged already in our internal issues/improvements tracking system. Therefore, I've also logged your feedback on it and we will notify this thread when a new version that would implement the f...

Hi,
I also logged your latest feedback on the issue we have in our tracking system and tried to prioritize it.
We will reply back to this thread if a different implementation would become available.

Regards,
Costin

Hi horisonten, Could you please let us know which specific version of WebHelp did you use to test this functionality? Also, in order to look into this, we would need you to send us a sample DITA Map files hierarchy in an as minimal form as possible which we could use to reproduce the reported behavi...

Hi galanohan,

This is not possible using the current implementation of WebHelp, but we already have an improvement request logged for this in our internal tracking system, so I logged your vote for it and we will notify this thread when this will get implemented.

Regards,
Costin

Hi matt_k, Indeed, in the newer versions released between the versions 24 and 26 the structure of the DITA OT generated output may have changed, so you may need to update the rules in your customization CSS accordingly, to match specific elements from the output. To help you identify which selectors...

Hi Konrad,

The validation error occurs as the order of the <logo/> and <favicon/> elements is incorrect.
More specific, the <logo/> element should come first, followed by <favicon/>. If you switch the two elements, the error should not occur anymore.

Regards,
Costin

Hi, There is no out-of-the-box documentation for various customizations, but it is possible to customize the WebHelp output (including the colors for different elements) through a CSS customization. You can find more information on how you could use the CSS Inspector from your internet browser to in...

Hi Amit,

It is not very clear from the 2 images you attached which note do you refer to..
Could you highlight the specific area which contains the note you refer to and describe the issue in more details please?

Regards,
Costin

Hi Amit, As we are not aware of this kind of issues with the current implementation of WebHelp and judging by the look of the WebHelp output in the screenshots you posted, probably you are using a customization of your own (possibly through a custom publishing template). Please try using the default...

Hi, Which specific version of Oxygen / WebHelp are you using to run the transformation? From the feedback you provided, we understand that your temporary folder may still contain some debris from previous transformations. Therefore, please make sure that you set both the "clean.temp" and t...

Hi Galano, Thank you for the feedback you provided and for the sample! We were able to reproduce the behavior you reported using your sample. We are currently prepairing to release a new version of the Oxygen Feedback, so almost all of our HR are focused on implementing the features to be included i...

Hi Kim,

Unfortunately there is no official procedure to use a plugin for customizing the search engine in the WebHelp output.
Therefore, the only solutions would be the ones Beniamin already described, by using the methods linked in his reply just above in this thread.

Regards,
Costin

Hi davenz, The " webhelp.fragment.before.topic.content " was not available in the old version 21 so that is why it has no effect. If you need to use this parameter you need to use at least the version 23.1. According to the Upgrade eligibility period section from our Upgrade Policy , upgra...

Hi Konrad,
Yes, it should be the recommended approach.
We created that section in our user-guide, even to come to the help of the users that need to change the translations or create their own ones.

Kind Regards,
Costin

Hi Konrad, Please note that it is recommended to avoid at all costs editing the files from the DITA OT directly, because this could trigger issues which could be very hard to debug at a later time. Instead, Oxygen comes with support for localizing the output interface and there is a dedicated sectio...

Hi Aparna, It may be possible that you are using a customization that is different by the ones your colleagues use. Please note however that our support policy covers only the Oxygen functionality and issues that may occur when using the software without any customization (with the default DITA OT a...

Hello, I checked and the status of the issue in our system still appears as " open ". We will notify this thread when an implementation will become available. As we did not have many request for this (removing the collapsible sections from the output), most probably this won't be implement...

Hi MicTie,

For the time being there is no update regarding this.
We have the improvement request logged in our system and its status is still "open".
We will notify this thread when/if a different implementation becomes available.

Regards,
Costin

Hi gill_oxygen, The strings from the DITA-OT plugins developed by us (WebHelp / PDF CSS) already come with our own translations which we translated using authorized partners specialized in translations. However, if you noticed any incorrect translations in the default translations available for the ...

Hello,

As the improvement request was logged recently, there is currently no update.
The status is still "Open" in our internal tracking system. We will notify this thread when an implementation will become available.

Best Regards,
Costin

Hi Justyna,

So far, the issue still appears as open in our tracking system.
We will notify this thread when a new implementation will be available.

Regards,
Costin

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