Hello Hussein, thank you very much for your support and the informations about audience. with the latest release (4.4.2) all works fine. And i will get the ToC i expected ;-)
So i think, we would buy some "Professional Edition"-Licences in the next time ;-) Best regards, Martin Schild -----Ursprüngliche Nachricht----- Von: Hussein Shafie [mailto:[email protected]] Gesendet: Donnerstag, 13. Januar 2011 17:38 An: Schild Martin Cc: [email protected]; [email protected] Betreff: Re: [XFC] Question about xsl utility and ditaval-files On 01/13/2011 03:50 PM, Schild Martin wrote: > Hello, > i am using XSL Utility 4.4.1 > That's what I suspected. Please upgrade to latest release which is XSL Utility 4.4.2. This should fix the bug you have described. (I have checked that using attached files.) Now some details about the behavior of XSL Utility 4.4.2. The following map, filtered using the .ditaval below, will give you a .pdf file containing topicA and topicD. And its TOC will list "Topic A" and "Topic D". Which is what you expect. --- <topicref href="topicA.dita"/> <topichead audience="Opacc-Lab" navtitle="Topichead title here"> <topicref href="topicB.dita"/> <topicref href="topicC.dita"/> </topichead> <topicref audience="OTHER" href="topicD.dita"/> --- (Remember that attribute "audience" cascades. Therefore <topicref href="topicB.dita"/> and <topicref href="topicC.dita"/> virtually have both audience="Opacc-Lab".) While the following other map, filtered using the .ditaval below, will give you a .pdf containing topicA, "Topichead title here", topicC and topicD. And its TOC will list "Topic A", "Topichead title here", "Topic C" and "Topic D". --- <topicref href="topicA.dita"/> <topichead audience="Opacc-Lab" navtitle="Topichead title here"> <topicref href="topicB.dita"/> <topicref audience="OTHER" href="topicC.dita"/> </topichead> <topicref audience="OTHER" href="topicD.dita"/> --- (Remember that attribute "audience" cascades, in an additive way. Therefore <topicref href="topicB.dita"/> virtually has audience="Opacc-Lab and <topicref audience="OTHER" href="topicC.dita"/> virtually has audience="Opacc-Lab OTHER".) That is, because the topichead contains a non-excluded topicref (the one with href="topicC.dita"), the topichead will *not* be excluded. This behavior is dictated by common sense more than by the DITA spec, which does not explicitly specify what to do in the second case. > Regards, > Martin Schild > > -----Ursprüngliche Nachricht----- > Von: Hussein Shafie [mailto:[email protected]] > Gesendet: Donnerstag, 13. Januar 2011 15:41 > An: Schild Martin > Cc: [email protected] > Betreff: Re: [XFC] Question about xsl utility and ditaval-files > > Which version of XMLmind XSL Utility are you using? This is shown in the > title of its window. > > On 01/13/2011 01:33 PM, Schild Martin wrote: >> Hello, >> >> i am using XMLmind XSL Utility for evaluation in my company. >> >> >> >> Most things are working fine. >> >> I use XSL Utility to convert DITA-files to PDF. >> >> Now i have a question about audience and ditaval-files. >> >> >> >> In my ditamap, i have a topichead with some topicrefs. Both >> (topichead and topicrefs) have an audience. >> >> My ditaval file contains the following "exclude-rule" >> >> >> >> <val >> >> <prop action="exclude" att="audience" val="Opacc-Lab"/> >> >> </val> >> >> >> >> When i now convert the ditamap and his files to PDF, the content of >> all the topicrefs will be exclude. That's ok. >> >> My problem is, that in the table of content in the PDF, the title of >> the topichead is still present. >> >> >> >> Do i make something wrong? >> >> >> >> Best regards and thank you for feedback. -- XMLmind FO Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xfc-support
