Some flamage (start of message) and one advice (end of the
This is my anecdotical, highly opinionated take on XSLT:
ME : "Looks we have to adjust this another bit..."
Coworker: "Do you think we can get this to work before XML falls out of fashion?"
Basically, it looks like every time I fish out my XSLT, the task at hand is either:
- Nothing a good CSS could not handle
- Nothing I would not rather do with a glue language directly from the DOM.
And my question would be, why do we need a highly idiosyncrasiac, verbose, devious programming language for transformations? How is it superior to direct interaction
with the DOM?
Besides it appears to have a slew of limitations - just by looking at the mailing list, it appears that every tiny departure from the text book examples require some extension (Saxon is often mentioned).
So I have long ceased to try to wrestle with XSLT. When CSS is not up to snuff I usually do (on Win32):
#...do my stuff
On linux, you can get something similar from either the perl
XML modules OR the Xerces-C module.
AxKit has a thing that is called (I think) XpathScript, which does much what XSLT promises to do, but with much saner syntax and looks (IMHO). I have never used it, but it would probably be my choice after going straight to the DOM.
You can't have everything: where would you put it?
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.