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,

>> Are you sure about this? I've just tested a URL string containing
I definetely was wrong. Specification states only that '<' character is not
encoded and '&' in case of '&{'.
I just think Xalan always worked like this, so I took it as a granted.

Sorry for the confusion.
This is definietely a XalanJ bug. I'm not sure if it's been reported. Can
you take a look in the bugzila and report it, if it's not there?

Thanks,
Dimitry

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

At 11:38 -0800 28.01.2003, Voytenko, Dimitry wrote:
>Where exactly is this happening? In the attributes HREF/SRC? If so, this
>behaviour is correct. Otherwise, links won't work in the browsers.

Are you sure about this? I've just tested a URL string containing
'&' against a handful of browsers - Explorer 5, iCab 2.9, Chimera
0.8, Netscape 7 - and they all seem to take it in their stride.
Although I think you may be right that older browsers will choke on
it.

>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.

Yes, I know that HTML validation is not the same thing as XML.

I'm going by the validation tool at <http://validator.w3.org/>, which
flags as incorrect documents in which I use the:

arg1=foo&arg2=bar

version, and passes as correct documents in which I use:

arg1=foo&arg2=bar

relative to the HTML 4.0.1 Transitional doctype. The error messages
are accompanied by an explanation:

http://validator.w3.org/docs/errors.html#bad-entity

and the recommendation to use '&' in URLs.

I believe that I've found a hacky solution, which is to write:

arg1=foo&amp;arg2=bar

in my input XML documents. Xalan munges the first '&' into '&',
and I get the right output. This may come back to bite me at some
stage in the future, but for the moment it seems to resolve the
problem.

Thanks to everyone who answered.

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

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