Home Forums DITA and XMetaL Discussion Unusual problem with XMetal and specialized DITA DTD Reply To: Unusual problem with XMetal and specialized DITA DTD

Derek Read

Reply to: Unusual problem with XMetal and specialized DITA DTD

The only way XMetaL would tell you that your file is invalid in one instance but valid in another is that it is using two different DTDs depending on the location of the XML file, the SYSTEM and PUBLIC id and any catalog entries available that match the PUBLIC id. Check the SYSTEM path in the XML document to see that it is in fact pointing to the DTD in the same folder, and that the DTD itself does not reference any other files.

Note that XMetaL has an extensive catalog lookup mechanism in place for DITA documents and so if your XML file points to a DTD that cannot be found using the SYSTEM id XMetaL will use the PUBLIC id if present. If it finds a matching PUBLIC id in its catalogs then it will use one of the standard DITA DTDs that are installed with the product. I suspect that is what is occurring in your case.

You will want to deploy your specialized DITA DTD so that XMetaL provides you with a DITA authoring experience. You cannot deploy it to a random location as you can with any other DTD if you want XMetaL to recognize it as DITA. If you deploy your DTD using any other method than the one described in the following help topic then it will not be recognized as DITA. What that means is that XMetaL will auto-generate a basic customization for you (CSS and CTM file) giving you basic XML authoring experience, but none of the special DITA authoring functionality will be enabled.

see help topic: Working with DITA > Specializations (and all subtopics)