Cart
|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Accounting for Arbitrary Wrappers Without Going Mad
 Within the scope of paragraphs it's not a big deal because the processing in that context is pretty simple. But above the paragraph level it gets pretty funky because the presence of the wrappers will throw off match statements. I could of course add match options that include the Epic change tracking elements, and would do so if that were the end of it. Unfortunately, I also want to do different processing based on the interaction of the change tracking markup and a parameter that's passed in (reflecting the "view change tracking" setting in Epic itself). I can't think of an elegant solution to this sort of problem. An easy solution would be to have the XPath matches simply ignore elements in a particular name space, but I don't think that's possible. That would at least keep the base transform working whether the wrappers were there or not. But it wouldn't solve the larger problem of explosion of matches and templates. I'm wondering if there's a general pattern for approaching this type of markup other than the brute force method? Thanks, Eliot -- W. Eliot Kimber, eliot@xxxxxxxxxx Consultant, ISOGEN International 1016 La Posada Dr., Suite 240 Austin, TX 78752 Phone: 512.656.4139 XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list 
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
