Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 38376 invoked from network); 14 Feb 2007 20:12:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2007 20:12:48 -0000 Received: (qmail 11343 invoked by uid 500); 14 Feb 2007 20:12:42 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 11321 invoked by uid 500); 14 Feb 2007 20:12:42 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 11310 invoked by uid 99); 14 Feb 2007 20:12:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Feb 2007 12:12:42 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of rosenberg.leon@googlemail.com designates 64.233.182.187 as permitted sender) Received: from [64.233.182.187] (HELO nf-out-0910.google.com) (64.233.182.187) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Feb 2007 12:12:32 -0800 Received: by nf-out-0910.google.com with SMTP id d4so854475nfe for ; Wed, 14 Feb 2007 12:12:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TibnRKWxKwO6YFRGJfkc97UuAsdvmfQwgpDQ+xqD1IBiGL3Roumgjk8BaEYI2fUl96sqa2xLS6slUqbyVjP1jw+2VnaBxhjo9LJcGQ025m1hfjWktopODaoiMB23x5ntWczWXdgLthBWgvUnCNVxu/MpWP0RLiUN2OfJQrRFSug= Received: by 10.82.135.13 with SMTP id i13mr1453024bud.1171483930041; Wed, 14 Feb 2007 12:12:10 -0800 (PST) Received: by 10.82.136.1 with HTTP; Wed, 14 Feb 2007 12:12:10 -0800 (PST) Message-ID: <327858f40702141212h7f744cadwb785b220bec1165e@mail.gmail.com> Date: Wed, 14 Feb 2007 21:12:10 +0100 From: "Leon Rosenberg" To: "Tomcat Users List" Subject: Re: ampersand (&) handling in jspx - any workaround? In-Reply-To: <45D36BCD.2020504@christopherschultz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45D328F3.4020800@telig.de> <327858f40702140924l5fa7a4f5ue39625389da4eb68@mail.gmail.com> <45D35C08.6070201@cornell.edu> <45D360CE.60106@christopherschultz.net> <327858f40702141146i5bfd5925t613f44cef63f38a5@mail.gmail.com> <45D36BCD.2020504@christopherschultz.net> X-Virus-Checked: Checked by ClamAV on apache.org On 2/14/07, Christopher Schultz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Leon, > > Leon Rosenberg wrote: > > On 2/14/07, Christopher Schultz wrote: > >> If the &'s were preserved, then how would you actually emit an '&' > >> character? > > > > &#uuuu; > > the & is not xml its html. > > It's both, actually. > > > Btw, & isn't allowed in html as well, for example in links. > > Untrue. HTML allows bare & symbols. XHTML forbids them (for example, in > links). Normal html forbids them too. at least according to http://validator.w3.org/ regards Leon > > - -chris > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFF02vN9CaO5/Lv0PARAoCyAJ4gFNM4TLbChuHdVS9S862psxzuGgCdEwsD > 33/7qrnPaIB5GW69cylsuS8= > =+GDv > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org