RE: [xsl] Converting &, >, <, ", and other odd-ball characters...

Subject: RE: [xsl] Converting &, >, <, ", and other odd-ball characters...
From: "Kevin Duffey" <kevin.duffey@xxxxxxxx>
Date: Thu, 15 Feb 2001 21:24:46 -0800
Interesting dilema. For the most part, we are a b2b site that deals with
specific clients. Very unlikely this will occur, as far as the non-ascii
characters. I guess you could just "omit" them? I am not sure how it would
be handled. How do you make a web-based solution work with these characters?


> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Mike Brown
> Sent: Thursday, February 15, 2001 10:13 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] Converting &, >, <, ", and other odd-ball
> characters...
> Kevin Duffey wrote:
> > Oh yeah..not sure if you know this or not, but a "performance" tip..
> Yes, I knew there were better ways to do it, and I've done those things
> before; I didn't have access to that code though and I just wanted to get
> across the general idea, and JSP declarations, in case it was going to be
> helpful.
> > Lastly, can you think of any other characters that are a
> problem when used
> > in input boxes, text areas, or drop-downs that need to be converted?
> " -> &quot; only needs to happen when you're putting the string into an
> attribute value that is delimited by double quotes. Same for ' -> &apos;
> when using apostrophes.
> Escaping these characters is only half of your worries. The other half is
> that you cannot be guaranteed of the encoding of the form data that
> arrives in the HTTP request. When people enter non-ASCII characters,
> your JSP engine has maybe an 80% chance of decoding them properly.
>    - Mike
> ____________________________________________________________________
> Mike J. Brown, software engineer at            My XML/XSL resources:
> in Denver, Colorado, USA    
>  XSL-List info and archive:

 XSL-List info and archive:

Current Thread