Licensing restrictions for the Oxygen Webhelp transforms?

Here should go questions about transforming XML with XSLT and FOP.
Posts: 16
Joined: Tue Feb 03, 2015 3:23 am

Licensing restrictions for the Oxygen Webhelp transforms?

Post by misty » Wed Apr 20, 2016 6:36 pm


We'd like to use one of the Webhelp transforms as the basis for some documentation we include as part of our product. Are there any restrictions we should be aware of? Of course every writer at my company holds a valid Oxygen license. Thanks in advance for your help.


Posts: 45
Joined: Wed Jan 08, 2003 9:43 am

Re: Licensing restrictions for the Oxygen Webhelp transforms?

Post by stefan » Thu Apr 21, 2016 5:50 pm

There are two alternative ways to generate the WebHelp output:
a) within a valid licensed Oxygen XML application (by manually running the corresponding transformation)
b) using an automated process (like a script, command line) outside Oxygen XML application, by means of a special license (see

Using any of the above variants, you are permitted to make copies of the WebHelp generated output, and distribute those copies to your end users (as part of your product documentation, published on the web, a.s.o); provided that you comply with third party components license terms requirements that are distributed with the WebHelp generated output and ensure all copyright or other proprietary rights notices of Syncro Soft or its third party suppliers contained in files that bear such a notice are retained.

The rationality of these requirements relies on the structure of the WebHelp output, that is composed of not only of your own content but also css/js/php (usually scripting files) that provides additional functionality (search, feedback,...). While most of such scripting files are developed by our company, some of them are inherited from open-source projects (jQuery JS libary, etc) and licensed under not-viral open-source licenses (Apache 2.0, MIT, BSD) that would not create additional obligations for you or your end-users rather than proper attribution (assuming you are not performing any changes on them). To better compy with this requirement, starting with version 18, a license-3rd-party.txt file is added to the WebHelp output main directory in order to list the third party scripts.

If you require further clarification on licensing terms, please direct your questions to

Post Reply