Re: XML::XSLT v 50_5 error with xsl variables

You're not showing any XML or XLST, so there's no way to help other than to guess.

My guess is that you're running into a quoting issue somewhere. $name looks quite like a perl variable, after all.

When your only tool is a hammer, all problems look like your thumb.

Comment on Re: XML::XSLT v 50_5 error with xsl variables

Replies are listed 'Best First'.
Re^2: XML::XSLT v 50_5 error with xsl variables by misterperl (Friar) on Feb 08, 2018 at 13:41 UTC
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">` [download] 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]

Replies are listed 'Best First'.

Re^2: XML::XSLT v 50_5 error with xsl variables
by misterperl (Friar) on Feb 08, 2018 at 13:41 UTC

<xsl:if test="$name1 = $name2">
[download]

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]