Return-Path: Delivered-To: apmail-xml-general-archive@www.apache.org Received: (qmail 30083 invoked from network); 24 Oct 2007 23:05:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Oct 2007 23:05:10 -0000 Received: (qmail 21098 invoked by uid 500); 24 Oct 2007 23:04:57 -0000 Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 21049 invoked by uid 500); 24 Oct 2007 23:04:57 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: general@xml.apache.org List-Id: Delivered-To: mailing list general@xml.apache.org Delivered-To: moderator for general@xml.apache.org Received: (qmail 84051 invoked by uid 99); 24 Oct 2007 16:18:01 -0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C81658.F4EA87F6" Subject: RE: [Announce] Escaping double quotation marks in XSL Date: Wed, 24 Oct 2007 12:14:28 -0400 Message-ID: <044F2EDDF4FCA24A965ECAA66CB9345C01427469@vdsexc02> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Announce] Escaping double quotation marks in XSL Thread-Index: AcgWV+5NCbqHNleqSCO2xCaya3dLEQAABqEg References:

From: "Timothy Jones" To: , "Brian Minchau" Cc: , , X-ESAFE-STATUS: Mail clean X-ESAFE-DETAILS: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C81658.F4EA87F6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Maybe you should explore something like this: =20

=20 This way, the transformer is at least aware of the tag you are trying to insert into the output. =20 =20 =20 tlj =20 ________________________________ From: keshlam@us.ibm.com [mailto:keshlam@us.ibm.com]=20 Sent: Wednesday, October 24, 2007 11:58 AM To: Brian Minchau Cc: general@xml.apache.org; tranceradi@hotmail.com; xalan-j-users@xml.apache.org Subject: Re: [Announce] Escaping double quotation marks in XSL > Assuming that you are only interested in stream serialization, have you > thought of doing the serialization yourself for particular elements? For > example, something like this: >=20 > > > > ]>> > I *REALLY* detest that idiom. I've seen many people hurt themselves by trying to hand-generate XML; I consider it a very bad practice. Unless you're forced to do it in order to work with a downstream tool which has not been implemented correctly, I would recommend finding another solution. Any other solution. ------_=_NextPart_001_01C81658.F4EA87F6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Maybe=20 you should explore something like this:

<xsl:element=20 name=3D'image'>

&n= bsp;=20 <xsl:for-each select=3D'@*'>

&= nbsp; =20 <xsl:attribute name=3D'qname(.)'><xsl:value-of select=3D'.'=20 /></xsl:attribute>

&n= bsp;=20 </xsl:for-each>

=20 </xsl:element>

This=20 way, the transformer is at least aware of the tag you are trying to inser= t into=20 the output.

tlj =20

From: keshlam@us.ibm.com=20 [mailto:keshlam@us.ibm.com]
Sent: Wednesday, October 24, 2007 = 11:58=20 AM
To: Brian Minchau
Cc: general@xml.apache.org;=20 tranceradi@hotmail.com; xalan-j-users@xml.apache.org
Subject: R= e:=20 [Announce] Escaping double quotation marks in XSL

> Assuming that you are only interested in stream serialization= , have=20 you > thought of doing the serialization yourself for particular el= ements?=20 For > example, something like this: > >  > <xsl:template=20 match=3D"image"> > <![CDATA[=20 <image]>><xsl:apply-templates select=3D"@*"/> <![CDATA[= =20 >]>> > </xsl:template>

I *REALLY* de= test=20 that idiom. I've seen many people hurt themselves by trying to hand-gener= ate=20 XML; I consider it a very bad practice. Unless you're forced to do it in = order=20 to work with a downstream tool which has not been implemented correctly, = I would=20 recommend finding another solution. Any other solution.

------_=_NextPart_001_01C81658.F4EA87F6--