Subject: Re: [xsl] why not match text()? (fork from "Novice Question - matching entire text children") From: "Imsieke, Gerrit, le-tex" <gerrit.imsieke@xxxxxxxxx> Date: Tue, 21 Dec 2010 00:30:08 +0100 |
Watching this conversation, I found myself interested in how many experts say there is rarely a need to match text nodes. I do that all the time. Some examples include:
* transforming straight quotes to curly quotes * conditionally changing "-" to en-dash or em-dash * convert PUA characters to<tei:g> elements * deal with soft hyphens * ditching the punctuation that follows a<list> * finding the character before a footnote
So I'm guessing either a) there's a better way for me to be doing these things, or b) those experts who spoke of the rare need for matching text() either don't deal with data like mine -- TEI, i.e., mostly mixed content --, or deal with so much more of it that my needs for matching text() are, in fact, pretty rare from their point of view
I'm hoping someone will post the better way if it's (a). :-)
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] why not match text()? (fo, Michael Kay | Thread | Re: [xsl] why not match text()? (fo, Wendell Piez |
Re: [xsl] why not match text()? (fo, David Carlisle | Date | Re: [xsl] Novice Question - matchin, Wendell Piez |
Month |