as easy as an xslt stylesheet

How many time have I read that sentence! It is also as easy as writing a piece of assembly code.

Did you have a look at the XML you get for a node? It is precisely the kind of XML that's very hard to process with XSLT. So please, if you are going to advocate using XSLT here, show us the (tested) code.

Now if you had said "as easy as writing xml_grep --text_only --cond 'field[@name="doctext"]' node.xml | perl -n -e'if( m{<code>}..m{<//code>}) { s{</?code>}{}g; print; }'", then that would have been OK (extra / added in <//code> to avoid confusing PM's code) . Apart from the fact that it looks like the XML for the homenode I tested it on (tye's) is invalid.

In reply to Re: Re: Re: Re: downloading code from home nodes by mirod
in thread downloading code from home nodes by calin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.