RE: Antwort: RE: [xsl] Ampersand for URLs

[Robert Seber <robert.seber@xxxxxxxxxxxxxxxxxx>]

The browser replaces all character entities (e.g. &,  ) with their
equivalent characters when the page is rendered.  So if a browser receives
& in the HTML source  it will be converted to & by the browser.  As
Julian says, typing it directly into the navbar is not a valid test as the
browser doesn't have a chance to process this data.


> -----Original Message-----
> From: Julian F. Reschke [mailto:julian.reschke@xxxxxx]
> Sent: Friday, April 20, 2001 10:55 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE: Antwort: RE: [xsl] Ampersand for URLs
> 
> 
> Wrong.
> 
> The HTML method of XSLT emits exactly what HTML 4 requires.
> 
> Besides, I think Netscape *does* treat it correctly. Trying 
> to enter the URL
> in the navigation bar is NOT a valid test.
> 
> Julian
> 
> 
> > -----Original Message-----
> > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of
> > P.Vogt@xxxxxxxxxxxx
> > Sent: Friday, April 20, 2001 11:41 AM
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: Antwort: RE: [xsl] Ampersand for URLs
> >
> >
> > That's exactly what I'm afraid of. So I want a clean "&" to 
> separate the
> > cgi-parameters and not the &
> > What I don't get is, that this is a problem... I thougt 
> that it shouldn't
> > be a problem because this is the last step in processing. I 
> don't want to
> > process the resulting code. It looks like the processor or xslt is a
> > little bit to strict.
> >
> >   Philipp
> >
> > --
> > Philipp Vogt
> > Web-Entwickler/Programmierer/Member of visionLab
> > mainwork information technology AG
> > Höchstädtplatz 3 / 202, 1200 Wien
> > E-Mail: p.vogt@xxxxxxxxxxxx
> > Tel: +43 1 796 70 60
> > Fax: +43 1 796 70 60 - 60
> > Mobil: +43 699 1 946 95 24
> >
> >
> >
> >
> > "Daniel Newman" <daniel.newman@xxxxxxxxxxx>
> > Gesendet von: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > 20.04.2001 11:16
> > Bitte antworten an xsl-list
> >
> >
> >         An:     <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
> >         Kopie:
> >         Thema:  RE: [xsl] Ampersand for URLs
> >
> > Netscape does NOT like &amp; in the href, it results in a 
> 401 error. Bit
> > of
> > a pain, but there you go.
> >
> >
> > -----Original Message-----
> > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of 
> Robert Seber
> > Sent: 20 April 2001 10:01
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: RE: [xsl] Ampersand for URLs
> >
> >
> > In my experience all browsers will understand both & and 
> &amp; in hrefs.
> > In
> > fact, using &amp; is safer as IE4 sometimes sees &something 
> in a URL as a
> > character entity and translates it, causing all sorts of problems.
> >
> >
> > > -----Original Message-----
> > > From: P.Vogt@xxxxxxxxxxxx [mailto:P.Vogt@xxxxxxxxxxxx]
> > > Sent: Friday, April 20, 2001 9:36 AM
> > > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > > Subject: [xsl] Ampersand for URLs
> > >
> > >
> > > Hello!
> > >
> > >   Perhaps someone on this list can help me with a little problem:
> > >
> > > I want to transform an xsl to html which contains a url. This
> > > url has an
> > > ampersand, which seperate cgi-parameters. My problem is, that
> > > the xalan
> > > processor translates the & in &amp; (which should be ok
> > > refering to the
> > > xslt-reference and the faq).
> > >
> > > Example:
> > >
> > > Xsl:
> > > <img><xsl:attribute
> > > name="src">http://www.thehost.com/thescript?param=<xsl:value-of
> > > select="number"/><![CDATA[&]]>img=5</xsl:attribute></img>
> > >
> > > results in
> > >
> > > HTML:
> > >
> > > <img
> > > 
> src="http://www.thehost.com/thescript?param=15&amp;anotherparam=5";>
> > >
> > > But I need:
> > >
> > > <img 
> src="http://www.thehost.com/thescript?param=15&anotherparam=5";>
> > >
> > > Is there a workaround to get this url?
> > >
> > > I use:
> > >
> > > <xsl:stylesheet version="1.0"
> > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
> > >   <xsl:output doctype-public="-//W3C/DTD HTML 4.0 
> Transitional//EN"
> > > doctype-system="http://www.w3c.org/TR/REC-html40/loose.dtd";
> > > method="html"
> > > version="1.0" indent="yes" encoding="ISO-8859-1"
> > > media-type="text/html"/>
> > >
> > > in the XSL, if that is of any help.
> > >
> > >   Philipp
> > >
> > > --
> > > Philipp Vogt
> > > Web-Entwickler/Programmierer/Member of visionLab
> > > mainwork information technology AG
> > > Höchstädtplatz 3 / 202, 1200 Wien
> > > E-Mail: p.vogt@xxxxxxxxxxxx
> > > Tel: +43 1 796 70 60
> > > Fax: +43 1 796 70 60 - 60
> > > Mobil: +43 699 1 946 95 24
> > >
> > >  XSL-List info and archive:  
http://www.mulberrytech.com/xsl/xsl-list
> >
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list