I didn't see the original post, but SQL2000 automatically escapes those
characters to " ' and so on.  So this guy shouldn't be having
to write post-processors (unless he thinks he wants to convert the
" *back* to a double-quote in the XML, which is illegal).


> -----Original Message-----
> From: Mike Brown [mailto:mike@xxxxxxxx]
> Sent: Friday, March 22, 2002 2:36 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  invalid xml characters
> 
> stevenson wrote:
> > How can characters like double quote ("") be automatically escaped,
as
> my
> > data is coming from the database (SQL Server 2000) and it's users
who
> input
> > data in the database from the form in my intranet (front end)
> 
> You don't say what this has to do with XSLT (the topic of this list).
> 
> If you're just asking this question in general, then my advice is to
try
> to
> ensure that the data goes into the database unescaped, then when
pulling
> it
> out to put into XML, use your own external process (script or
function) to
> escape "&" and "<", and quotes that are destined to be in attribute
values
> delimited by the same kind of quotes.
> 
>    - 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


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list