What exactly do you have in mind? To convert the POD documentation of the modules installed at your machine into plain text, you just need perldoc. For example, converting the DBI docs into a text format:
$ perldoc -t DBI > DBI.txt
You may use pod2text as well, but in this case you have to find the full path of the file.
$ perldoc -l DBI
/usr/local/lib/perl/5.8.8/DBI.pm
$ pod2text /usr/local/lib/perl/5.8.8/DBI.pm > DBI.txt
Converting from PDF or something like that will probably be much poorer than the approach above that generates plain text from POD sources. If you want to convert many perldoc pages, writing a script to do that (as appropriate to your needs) should not be hard.
-
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.
|
