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

[download]

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

[download]

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.

In reply to Re: Perldocs extensions by ferreira
in thread Perldocs extensions by 20GT02

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.