Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I found DocBook-X, a strange little combination of tools to emit PDF from DocBook source.

    What an utter piece of crap.

    This package is the worst of what open source is about. This is a 16MB download of poorly documented and highly buggy software. Thankfully, it's mostly shell scripts, but completely untested shell scripts (docbook-sh.cfg is a slightly warmed over csh shell script that doesn't work; multiple bugs in docbook2pdf took a while to spot before it led to a few hundred lines of Java exceptio

    • Agreed -- I also wasted time trying to get the broken sh script to work, only to be rewarded by the ubiquitous Java stack trace. I must admit that I've never seen the draw of Java + XML, though.

      • Java + XML quite simply doesn't fly. You can do it for sure, but it really wasn't made to handle XML's flexibility gracefully. To be honest, the worst part of going from a Perl job to a job in which I occasionally do some Java is the XML support. No good SAX writer, no good parsing framework (JAXP is pretty much a joke), no trace of a proper SAX pipelining framework, no viable XPath on streams, no variety in tree implementations. It's appalling.

        Only two languages have proper XML support, Perl and Python. The latter probably more unfortunately, but then it's hard to find good Perl hackers to work on XML modules. Any many of them will tell you they won't have anything to do with it because "it's a Java thing". Sigh. EORANT.

        --

        -- Robin Berjon [berjon.com]