On 11/14/06, Rashmi Rubdi [EMAIL PROTECTED] wrote:
May be if there are languages other than HTML that JSTL works with then, having
an unescaped ampersand
makes sense if those other languages require an unescaped ampersand. But I
don't know if there are other languages
at this point.
?! Uh,
- Original Message
From: Trenton D. Adams [EMAIL PROTECTED]
Just out of curiosity, is JSTL supposed to do encoding by default?
I don't know that.
The W3C specs for a link in both HTML and XHTML mention that the ampersand
should be escaped as in
a
Yup, that totally makes sense to me.
-Rashmi
- Original Message
From: Hassan Schroeder [EMAIL PROTECTED]
To: Tag Libraries Users List taglibs-user@jakarta.apache.org
Sent: Tuesday, November 14, 2006 8:42:14 AM
Subject: Re: JSTL 1.1.2 c:url problem?
On 11/14/06, Rashmi Rubdi [EMAIL
Yeah, I suppose that's a good reason not to have an escaped output.
Thanks for the info.
Hassan Schroeder wrote:
On 11/14/06, Rashmi Rubdi [EMAIL PROTECTED] wrote:
May be if there are languages other than HTML that JSTL works with
then, having an unescaped ampersand
makes sense if those
- Original Message
From: Mikolaj Rydzewski [EMAIL PROTECTED]
To: Tag Libraries Users List taglibs-user@jakarta.apache.org
Sent: Monday, November 13, 2006 2:59:21 AM
Subject: Re: JSTL 1.1.2 c:url problem?
Trenton D. Adams wrote:
Is c:url supposed to encode your ampersands?
Unfortunately
: JSTL 1.1.2 c:url problem?
Trenton D. Adams wrote:
Is c:url supposed to encode your ampersands?
Unfortunately not. I have raised such case a few weeks ago:
http://mail-archives.apache.org/mod_mbox/jakarta-taglibs-user/200609.mbox/[EMAIL
PROTECTED]
It's not a problem to build your own patched
Trenton D. Adams wrote:
Is c:url supposed to encode your ampersands?
Unfortunately not. I have raised such case a few weeks ago:
http://mail-archives.apache.org/mod_mbox/jakarta-taglibs-user/200609.mbox/[EMAIL
PROTECTED]
It's not a problem to build your own patched jstl version.
--
Mikolaj
