This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Document() and &
- From: "Charles Knell" <cknell at onebox dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Fri, 17 May 2002 11:25:07 -0700
- Subject: RE: [xsl] Document() and &
- Reply-to: xsl-list at lists dot mulberrytech dot com
I hope you don't mind if I jump in on this thread, because I am struggling
with the same issue, yet the approach of substituting the HTML entity
& for the literal & is going nowhere.
Below are two examples of a fragment of an HTML element produced by passing
in a quoted string as a parameter. The goals is to pass a URL as a parameter
to the XSLT and get a valid URL in the output HTML document. In the first
one, I used '&' in the original string, in the second, I used '&'
As you can see, there is no difference between them. So what part about
the entity substitution approach am I missing?
<script language="JavaScript" src="http://my.eis.army.mil/pls/portal30/eis_CLOB.include_JScript?p_tableName=tbl_javascripts_2&p_docName=oQRpt5
<script language="JavaScript" src="http://my.eis.army.mil/pls/portal30/eis_CLOB.include_JScript?p_tableName=tbl_javascripts_2&p_docName=oQRpt5
--
Charles Knell
cknell@onebox.com - email
---- "Stuart Celarier" <stuart@ferncrk.com> wrote:
> >> That string does not look like well-formed XML to me,
>
> > It's part of a well formed document, so must have < and & quoted.
>
> Ah, it must be valid XML character data
> (http://www.w3.org/TR/2000/REC-xml-20001006#syntax), not well-formed
> XML. I'll buy that.
>
> My big toe is part of me, but it bothers me when people constantly
> think
> that my big toe is in fact me. Sm;)ey.
>
> Cheers,
> Stuart
>
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list