Oxygen XML Forum

Hi,

I found the page https://www.oxygenxml.com/doc/versions/ ... brary.html to render PSD (Adobe Photoshop) images in Oxygen XML Editor.
As (many of) our graphics are created in photoshop, using PSD files in Oxygen seemed like a very interesting solution. We then can use the source files instead of generating files specifically for publishing.
But although the image appears in XML Editor and also prints correctly to PDF, I cannot get it to work in Webhelp. I assume this is because the transformation does not convert the graphic, but publishes it as is and HTML does not support PSD?
Is any solution on the horizon? Otherwise we will have to stick with creating extra images for publishing and revert the installation of the JAR files as its of no use to us then.

Best regards
Jan Willem

Image processing is a pain in a DITA environment. The DocBook-based Paligo system cam handle Adobe formats natively and IIRC convert them on-the-fly. In a DITA environment you have to IMHO convert AI->SVG and PSD->PNG manually. And you have to fiddle out the correct export settings in Illustrator. Our technical illustrators work on SharePoint and the technical writers copy the covered files to Git.

In my experience, as long as you stick to the 'standard' image formats, working with images works fine.
As for Paligo, we've used that in the past, but as with most of the CMS-based solutions, choosing a package/proram means you're stuck with it. Exports use all kinds of internal IDs in filenames and references, which makes moving to another system harder. DITA is a standard, but unfortunately CMS-es aren't. We are very happy with the much easier (and a lot cheaper) solution we have now, Oxygen, Git, and Photoshop. But directly using the photoshop files would make the process even simpler.

Hello,
Unfortunately, we do not have an existing workaround for the issue you're facing. A possible solution involves the development of a custom DITA OT plugin which would convert the images upon generation.

We have logged an issue to our internal tracking tool to be further investigated by our development team. We will let you know if/when this will be implemented.