Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Will Senn <>
To: Bakul Shah <>
Cc: coff <>
Subject: [COFF] Re: converting lousy scans of pdfs into something more useable
Date: Fri, 3 Feb 2023 10:25:50 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

On 2/3/23 10:01 AM, Bakul Shah wrote:
> It's a python script that runs most any unix and uses
> tesseract. Its author's motivation seems similar to yours:
> I searched the web for a free command line tool to OCR PDF files: I found many, but none of them were really satisfying:
>      • Either they produced PDF files with misplaced text under the image (making copy/paste impossible)
>      • Or they did not handle accents and multilingual characters
>      • Or they changed the resolution of the embedded images
>      • Or they generated ridiculously large PDF files
>      • Or they crashed when trying to OCR
>      • Or they did not produce valid PDF files
>      • On top of that none of them produced PDF/A files (format dedicated for long time storage)
> I decided to develop my own tool.

Nice. Off to checking out OCRmyPDF!

> I rarely print PDFs any more.

I can't seem to get away from having to highlight and mark up the stuff 
I read. I love pdf's searchability of words, but not for quickly 
locating a section, or just browsing and studying them. I can flip pages 
much faster with paper than an ebook it seems :).


[-- Attachment #2: Type: text/html, Size: 1916 bytes --]

  reply	other threads:[~2023-02-03 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 15:27 [COFF] " Will Senn
2023-02-03 16:00 ` [COFF] " Dennis Boone
2023-02-03 16:01 ` Bakul Shah
2023-02-03 16:25   ` Will Senn [this message]
2023-02-04  7:59 ` Ralph Corderoy
     [not found] <>
2023-02-03 16:21 ` [COFF] Re: converting lousy scans of pdfs into something more, useable Will Senn
2023-02-03 17:09 [COFF] Re: converting lousy scans of pdfs into something more useable Bakul Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).