I'm trying to match any element node, whose child text node contains a carriage return or line feed. I have something that's working, but it seems inelegant to me. Maybe I'm just being picky, but is there any improvement I could make to this? I'm using saxon 8.9 (2.0 transformation). I've looked into using "matches()" but I cannot get a regular expression to work properly. Mostly, because I'm not very good at regex :)

Suggestions? Improvements?

I would probably write
but I don't think that is more elegant than yours.

__________________
Martin Honnen
Microsoft MVP (XML, Data Platform Development) 2005/04 - 2013/03
My blog

A text node is very unlikely to contain a CR, because unless it's written as a numeric character reference, the XML parser will turn it into a NL.

And testing whether the string-value of the element contains a newline is equivalent to testing whether it has a text node that contains a newline. So I think it's just

Saxon 8.9 is getting very old, by the way: time you upgraded.

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference

I ran into some problems with just doing "contains()" directly on the element node. Unless the document was using "<xsl:strip-space elements="*" />" it was matching on pretty much the entire document.

You're telling me! We run into bugs every once and a while linked back to 8.9. Unfortunately, we're tied to and Enterprise Service Bus product (Sonic) that has the version of Saxon built in statically. We've tried to just upgrade the saxon processor portion of the ESB product, but that blows up. We also have upgraded sonic a couple times, but that still haven't adopted 9+ version of saxon.

To be honest, I'm just happy to be able to use XSLT 2.0 compared to 1.0. I'll deal with the older version for now.

Thanks for your suggestions, much appreciated.