Actually, we had problems with this approach. We integrated a custom plugin on a local Windows machine but the DITA-OT failed on the Linux production server because of different file separators.It is probably a bit overkill, but you could try using the Windows Subsystem for Linux (https://learn.micr...

Hi Susan,Many thanks for this thorough information!Best regards,Frank

In addition to the overview table by @punagpal you should check whether advanced DITA mechanisms are supported by the respective publication pipeline, especially the indirect referencing mechanisms:key referencesconrefsconkeyrefsprofilingI have not yet tested the Native PDF pipeline in detail but I ...

Thanks for this post. Just some remarks:With the mapref element you usually don't need the "format" and "type" attributes.You should use the processing-role attribute and set it to "resource-only" for your key definition map.<mapref href="global-keys-map.ditamap" processing-role="resource-only" />Be...

Hi Divraj,Many thanks for this information. We tried to look this information up in the AEM Content Migration Guide available from https://helpx.adobe.com/support/xml-documentation-for-experience-manager.html but the manual is for AEM Guides 3.5 and dates from 2019 so it unfortunately is heavily out...

Hi,We faced a similar issue when moving our custom DITA-OT from a test environment that was on Windows to a Linux server. It is recommended to run the DITA-OT integrator script on Linux to avoid issues with path separators: https://experienceleaguecommunities.adobe.com/t5/experience-manager-guides/u...

Hi @DivrajSingh,You describe how to make changes to the original PDF2 DITA-OT plugin. However, best coding practices are to never modify any of the core DITA-OT code, but to create a separate PDF plugin instead. I see two options:Create a new transformation type - Will this work in AEM? Or requires ...

Just for the record the detailed hints from @DivrajSingh: Using a custom DITA-OT for publishing | Things to remember  

The error message points to the general problem that the DITA-OT can have difficulties resolving references when the DITA map is not on top level. You might try creating a wrapper map on top level and create the output from that map. HTHFrank