Unable to publish webhelp responsive in Oxygen XML Author 24.1

[vvkumarr]

Hi,
I am using Oxygen XML Author 24.1. I am getting following error on generating webhelp responsive and webhelp responsive is not generated. Please suggest a solution.
System ID: D:\XXX\XXX\XXX.ditamap
Scenario: DITA Map WebHelp Responsive - Copy
Input file: D:\XXX\XXX\XX.ditamap
Engine name: DITA-OT
Severity: fatal
Description: Transformation failed.
Error: java.lang.NullPointerException: Cannot read field "result" because "fi" is null
The process finished with exit code: 1

[Costin]

Hi Vvkumarr,

The DITA Open Toolkit which Oxygen transformations use is known to have some issues when there are DITA or image files which contain special characters (like apostrophe - ', slash - /, number sign - #, etc.) in their names.
You can find more details on those issues in the following bug reports from the DITA OT:
https://github.com/dita-ot/dita-ot/issues/2844
https://github.com/dita-ot/dita-ot/issues/4324

Therefore, you should double check that none of your files contain special character in their names and retry the transformation after you renamed any possible occurrences.

Regards,
Costin

[vvkumarr]

Hi,
As per the details given in the URL https://github.com/dita-ot/dita-ot/issues/2844 I have checked for special characters like apostrophe ', slash /, number sign # in the file name. I did not find any.

As per the details given in the URL https://github.com/dita-ot/dita-ot/issues/4324 I have checked if there is any slash / after the name of the image. I did not find any.
Still, transformation failed error is coming. Is there any other check to be done on these source files?

[marius]

Hi,
In order to assist you more effectively, we would greatly appreciate it if you could provide us with a minimal sample of your project to replicate the issue on our end (a ditamap and a few topics).
Please be informed that the current version of Oxygen XML Author is 26.1. We highly recommend testing your project on this latest release, as it is likely that the issue you are experiencing has been addressed.

Regards,
Marius