As a side note in favor of an XSLT approach, the KDE project's documentation is stored in DocBook XML format, and transformed on-the-fly to HTML for (well understood) rendering. All in all, it's a pretty slick system. We're implementing something disturbingly similar over here, although it's based on Java and it's getting delivered via the web.
As far as an XSL-based transformation toolkit goes, check out XML::Sablotron, a Perl interface to the Sablotron XSLT processor -- combine that with AxKit in a mod_perl environment and you have opened up a new world. Whether or not you need to deliver the docs over HTTP, I've found XML::Sablotron to be pretty easy to use, even if in the end you're using C libraries.
perl -e 'print "How sweet does a rose smell? "; chomp ($n = <STDIN>);
+$rose = "smells sweet to degree $n"; *other_name = *rose; print "$oth
+er_name\n"'
-
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.
|