That is nice. ++
I encountered a similar problem when I wanted to load some Pod documentation onto a Kwiki site at work. However, since nobody else there used Pod I took another approach and wrote a parser as a subclass of Sean Burke's Pod::Simple.
The module is Pod::Simple::Wiki. It is still a work in progress but here is a simple pod2kwiki filter based on it.
#!/usr/bin/perl -w
use strict;
use Pod::Simple::Wiki;
my $parser = Pod::Simple::Wiki->new('kwiki');
if (defined $ARGV[0]) {
open IN, $ARGV[0] or die "Couldn't open $ARGV[0]: $!\n";
}
else {
*IN = *STDIN;
}
if (defined $ARGV[1]) {
open OUT, ">$ARGV[1]" or die "Couldn't open $ARGV[1]: $!\n";
}
else {
*OUT = *STDOUT;
}
$parser->output_fh(*OUT);
$parser->parse_file(*IN);
Pod to Kwiki isn't currently a one to one mapping. Kwiki doesn't yet support term lists and definition lists and it isn't possible to escape camel case words in inline code sections.
Here is an example of the the Parse::RecDescent docs converted from Pod to Kwiki to Html.
--
John.
If man is 5 then this is the very model of a man.
-
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.
|