Sergiu,
At 10:54 AM 10/1/2003, you wrote:
Does anybody nows why "e; is so hard to handle?
Because you have to get it past *both* the XML parser (which the escaping
of " into "e; will do) and the XPath expression parser.
E.g. <xsl:value-of select='translate(.,""e;","-")'/>
the XML parser resolves this to
translate(.,""","-")
which doesn't make much sense in XPath.
The usual workaround is to bind the problem character (or string) to a
variable, so you can evaluate the expression
translate(.,$quote,"-")
which isn't a problem.
Make more sense now? This double layer of indirection for "hot" characters
is part of the price we pay for the expression language wrapped in XML
syntax. If XPath had a completely different set of significant characters
(delimiters) from XML -- things would be confusing in a different way.
Cheers,
Wendell
Sergiu
> Abhishek Sanwal
> HP - Houston Campus
> abhishek(_dot_)sanwal(_at_)hp(_dot_)com
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list