From: Nam Quang Tran on
It seems I was able to fix the problem with the PDF indexing discussed
in this thread, thanks to a problematic PDF file Mike sent me.
So it's very likely that there will be a new release of DocFetcher
next week (DocFetcher 1.0.2).
From: Craig on
On 01/15/2010 03:22 PM, Nam Quang Tran wrote:
> It seems I was able to fix the problem with the PDF indexing discussed
> in this thread, thanks to a problematic PDF file Mike sent me.
> So it's very likely that there will be a new release of DocFetcher
> next week (DocFetcher 1.0.2).

good to hear. thx.

--
-Craig
From: mike on
Nam Quang Tran wrote:
> It seems I was able to fix the problem with the PDF indexing discussed
> in this thread, thanks to a problematic PDF file Mike sent me.
> So it's very likely that there will be a new release of DocFetcher
> next week (DocFetcher 1.0.2).

Excellent.
Thanks,
mike
From: Howldog on
On Fri, 15 Jan 2010 12:15:52 -0800 (PST), Nam Quang Tran wrote:

>> I remember you, you were the one who took orders from that Italian slob
>> Saladini. Did you trick the Jewtalians into forking over their dough to
>> Ho Ho Ho Chi Minh?
>
> Huh? I seriously don't know what you're talking about. If this is a
> joke then I didn't get it.

Do you deny doing work for that fraud Saladino? Do I need to post a
link?
From: Spamblk on
Nam Quang Tran <qforce.bak(a)googlemail.com> wrote in
news:f7babbac-4350-4005-bfbe-336d2bd34b2a(a)o28g2000yqh.googlegroups.com:

> By the way, there's an easy way to find out if the "can't extract
> text" flag in a PDF file is set: If you can't copy text from the PDF
> file to the clipboard using a standard PDF reader such as Adobe or
> Foxit Reader, then this flag is probably set.
<snip...>

I also have a copy of pdftotext, version 3.01 which can be used to scan PDF
files for the text component. It won't work (unless the owner password is
included on the command line) for PDF files with extraction and copying
permissions disabled so is a good way of finding these files.