This is the mail archive of the xsl-list@mulberrytech.com mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
> > > I have come across a problem when processing XML files produced > dynamically > > by a script pulling back data from a database. If there are reserved > XML > > characters within the database content being retrieved then some XML > parsers > > will throw up an error (depending on the character), so preventing > further > > processing (in this case transformation to html). The only > (unsatisfactory) > > solution I can think of at the moment is to CDATA every field I > retrieve > > dynamically, as I have no control over the input into the database. > > If you have sufficient access to the data to wrap it in CDATA, > couldn't you instead just fix the "reserved" characters (depending on > what precisely you mean by that) before letting the XSLT processor see > it? > > Michael But as I don't have any control over the data that has been input into the database then I would have to loop through every character of every field I retrieved. It would be easier to wrap everything in CDATA, although I'm hoping there is a more sophisticated answer to the problem than that. Owen. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |