Subject: [xsl] why not match text()? (fork from "Novice Question - matching entire text children") From: Syd Bauman <Syd_Bauman@xxxxxxxxx> Date: Mon, 20 Dec 2010 18:05:33 -0500 |
Wendell is absolutely correct, a lot of learning goes on 'round here just "watching over each other's shoulders", which I don't get to do as much as I'd like. 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] Novice Question - matchin, David Lee | Thread | Re: [xsl] why not match text()? (fo, David Carlisle |
RE: [xsl] Novice Question - matchin, David Lee | Date | Re: [xsl] why not match text()? (fo, David Carlisle |
Month |