Re: XSLT/XPATH problem, possible bug

Michael Hansen wrote:
>>I will try to run some tests here locally to see whether Mozilla might
>>be failing to unescape the & in the query string of the href of
>>the processing instruction.
> 
> 
> That is exactly the problem. For now I have a solution with base64 encoded 
> transfer of the argument set, but since W3C recommends encoding the 
> ampersands in urls, this should be considered as a bug (and a grave one?), 
> or what?

My reading of <http://www.w3.org/TR/REC-xml/#dt-chardata> is that you do 
not need to escape the ampersand '&' in a processing instruction:

"The ampersand character (&) and the left angle bracket (<) MUST NOT 
appear in their literal form, _except_ when used as markup delimiters, 
or within a comment, a processing instruction, or a CDATA section."

So you would simply need to write your xml-stylesheet processing 
instruction with unescaped ampersands (e.g.
   &filter=Rock
) and all is fine, Mozilla will then make the proper URL request and 
your PHP script will have the proper $_GET variables.

That is what the XML specification gives.



-- 

	Martin Honnen
	http://JavaScript.FAQTs.com/