DITA and XMetaL Discussion
sbodoff June 29, 2010 at 12:28 am
XMetaL rewriting bookmap DOCTYPEJune 29, 2010 at 12:28 amParticipants 1Replies 2Last Activity 12 years ago
The DOCTYPE of the bookmap is
However, when I save my bookmaps, XMetaL keeps replacing it with this:
which doesn't work for bookmaps that are being read into production tools. Why is this happening and how can I stop it?severin.foreman June 29, 2010 at 12:32 am
Reply to: XMetaL rewriting bookmap DOCTYPEJune 29, 2010 at 12:32 am
The doctype declaration should be:
XMetaL will resolve the location of the DTD file based on the public ID and a combination of proprietary and DITA OT catalog files.Derek Read June 29, 2010 at 6:34 pm
Reply to: XMetaL rewriting bookmap DOCTYPEJune 29, 2010 at 6:34 pm
The problem is that XMetaL Author Enterprise 220.127.116.11 is actually inserting full path or relative path to our “stub” DTD, which is not desirable. sbodoff didn't say which version is being used, but I assume it is 18.104.22.168 as that is the version I am aware of that has this issue.
The preferred form is in fact this:
This issue only affects bookmap and to the best of my understanding we caught it fast enough that there is only one affected version (22.214.171.124).
Version 6.0.1.030 (available since May 26) addressed the issue. Our sales people can help anyone that needs this version to obtain it.
The fix should continue to respect the SYSTEM portion of the DOCTYPE declaration in existing files when opening and saving (and leave them unchanged), so if you have files that were messed up by 126.96.36.199 the XML source may need tweaking. The fix is for new files created from template from within XMetaL Author Enterprise (ie: File > New).
If you are using a CMS system and you create new files using the Repository menu item called “New from Repository Template” that should also work fine (such CMS integrations are based on our “XMetaL Connector” APIs specifically designed to interop nicely with CMS systems).
If you are using a CMS system and the Repository menu is disabled (you create new documents some other way) then I cannot predict what the behavior will be for you as the CMS system is custom coded and not using our standard “XMetaL Connector” CMS-specific APIs. However, as stated above, the product is coded to respect the DOCTYPE declaration for existing documents. This basically means any documents not opened from the Template folder in the XMetaL installation path, so I assume things should continue to function for such integrations as well (and likely were not affected in the first place).
- You must be logged in to reply to this topic.