Home Forums General XMetaL Discussion External entity LI___1 Reply To: External entity LI___1

Derek Read

Reply to: External entity LI___1

The DITA DTDs only define one entity, the named character entity “nbsp” which is mapped to the non-breaking space character U+00A0.

There should typically be no need to use entities (text or otherwise) in DITA and I would avoid them and instead use the “content referencing” mechanism provided by DITA's conref attribute.

XMetaL Author Enterprise should not insert entities into a document unless specifically instructed to do so (though that can be done via script in addition to manual editing, so in theory a customized version of XMetaL could do this without you knowing).

In order for an entity to be referenced in a DITA document (because there are no entities except nbsp defined in the DITA DTDs) the entity would need to have been defined in the internal subset of the XML file in question, which would then appear something like this:



It would be best to check with the CMS vendor, the company that created the integration between the CMS and XMetaL, or any other tool vendors (if you use other tools to work with your files, including any automated processes).

It is extremely likely this entity is being added by another process external to XMetaL. You should be able to confirm this by checking a “clean” file (one with no entity declarations or references in it) into and out of the CMS using whatever means the CMS provides for this, external to the interface provided through XMetaL. If the file isn't “dirtied” by this method then you can suspect another tool or the connection between the CMS and XMetaL Author Enterprise (we refer to this connecting code as an “adapter”).

After you have eliminated all other possibilities and you suspect the adapter as being the cause you should check with the person or company that created the adapter. The adapter is essentially a set of scripts added to XMetaL that extends (and in some cases alters) the default behavior of XMetaL allowing it to interact with a CMS (adding check-in, check-out, and other actions the CMS supports). Such a script can be told to do virtually anything, including making modifications to documents open in XMetaL.