Subject: RE: Non-validating XSL processors From: Matthew Bentley <matthew.bentley@xxxxxxxxxxxxxx> Date: Mon, 25 Sep 2000 08:04:20 +1000 |
>But the simple way to solve the problem (assuming that it's a real problem >and not imagined) is to preprocess the source XML to replace the ampersands >with something else, and then postprocess the output to put them back again. Thanks Mike - this is actually what I've been doing - I translate from '&' to '$!$' - I was just wondering whether theres an alternative- Matt ===================================================================== WARNING -This e-mail, including any attachments, is for the personal use of the recipient(s) only. Republication and re-dissemination, including posting to news groups or web pages, is strictly prohibited without the express prior consent of Thomson Legal & Regulatory Group Asia Pacific Ltd ACN 058 914 668 ===================================================================== XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Non-validating XSL processors, mnaughto | Thread | RE: Non-validating XSL processors, Sebastian Rahtz |
Re: automatic numbering, Sebastian Rahtz | Date | RE: Non-validating XSL processors, Sebastian Rahtz |
Month |