[AuckLUG] OCR software

[Justin Cook]

"Tesseract" has recently been released by Google. It's not as good as 
the commercial options, but it's far better than the other free ones.

It can't handle multi-column text yet though, so it might not work for 
magazines.

*Justin Cook*
Developer
http://www.skull.co.nz/

	

*Skype*
justincookskull <skype:justincookskull?call> 	My status 
<skype:justincookskull?call>



John Deverall wrote:
> Hi everyone, 
>
> I've got a bunch of magazines I want to load onto a website. 
>
> http://www.autc.org.nz
>
> The magazines are autc club journals dating back to the 1940's, one journal
> for each year. 
>
> Does anyone know of a good way to go about this? 
>
> Preferably I'd like character recognition and output to html as it would be
> nice to be able to search the contents of the magazines over the years using
> the website search feature. 
>
> Any ideas? 
>
>
> -----Original Message-----
> From: aucklug-bounces at linux.net.nz [mailto:aucklug-bounces at linux.net.nz] On
> Behalf Of Daniel Pittman
> Sent: Monday, 18 September 2006 6:24 p.m.
> To: Auckland Linux User Group mailing list
> Subject: Re: [AuckLUG] Restricting E-mail access for Children
>
> "Chris Hodgetts" <chris at archnetnz.com> writes:
>
>   
>> I was wondering what the best way to restrict e-mail is.  Basically I
>> want to create a White list that allows mail to and from a set group
>> of people.
>>     
>
> Since you use postfix, use 'check_recipient_access' in the
> smtpd_recipient_restrictions section of main.cf, which will allow you to
> create your whitelist and then block everything else.
>
> That is a global setting, though, not per-user.
>
>   
>> Inbound I can do with Procmail but I am not sure how to restrict
>> outbound addresses, and ideally I would like to just maintain one
>> white list.
>>
>> I only want to do this for ONE account on the server, SMTP is using
>> SMTP Auth so there might be something there that I can utilise.
>>     
>
> For that, though, you probably need a hand-written policy daemon to
> identify both the sender and recipient, and act on that.  The version of
> Postfix you have supports that, and writing a policy daemon isn't /that/
> hard.
>
> See the simple greylist example that Postfix ships, or that is on their
> website, for the Perl code.
>
>
> Blocking outbound mail from that one account is a much harder job than
> blocking inbound, though, as you note.  Most threat models with email
> assume that internal senders are at least semi-trusted.
>
>
> Perhaps if you outline why you want to do this there is a better way to
> achieve your goals overall?
>
> Regards,
>         Daniel
>