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]
Other format: [Raw text]

Re: searching and replacing


normbishop1@netscape.net wrote:
> I don't have <sub> as a node in the document.  What I have is & lt; sup & 
> gt; (separated with a space to avoid the email system to convert it to 
> <sub>). 

OK. There's no better way, except to redesign your XML so that you don't have 
pseudo-markup embedded in the text content. There's an equally kludgy and 
slightly less reliable way, using disable-output-escaping, but I won't go into 
that.

Either way, you're trying to do something that XSLT isn't really designed to
handle. You are trying to parse the text in a text node as if its
pseudo-markup substrings were in fact markup. You basically want to
re-implement an XML parser using XSLT. I would look into shifting the burden 
of dealing with this to whoever is feeding you the XML. Make them give you 
something that you can work with more easily.

   - Mike
____________________________________________________________________________
  mike j. brown                   |  xml/xslt: http://skew.org/xml/
  denver/boulder, colorado, usa   |  resume: http://skew.org/~mike/resume/

 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]