DITA and XMetaL Discussion
bjorn May 15, 2014 at 9:05 am
dita4publishers – Dita specializationMay 15, 2014 at 9:05 amParticipants 3Replies 4Last Activity 8 years, 9 months ago
We are trying some different dita specializations to see if some of them suits our need out of the box, and at the same time see it we can implement them in XMetaL 9. But to implement the dita4publisher specialization wasn't so easy as some of the smaller specialisations.
We have tried to import the d4p-plugin with the apache ant tool that followed the XMetaL installation, but this can't be completed.
Does any people have experience with implement this plugin or just the specialization to XMetaL?
BjørnDerek Read May 16, 2014 at 12:03 am
Reply to: dita4publishers – Dita specializationMay 16, 2014 at 12:03 am
I think there are two pieces here.
1. The dita4publishers plug-in is included with the DITA OT bundled with XMetaL Author Enterprise 8 and 9 and some of the outputs it can create are exposed through the Generate Output dialog as “deliverables”. To see the full list, from the Tools menu select Configure Output. By default these deliverables are hidden so you also probably need to check the box marked “Show disabled deliverable types” to see them. Anything with “experimental” after the deliverable name is one of the d4p plug-ins.
2. For specializations, I guess we'd want to know exactly which one you are trying and what the issue is. Presumably this means that following the instructions in the Help (Working with DITA > DITA Specializations) are not working for a particular specialized DTD?bjorn May 16, 2014 at 12:17 pm
Reply to: dita4publishers – Dita specializationMay 16, 2014 at 12:17 pm
Hi and thanks you for a clarifying reply.
What we are trying to implement is the DITA4Publisher content model(see picture and attachment).
First I thought we had to implement the whole content model(with chapters, part, subsections, ++ dtds), but today we just tried to implement the article.dtd, this dtd contains many references to other *.mod and *.ent files.
After resolving the location paths in the dtd and reference files , we implement the dtd to XMetaL. After this the dita12_specialized.soc and the dita_xac_catalog_specialized.xml is updated with public id and reference to XACs folders article_ditabase.dtd.
When I opened the article template in XMetaL I get this message: “Rules checking cannot be turned on: The element classification is not allowed at this point in the container prolog.”. When I clicked “ok” the template opens, and after removing the classification element from the template the document is valid. After saving it, I thought I could insert it in to a ditamap, like I have done before with smaller dita specializations. But XMetaL doesn't recognize the article file as a dita file and won’t insert it (see pictures”NoDita.png”). Can you see anything that could stop this from working? Maybe there’s something with the id's I have overlooked? The files I have attached is the standard Dite4Publisherfiles.
Bjørnbjorn May 19, 2014 at 9:36 am
Reply to: dita4publishers – Dita specializationMay 19, 2014 at 9:36 am
I see that the Dite4Publisher content model is using “nextCatalog” to organize where to locate the dtds, ents and mods files. I can't find anything in the documentation or on the Internet regarding the use of XMetaL and nextCatalog.
Is this because every specialized dita dtd used in XMetaL has ble implemented through the tools > select specialized DITA DTD menu?
BjørnDerek Read May 20, 2014 at 7:58 pm
Reply to: dita4publishers – Dita specializationMay 20, 2014 at 7:58 pm
You must use XMetaL's method for setting up the software to recognize a specialized DITA DTD. XMetaL Author Enterprise uses its own catalog files and when you select Tools > Select Specialized DITA DTD that function adds appropriate entries to XMetaL's catalog files so that it can later find everything without prompting. A number of files are also generated that allow XMetaL to provide you with DITA authoring capabilities. The reason for this is that XMetaL Author is a fully customizable platform that allows a developer to create an authoring environment with special capabilities that make it easy to author to a particular DTD (any DTD). This one step tells XMetaL to put in place a number of files that make up the DITA authoring customization and set them up for use with your specialized DTD (via XMetaL's own catalog look-up). For any document type other than DITA, to add special authoring capabilities you need to create similar files or install a customization someone else has built for that DTD.
Paths between files in a specialized DTD also must resolve without the use of catalogs for all functionality in XMetaL Author Enterprise to be available (typically these are relative paths such as “../siblingfolder/somefile.mod”). This is documented as well. The reason for this is that for a few features XMetaL uses external parsers that do not support catalog look-up (including MSXML).
- You must be logged in to reply to this topic.