Hello,
    We've recently started to upgrade from DITAC 1.2.1 to 2.0.x and have run
into a few issues that surprised us based on our reading of the release
notes.

    First one has to do with the legal values for the 'id' attribute. The
release notes say that as of version 1.2.2_01, ids are NMTOKENs.
      Looking at the definition of NMTOKEN as defined here:
http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-Nmtoken
      It seems to us that completely numeric 'id' values should be
acceptable, but we had to convert all of our 'id' values to start with a
letter before DITAC would accept them.
      Also, the code (such as I understand it not being at all familiar with
the DITAC source) seems to reassign an 'id value if it gets one that it
doesn't like. It would have been very helpful to have gotten a warning when
that happens.

    Second one has to with filter at the topic level. In DITAC 1.2.1 we were
able to filter content from our final document by having filtering
attributes on the concept element in our topic files. With version 2.0.0 we
instead have to apply that filtering to the ditamap's topicref elements in
order to suppress entire topics from our output documents.
        I could not find where in the DITAC release notes that change was
listed (or perhaps it is there but I just don't understand it).
        This is a huge deal for us, and we are wondering if DITAC can revert
back to the 1.2.1 version behaviour of honoring the filttering attributes at
the topic/concept level?

    Thank you!
         --Doug
 
--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support

Reply via email to