On Thu, Mar 25, 2010 at 6:48 AM, Hussein Shafie <hussein at xmlmind.com> wrote:
> Well, to our knowledge this works to a certain extent. See attached sample. > Hmm, well here is what I am doing that doesn't seem to work. I'm only attaching files that are new or changed from your attachments. If you happen to specify the audience differently in the map, there are > great chances that ditac will not be able to properly apply your > .ditaval file. This is not the case when you directly specify > conditional processing *attributes* on the topic and/or its descendant > elements. In other words, if you want it to work, keep it simple. > See attachment sample2.dita for a new topic. Revised sample.ditamap file: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "http://docs.oasis-open.org/dita/dtd/map.dtd";> <map> <title>Sample map</title> <topicref audience="newbie" href="sample.dita"/> <topicref audience="experts" href="sample2.dita"/> </map> sample.docx contains both despite the ditaval only turning on newbie (unchanged ditaval from your previous email). Command line was: /c/ditac-1_2_0/bin/ditac.bat -xfc c:/xfc_perso_java-4_3_2/bin/fo2docx.bat -filter sample.ditaval sample.docx sample.ditamap > We are reluctant to document how topicmeta's conditional processing > child elements (such as audience) are converted/merged to/with topic's > conditional processing attributes and/or with topic/prolog/metadata's > conditional processing child elements because > [1] This should be *clearly* documented by the DITA spec. > [2] In our opinion, it's a mess. > Agreed. When we first started our DITA eval, we testing using the DITA Open Toolkit and by putting the conditional elements on the topicref entries directly, as per our understanding of the DITA spec. > Additionally/related, while that description of limitations indicates > > that it is possible to flag 'ph' elements, such conditionals are not > > processed when they occur in the map/bookmap file itself (as > > sub-elements of the title element, for example). We consider that a bug. > > Being able to conditionalize a title is required so that the title will > > match the conditionalized contents of the resulting document. Previous > > experiments we did led us to believe this would work, but upon further > > investigation, that seems to have been the result of the title coming > > out of the first dita file, where conditional/filter processing is > working. > > > > This is clearly a bug which will be fixed in next release of ditac. > Thanks! -Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.xmlmind.com/pipermail/ditac-support/attachments/20100325/e64accf1/attachment-0001.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: sample2.dita Type: application/octet-stream Size: 287 bytes Desc: not available Url : http://www.xmlmind.com/pipermail/ditac-support/attachments/20100325/e64accf1/attachment-0002.dll -------------- next part -------------- A non-text attachment was scrubbed... Name: sample.ditamap Type: application/octet-stream Size: 281 bytes Desc: not available Url : http://www.xmlmind.com/pipermail/ditac-support/attachments/20100325/e64accf1/attachment-0003.dll -------------- next part -------------- A non-text attachment was scrubbed... Name: sample.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 7813 bytes Desc: not available Url : http://www.xmlmind.com/pipermail/ditac-support/attachments/20100325/e64accf1/attachment-0001.bin
