Ok, I think you've misunderstood me. Your source will look exactly as it does now except that you'd add some kind of flag on the wrapper chapter element (like role="dummy") and then match that with the proposed xslt. So you can still see the sections in your editor if it supports xinclude and you can still validate the xincludes with xmllint. In your build script, AFTER you have had a processor resolve the xincludes but before it passes the resolved document to the DocBook xsls, it runs the proposed xslt on the source.
Now it's true that in your editor, the toc will still look funny, but at least in the output, things will be ok. David ________________________________ From: [email protected] [mailto:[email protected]] Sent: Monday, July 26, 2010 3:28 PM To: Cramer, David W (David) Cc: '[email protected]'; 'DocBook Technical Committee' Subject: RE: [docbook] Sections and topics Thanks David, I'm reluctant to go the XSLT route because our team REALLY values being able to see the xincluded information resolved in our authoring environment. Thanks, Kate .......................................................................................................................................................................................................................... Kate Wringe | Tech Writer 2| Sybase 445 Wes Graham Way, Waterloo, ON, N2L 6R2 Canada | Tel: (519) 883-6838 | [email protected] | www.sybase.com
