Hi,
Yes, now how remember! So: write everything to a tree, along with file
references and log-report, and then write the tree out to the different
files, if memory is not an issue, or write the tree out and then split
that file, or do two passes ...
Thank you,
ac
On 13/08/2010 15:31, ac wrote:
Hi,
I am probably not understanding the problem correctly, but why not
build the report in a variable as the files are being processed and
then write it out to as a report file when the replacement task is done?
Thank you.
ac
When you're three levels deep in recursive calls of
xsl:result-document, there's no way of writing anything to a top-level
variable. In fact, you're not even allowed to call xsl:result-document
white writing to a variable, so it wouldn't work even if the calls
weren't recursive.
Michael Kay
Saxonica
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--