Pages: 1
Author Topic: DITA Ids not being assigned  (Read 1716 times)

Posts: 20

« on: September 07, 2013, 06:17:19 PM »

We have upgraded to XMetaL 8 SP1 Author Enterprise from XMetaL 6 SP1. We have observed an issue with XMetal 8 SP1 where DITA Ids are not being to all the content tags in the document. I have debugged with XMetal Developer 7 and looks like in nulAssignElements method in Library_ID.js macro the node list is not being traversed properly. Following is code snippet.

  //get ndl here
  var readPosition = 0;
  for (var i=0; i < len; i++){
    var nde = ndl.item(readPosition); //readPosition is always 0

The behavior is that only the first tag in the document will be assigned DITA id. The code words in XMetaL 6 SP1 since the nodelist pops the item instead of a get in the list.

Please advice if our observation is correct and if the fix is available.



Posts: 265

« Reply #1 on: September 09, 2013, 08:59:37 AM »

You might check Tools > DITA Options > General Tab >  Options button (next to Auto-assign element IDs).
Derek Read
Program Manager (XMetaL)

Posts: 2579

« Reply #2 on: September 10, 2013, 02:16:34 PM »

This does not look like our code so I'm not sure what is being discussed here.

The only supported method for introducing changes to (some) DITA functionality with script is to implement those changes in specifically defined JScript prototype overrides.

This is undocumented (partners are typically involved in this work) but there is an example here:
C:\Program Files\XMetaL 8.0\Author\DITA\XACs\1.2\ditabase\

That example must be renamed to remove the ".off" portion to be enabled. If a different DITA document type needs similar overrides to be made then the file needs to be duplicated into the corresponding folder for the other DTD, renamed to correspond to the base DTD file name in that folder, and all prototype declarations in the file must be similarly renamed.

Other types of changes are unsupported.
Pages: 1
Jump to:  

email us