Hello support team, hello Oxygen users,
Where should WebHelp Responsive be deployed?
* On a server?
* On a local computer (i.e., installed together with the application it is created for)?
Do I lose functionality if WebHelp Responsive does not run on a server?
Freundliche Grüße | Best regards
Frank Dissinger
Documentation Manager
..........................................
CGS ORIS GmbH
Email frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://www.cgs-oris.com/>
Address Kettelerstrasse 24 | 63512 Hainburg | Germany
Phone +49 6182 9626-0 | Fax +49 6182 9626-99
Commercial register Offenbach, HRB no. 21495
Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji
[cid:image001.png@01DCCC1E.2F6A19C0]<https://www.cgs-oris.com/>
_______________________________________________
oXygen-user mailing list -- oxygen-user(a)oxygenxml.com
To unsubscribe send an email to oxygen-user-leave(a)oxygenxml.com
Thank you, Julien, for your reply.
I have heard about DITA-OT Project Files, but have no experience with them. Before I dig deeper into this matter:
* Can I use these DITA-OT Project Files in an Oxygen transformation scenario?
* Or do I have to start the transformation from an external script?
* If I need an external script, do I have to purchase this 3,543 € WebHelp license?
Regards, Frank
Von: Oxygen XML Editor Support (Julien Lacour) <support(a)oxygenxml.com<mailto:support@oxygenxml.com>>
Gesendet: Mittwoch, 15. April 2026 09:50
An: Frank Dissinger <frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com>>
Betreff: Re: [OXYGEN-47705] [oXygen-user] First steps with WebHelp Responsive
Hello Frank,
The transformation scenario represents the actual output you want to generate (such as WebHelp Responsive, CHM, PDF, etc.) while the publishing template is a customization package passed as parameter to the scenario. You can find more details about publishing templates here<https://www.oxygenxml.com/doc/versions/28.1/ug-webhelp-responsive/topics/wh…>.
As you need to produce different outputs using different colors, logos, etc. I think the correct use-case is to have multiple transformation scenarios. One solution to keep them in a single location is to create deliverables in a DITA-OT Project file<https://www.dita-ot.org/dev/topics/using-project-files.html>.
Another possibility is to create a scenario using the ${ask} editor variable<https://www.oxygenxml.com/doc/versions/28.1/ug-editor/topics/editor-variabl…> to set some parameters such as logo or CSS.
If you are at ease with Ant, you could try to create a custom DITA-OT plugin with your own transtype that further calls the WebHelp Responsive transformation after setting the variables.
Regards,
Julien
On 4/14/2026 5:33 PM, Frank Dissinger wrote:
Hello all,
I am a bit confused. There are transformation scenarios and publishing templates.
What is each used for?
Where are these things stored? I want to add them to our source code repository to have a version history and backup.
I need to create WebHelp Responsive for various products in various languages.
There is a shared company logo for all products. If we create OEM versions one day, however, the company logo will vary.
There is a separate product logo for each product.
There is a separate project folder for each product and language, which holds the root ditamap that will be processed.
There is a separate output folder for each product and language.
There is a special color for each product. This color should be set for:
1. The background of the Search panel in the main
2. The shortdesc element that follows a topic title; figure titles; table titles (to be handled via CSS variables)
I wouldn’t like to have a separate transformation scenario for every single publication. I would like to maintain only a minimum of files. How should I organize this?
Ideally, all this information could be retrieved automatically from the ditamap being published.
Can Oxygen create custom editor variables from ditamap information?
Or can I start the transformation from a script that prompts the user for this information? Or call a script from the scenario?
For CHM output, which I did previously, I created an ANT script which asked for the product and language and, based on user input, set the name of the ditamap to process, the language, output directory, location of resources such as logos, etc.
Best regards
Frank Dissinger
Documentation Manager
..........................................
CGS ORIS GmbH
Email frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://www.cgs-oris.com/>
Address Kettelerstrasse 24 | 63512 Hainburg | Germany
Phone +49 6182 9626-0 | Fax +49 6182 9626-99
Commercial register Offenbach, HRB no. 21495
Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji
[cid:image001.png@01DCCCE4.3058AD80]<https://www.cgs-oris.com/>
_______________________________________________
oXygen-user mailing list -- oxygen-user(a)oxygenxml.com
To unsubscribe send an email to oxygen-user-leave(a)oxygenxml.com
Thank you, Julien, for your reply.
My company has decided to deploy the help on the local computer, not on a server.
Fortunately, none of your points seems to affect us:
* I do not create an Index
* Google Search? Users can do that on their own in their web browser.
* A feedback mechanism would be good a good idea, but not an option for my company at the moment.
Regards, Frank
Von: Oxygen XML Editor Support (Julien Lacour) <support(a)oxygenxml.com<mailto:support@oxygenxml.com>>
Gesendet: Mittwoch, 15. April 2026 09:19
An: Frank Dissinger <frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com>>
Betreff: Re: [OXYGEN-47679] [oXygen-user] First steps with WebHelp Responsive
Hello Frank,
Usually WebHelp Responsive outputs are made to be deployed on an HTTP Server (such as Apache HTTP Server).
If you keep the files locally you will not have access to the following features:
* The Kuromoji analyzer<https://www.oxygenxml.com/doc/versions/28.1/ug-webhelp-responsive/topics/in…> used to index Japanese content
* The Google Search Integration will not work
* Oxygen Feedback search and comment section cannot be used
Regards,
Julien
On 4/14/2026 3:51 PM, Frank Dissinger wrote:
Hello support team, hello Oxygen users,
Where should WebHelp Responsive be deployed?
1. On a server?
2. On a local computer (i.e., installed together with the application it is created for)?
Do I lose functionality if WebHelp Responsive does not run on a server?
Freundliche Grüße | Best regards
Frank Dissinger
Documentation Manager
..........................................
CGS ORIS GmbH
Email frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://www.cgs-oris.com/>
Address Kettelerstrasse 24 | 63512 Hainburg | Germany
Phone +49 6182 9626-0 | Fax +49 6182 9626-99
Commercial register Offenbach, HRB no. 21495
Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji
[cid:image001.png@01DCCCDE.DF0FC170]<https://www.cgs-oris.com/>
_______________________________________________
oXygen-user mailing list -- oxygen-user(a)oxygenxml.com
To unsubscribe send an email to oxygen-user-leave(a)oxygenxml.com
Hello all,
I am a bit confused. There are transformation scenarios and publishing templates.
What is each used for?
Where are these things stored? I want to add them to our source code repository to have a version history and backup.
I need to create WebHelp Responsive for various products in various languages.
There is a shared company logo for all products. If we create OEM versions one day, however, the company logo will vary.
There is a separate product logo for each product.
There is a separate project folder for each product and language, which holds the root ditamap that will be processed.
There is a separate output folder for each product and language.
There is a special color for each product. This color should be set for:
* The background of the Search panel in the main
* The shortdesc element that follows a topic title; figure titles; table titles (to be handled via CSS variables)
I wouldn't like to have a separate transformation scenario for every single publication. I would like to maintain only a minimum of files. How should I organize this?
Ideally, all this information could be retrieved automatically from the ditamap being published.
Can Oxygen create custom editor variables from ditamap information?
Or can I start the transformation from a script that prompts the user for this information? Or call a script from the scenario?
For CHM output, which I did previously, I created an ANT script which asked for the product and language and, based on user input, set the name of the ditamap to process, the language, output directory, location of resources such as logos, etc.
Best regards
Frank Dissinger
Documentation Manager
..........................................
CGS ORIS GmbH
Email frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://www.cgs-oris.com/>
Address Kettelerstrasse 24 | 63512 Hainburg | Germany
Phone +49 6182 9626-0 | Fax +49 6182 9626-99
Commercial register Offenbach, HRB no. 21495
Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji
[cid:image001.png@01DCCC2A.18729F10]<https://www.cgs-oris.com/>
_______________________________________________
oXygen-user mailing list -- oxygen-user(a)oxygenxml.com
To unsubscribe send an email to oxygen-user-leave(a)oxygenxml.com
I have set various parameters (see Figure), now Oxygen generates only empty pages. What have I done wrong?
[cid:image001.png@01DCCC2E.86601D00]
Freundliche Grüße | Best regards
Frank Dissinger
Documentation Manager
..........................................
CGS ORIS GmbH
Email frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://www.cgs-oris.com/>
Address Kettelerstrasse 24 | 63512 Hainburg | Germany
Phone +49 6182 9626-0 | Fax +49 6182 9626-99
Commercial register Offenbach, HRB no. 21495
Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji
[cid:image002.png@01DCCC2E.86601D00]<https://www.cgs-oris.com/>
_______________________________________________
oXygen-user mailing list -- oxygen-user(a)oxygenxml.com
To unsubscribe send an email to oxygen-user-leave(a)oxygenxml.com
When I set "clean.output" to "yes", I get the following error:
System ID: C:\CGS\DOKU\DITA_projects\0000_recent\build\sources\enu\ctuner\help_oris-ctw.ditamap
Scenario: WebHelp Responsive CGS
Input file: C:\CGS\DOKU\DITA_projects\0000_recent\build\sources\enu\ctuner\help_oris-ctw.ditamap
Engine name: DITA-OT
Severity: fatal
Description: Transformation failed. C:\Program Files\Oxygen XML Editor 28\frameworks\dita\DITA-OT\plugins\org.dita.base\build_preprocess.xml:80:
Failed to merge ditaval files: C:\CGS\DOKU\DITA_projects\0000_recent\build\out\ctuner\help\enu\temp\ditaot.generated.ditaval
Why does Oxygen try to merge something with a ditaval file generated previously? I should be able to create output in an empty directory.
Freundliche Grüße | Best regards
Frank Dissinger
Documentation Manager
..........................................
CGS ORIS GmbH
Email frank.dissinger(a)cgs-oris.com<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://www.cgs-oris.com/>
Address Kettelerstrasse 24 | 63512 Hainburg | Germany
Phone +49 6182 9626-0 | Fax +49 6182 9626-99
Commercial register Offenbach, HRB no. 21495
Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji
[cid:image001.png@01DCCC27.C6A2EF70]<https://www.cgs-oris.com/>
_______________________________________________
oXygen-user mailing list -- oxygen-user(a)oxygenxml.com
To unsubscribe send an email to oxygen-user-leave(a)oxygenxml.com
Hi everyone,
We are happy to announce the release of *Oxygen Content Fusion
Enterprise 9.1*, the latest version of our DITA CMS for the AI era,
built to bridge the gap between XML experts and SMEs through structured
content, intuitive collaboration, and agentic AI workflows.
Version *9.1* makes collaboration faster and more transparent. You can
now use *@mentions* to bring specific teammates into a conversation, and
they receive an email notification with a direct link to the relevant
comment so they can respond quickly.
A new *Review Task Dashboard* gives you a centralized view of task
progress, including due dates, reviewer status, associated files, and
task details, making it easier to track reviews at a glance.
The visual editor, powered by the latest Oxygen XML Web Author, adds
sticky headers for large DITA tables, built-in *S1000D® issue 4.x*
editing support, and new developer APIs for customizing the review
experience. AI-assisted authoring is also enhanced with a new *Planner*
chat mode that can break complex tasks into multi-step plans and
delegate them to specialized AI agents.
More information about *Oxygen Content Fusion Enterprise 9.1* can be
found at:
https://www.oxygenxml.com/content_fusion/whats_new_enterprise.html
*Oxygen Content Fusion Cloud* is now available as a fully managed *SaaS
(Software as a Service)* platform, so you can use content management,
collaborative review, and automated publishing without local
installation or server maintenance. Find out more at
https://www.oxygenxml.com/content_fusion.html
Best regards,
Alin
--
Alin Belu
Oxygen XML Editor
_______________________________________________
oXygen-user mailing list -- oxygen-user(a)oxygenxml.com
To unsubscribe send an email to oxygen-user-leave(a)oxygenxml.com
