This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: xsl:param and replace.xsl
- From: DPawson at rnib dot org dot uk
- To: xsl-list at lists dot mulberrytech dot com
- Date: Fri, 14 Dec 2001 09:06:40 -0000
- Subject: RE: [xsl] xsl:param and replace.xsl
- Reply-to: xsl-list at lists dot mulberrytech dot com
Mike Kay said.
> An XSLT processor produces a result tree from a source tree.
> The source tree
> is immutable. It would be possible in principle for the
> serialized result
> file to overwrite the original serialized input file, but I
> can't see a good
> reason for wanting to do that, and many good reasons for not doing it.
I've just spent the last week doing that in a python program.
Requirement was to convert an e-book from version x to version y.
Needed all the same filenames, variant (transformed) content.
rename original to .bak
transform xxx.bak to xxx.xml
'transformInPlace' was the function name.
That's the use case anyway.
Regards DaveP
-
NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the
intended recipient you are hereby notified that you must not use,
disclose, distribute, copy, print or rely on this email's content. If
you are not the intended recipient, please notify the sender
immediately and then delete the email and any attachments from your
system.
RNIB has made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list