It sounds like a fairly big task in itself.. I thought a bit about it and perhaps you could try one of the following approaches...

Firstly, if you need full text searching, its probably wise to build indexes first... searching all the PDF files on your server is going to take far too long, and you could run into scalability and concurrency issues..

So the solution would probably be to periodically convert the textual content of the PDF files into a text file, and index that text file... Text indexing is pretty well understood, and its fast, moreover, so this would probably be the most efficient method.. Just provide a link to the real PDF file in your search results

Another thing you could try is to convert the PDF to HTML (see the links below).. Have a converter program product HTML output, and then run an indexing tool like ht://Dig or something on the HTML output.. Then, your users can read the output in HTML, and if desired download the PDF format document.

These are some links I found that might make your life easier, mostly to do with PDF conversion from one form or another, but there are some links on how to convert PDF to other formats as well...
PDF tools
Perl modules for PDF conversion
HTH


In reply to Re: Full Text Search by tinman
in thread Full Text Search by skullbowl

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.