I'd definitely recommend one of the "mainstream" XML tools (for DOM/SAX/XSLT) over another Perl module, even if this involves a Horrible Hack to switch from the Perl environment to the Java world (a "used coffee filter", or whatever they call it) that the DOM was originally coded for. Personally I'm writing XML/XSLT code for M$oft; IE5 and ASP, so I choose to use the MXSML DOM via Win32::OLE even when I'm coding Perl.
DOMs aren't standardised; there's a lot of space around the W3C spec that is implementation dependent (especially with namespaces). Using something commonplace is good, and Xerces would be a good choice.
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
