An HTML attachment was scrubbed... URL: http://www.xmlmind.com/pipermail/ditac-support/attachments/20091021/e60e3383/attachment.htm -------------- next part -------------- Hussein, Thank you for the quick response. Can I expect a notification when the bug is fixed or should I periodically check the download page for a new version of DITAC? Regards,
Chris ~...@-@~ Chris DeMattio Sr. Engineering Manager Seagate Technology, Inc. 389 Disc Drive Longmont, CO 80503 (720) 684-2663 (SeaTEL 8 684-2663) christopher.demattio at seagate.com ------------------------------ This email contains information which may be confidential and/or privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in or attached to the email. If you have received the email in error, please destroy it and advise the sender of this email immediately by telephone or email provided herein above. ________________________________ From: Hussein Shafie <[email protected]> [mailto:Hussein Shafie <hussein at xmlmind.com>] Sent: Wednesday, October 21, 2009 2:59 AM To: Christopher.J.Demattio at seagate.com Cc: ditac-support at xmlmind.com Subject: Re: [ditac] Filtering Christopher.J.Demattio at seagate.com wrote: > > I seem to be having problems filtering dita content with the dita converter. > > In the DITA-OT, they support a concept of a default filtering action > followed by a more specific action. For example, the following syntax > filters out all content marked with the 'audience' attribute unless the > attribute has a value of 'external'. > > < prop att="audience" action="exclude" /> > < prop att="audience" val="external" action="include" /> > > For reference, please refer to the DITA 1.1 Language specification, for > the 'prop' element, where they say: > > "There can be at most one occurrence of a "prop" element with no > attribute specified (setting a default action for every prop element), > at most one for each attribute with no value specified (setting the > default action for a specific attribute), and at most one with each > attribute value specification (to avoid conflicting actions for the same > attribute value)." > > > When I test the above syntax in the DITA-OT, it works as expected. > However, when I do the same in the dita converter, all output marked > with an audience attribute is excluded, including that which is marked > with 'external'. > > Does the dita converter support the concept of default attribute values? > Yes. This is obviously a bug. We'll fix it and we'll make available a patch in the next few days.
