Douglas W Philips wrote: > 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.
If this is the case with ditac 2.x, then please report this problem as a bug (which I cannot reproduce; see below). > 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. The id attribute of a topic must be an NCName (may not be completely numeric). The id attribute of any element contained in a topic must be an NMTOKEN (may be completely numeric). Ditac, which is not a DITA validator, will replace any id value which is not an NMTOKEN, and this for all kinds of elements. Therefore completely numeric 'id' values are always accepted by ditac 2.x. (I've retested that.) We have no problem issuing a warning when an id is automatically replaced by ditac 2.x. This will be done in the next release of ditac 2.x. > > 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 filtering > attributes at the topic/concept level? > The filtering attributes are honored at topic/concept level, except that you cannot filter out the topic/concept itself. In order to do that, you indeed have to set the filtering attribute on the corresponding topicref. We forgot to specify this important change in the release notes of ditac and we are really sorry that you get caught by this limitation. We'll of course document it in the next release of ditac 2.x. Unfortunately, the current implementation of ditac 2.x makes it quite difficult to revert to the behaviour of ditac 1.x. -- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
