HTML output method and & in URLs

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

HTML output method and & in URLs

HTML output method and & in URLs

2003-01-28 - By Voytenko, Dimitry

Reply: 1 2 3 4 5 6 7 8

Hi Angus,

Where exactly is this happening? In the attributes HREF/SRC? If so, this
behaviour is correct. Otherwise, links won't work in the browsers. There's
no other way to disable escaping in attributes (&, <, etc). This behaviour
is defined in the xslt specification.

If this is happening in the elements SCRIPT or STYLE this is also correct.

I'm not quite sure how exactly you were trying to validate your HTML
document. HTML is not an XML, but SGML. Thus, you can't validate it against
XML rules. There're a lot of differences comparing to XML. For instance,
<IMG> and <BR> tags are never closed. Attributes "selected", "nowrap", etc
can be output w/o value.
You can find the rest in the
http://www.w3.org/TR/xslt#section-HTML-Output-Method

Thanks,
Dimitry

-----Original Message-----
From: Angus McIntyre [mailto:angus@(protected)]
Sent: Tuesday, January 28, 2003 11:20
To: xalan-j-users@(protected)
Subject: HTML output method and & in URLs

I have a stylesheet processor based on Xalan and Ant which I'm using
to generate HTML pages from XML. Within my pages, I have some URL
strings containing arguments, separated by '&'. In the input
document, the form is:

arg1=foo&arg2=bar&arg3=baz

The final HTML output contains the string

arg1=foo&arg2=bar&arg3=baz

which fails validation as HTML, because it uses '&' rather than '&'.

My stylesheet defines the output method as:

<xsl:output method="html"
doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN"

doctype-system="http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"
xalan:omit-meta-tag="yes"/>

If I change the method to 'xml', the '&' entities are not
converted, so it's presumably the HTML conversion process that is
doing this. Setting:

xalan:use-url-escaping="no"

doesn't seem to fix the problem.

Is there any way around this, or am I going to have to hack my
processor to reencode the '&' characters as entities?

Thanks

Angus
--
angus@(protected) http://pobox.com/~angus

_____________________________________________________
Sector Data, LLC, is not affiliated with Sector, Inc., or SIAC