Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

DITA Specializations in Native PDF Publishing (Topics Disappear in PDF)

Avatar

Level 6

DITA Specializations in Native PDF Publishing (Topics Disappear in PDF)

 

We have one DITA specialization that appears to be properly configured in AEM Guides. I can insert it and use it in the XML Editor in topics and concepts.

 

In previous AEM Guides versions, this specialization appeared in PDF outputs, but that may have been using FMPS before Native PDF Publishing was released. I don't recall if I ever tested it in the earlier versions of Native PDF Publishing. We abandoned this specialization because there was no easy way to format it for the AEM Sites output. However, we'd like to return to using this specialization (which is based on the PARML element) since DITA is designed for easy customization and future releases will make it easier to format the AEM Sites outputs.

 

The specialization appears in the default DITA-OT PDF output. It is unformatted (expected behavior) because there is no easy to way format the DITA-OT files, but it does appear.

 

Currently (AEM Guides v4.6), the DITA specialization does the following:
1. In Native PDF Publishing output, any topic with the specialization does not appear in the PDF output. No title/heading, no content, no entry in the table of contents.
2. In AEM Sites output, any topic with the specialization is listed in the table of contents, but the output for that topic is empty/blank.
3. In the default DITA-OT output, the specialization appears, but is unformatted (expected behavior since these are the default DITA-OT files that aren't customized.)

 

What went wrong? Why does it appear that this specialization is correctly set up in the AEM Guides configuration, but doesn't output in Native PDF Publishing?

2 Replies

Avatar

Employee

@sschnelbach :

I understand you have not validated this with previous versions of Native PDF - but we do support specialized schema in Native PDF as well.

 

Few things to check here before this goes for debugging further:

- is the customized schema(or catalog files) integrated in DITA-OT?

- or is the custom catalog added to DITA Profile?

- and if you also validated this with version 5.0 (just in case you are planning upgrade) - the output preset has the option to use DITA-OT pre processing (for normalization of content) which should be enabled - check 5.0 release notes point#2 of this section

 

 

Avatar

Administrator

@sschnelbach Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!



Kautuk Sahni