Re: Frustrating with XSL-T 2.0 [wasRe: Re: Spam

Nothing about 2.0 frustrates me overly much. When I made that comment, I 
was thinking that the learning curve for the new version might frustrate 
some people. There's nothing particularly tough about it, but it's the 
nature of the software industry that most of us have to learn under tight 
deadlines. The other source of potential frustration that comes to mind is 
the differences between 1.0 (and 1.1) and 2.0. When something doesn't work 
quite like it used to, that can be frustrating. And the more subtle the 
difference, the more frustrating it can be.

For the most part, 2.0 has relieved my frustrations. for-each-group, 
analyze-string, tokenize(), min() and max(), upper-case() and 
lower-case(), and other instructions and functions have all saved me 
bunches of time and made for shorter files. Notice how these items embody 
grouping, regular expressions, and string manipulation. For me, those are 
the three big improvements of 2.0.

Jay Bryant
Bryant Communication Services
(presently consulting at Synergistic Solution Technologies)




Frans Englich <frans.englich@xxxxxxxxx> 
10/20/2005 12:55 PM
Please respond to
xsl-list@xxxxxxxxxxxxxxxxxxxxxx


To
xsl-list@xxxxxxxxxxxxxxxxxxxxxx
cc

Subject
 Frustrating with XSL-T 2.0 [wasRe:  Re: Spam: RE: String 
manipulation in XSLT]






On Thursday 20 October 2005 17:26, JBryant@xxxxxxxxx wrote:
[...]
> If there's any way you can move to XSLT 2.0, some of your frustration
> might go away (of course, you might be frustrated in new ways, too).

That comment woke my interest. What do people find frustrating with XSL-T 
2.0, 
as opposed to XSL-T 1.0?

(I'm not questioning that XSL-T 2.0 may be frustrating or not be 
"perfect", 
I'm just curious on people's experiences.)


Cheers,

                                 Frans