I showed the pertinent XML/XSLT - I program for a corporation and its all propriety so I can't really share the data. There is nothing to guess about really - this line
<xsl:if test="$name1 = $name2">
produces that error. It doesn't matter what it's embedded in- that line produces that error, anywhere. Yes, XSL variables DO look like Perl variables. I didn't invent the xsl var syntax, so I don't know what you mean by that comment.
The question is really not about the particulars of the XSLT or XML. If there was a quote or any other syntax error, the browser wouldn't have rendered it. Unlike HTML, the XSL tags must be perfect, or the browser throws errors. As I said, the browser is very particular about things being pristine. No, the question is more about do I need to abandon XML::XSLT since I've apparently reached a practical limit of it's capability to support xsl 2.0. I'm planning to ask my Ruby coder down the hall if he has a Ruby method to render the HTML. I've never encountered something Perl wasn't up to doing, but it feels like this is the one....
| [reply] [d/l] |