On 06/21/2011 06:15 PM, Douglas W Philips wrote: > On Tue, Jun 21, 2011 at 6:34 AM, Hussein Shafie <[email protected] > <mailto:[email protected]>> wrote: > > 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). > > > Ok. I was able to reproduce this on 2.0.2, and will file a separate bug > report. > Since we have already converted our id values to something more human > readable, this isn't a show-stopper for us right now. > I will have to see if I can create a small sample example to demonstrate > the bug, so it may be later in the week until I can get it submitted.
Thank you for taking the time to do this. > > 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. > > > I'm not sure what you mean by this. > What we are seeing is that the content of a concept is present in the > final document, which was not true for 1.2.1. > With 2.0.2 it is as if the concept's attribute filter was not even present. Let's suppose your .ditaval file is: --- <val> <prop action="exclude" att="audience" val="expert"/> </val> --- [A] With ditac 1.x, if you wanted to exclude myconcept.dita, you had to specify audience="expert" on the <concept> element. <concept audience="expert"> ... </concept> [B] With ditac 2.x, let's suppose you map contains: <topicref href="myconcept.dita" /> if you want to exclude myconcept.dita, you must specify: <topicref audience="expert" href="myconcept.dita" /> ditac 1.x did not support [B]. In our opinion, [B] is more useful and more intuitive than [A]. Now, we'll see what we can do to support both [A] and [B] in ditac 2.x. However, I cannot promise that we'll succeed in removing this limitation. -- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
