DITA and XMetaL Discussion
hhvmetaal February 11, 2015 at 10:17 am
"Could not find a Topic" error while editing metadata for specialization.February 11, 2015 at 10:17 amParticipants 2Replies 3Last Activity 7 years, 7 months ago
we're using XMetaL 9.0 Author Enterprise.
When choosing Insert/Topic Metadata from the menu I get a message “Could not find a Topic” on a DITA specialization. When using a standard DITA topic like “General Task” I get the window for adding/editing metadata.
Why is this? Does XMetaL not recognize that our specialization is a DITA Topic?
Has anyone else experienced this?
Thanks for your answers.
Huib Verweij.Derek Read February 11, 2015 at 9:09 pm
Reply to: "Could not find a Topic" error while editing metadata for specialization.February 11, 2015 at 9:09 pm
The software needs to be configured to recognize a particular DTD as DITA. In simple terms this means selecting the item Tools > Select Specialized DITA DTD and then following a few steps in a wizard to set that up.
However, you should also read this topic in the Help: Working with DITA > DITA Specializationshhvmetaal February 11, 2015 at 10:11 pm
Reply to: "Could not find a Topic" error while editing metadata for specialization.February 11, 2015 at 10:11 pm
just to be sure I repeated a manual import of our DITA specialization like you suggested using Tools/Select Specialized DITA DTD. Before that import I deleted the generated folder from AuthorDITAXACs1.2 and deleted the corresponding lines from dita12_speciliazed.soc and data_xac_catalog_specialized.xml.
XMetaL reported a successful import and after restarting the specialized DTD was found. However, with Insert/Topic Metadata I got the same response from XMetaL “Could not find a Topic.”.
The XMetaL version we use is XmetaL Author Enterprise 9.0.0.053.
Huib Verweij.Derek Read February 12, 2015 at 8:29 pm
Reply to: "Could not find a Topic" error while editing metadata for specialization.February 12, 2015 at 8:29 pm
Please see our email thread. In there (after looking at your files) I suggested that the paths needed to be corrected as you have one too many “../” in the path for some references to the standard DITA DTD files.
- You must be logged in to reply to this topic.