Why use cinclude to include a complete XML and use XSL to
filter again if you could do the same
directly with just one generate...
Simply to avoid confusion. When the file gets really long, the original
xml file is about twice the length of the resulting HTML file, I loose
track of where I am. So I'd rather divide it into two separate files.
I meant something like:
<match pattern="content/de/**.xml">
<generate src="{path to german content}/{1}.xml"/>
<serialize type="xml" />
</match>
<match pattern="content/en/**.xml">
<generate src="{path to english content}/{1}.xml"/>
<serialize type="xml" />
</match>
<match pattern="*/**.html">
<generate src="cocoon:/content/{1}/{2}.xml"/>
<!-- transformation -->
<serialize type="html"/>
</match>
Still separate xml files, but a simple generate in the match for html files and
no include transforms...
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
