Thread: Bug report
View Single Post
Old 01-18-2011, 05:44 AM   #137
teofrast
Enthusiast
teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.teofrast once ate a cherry pie in a record 7 seconds.
 
Posts: 34
Karma: 1593
Join Date: Jan 2011
Device: pocketbook902
thank you review,
you've been very clear. I'll decide what to do when the problem will arise book by book (I've also many manuscripts - not from archive - and quite ancient prints, and I doubt OCR had been used, unless an enormous amount of hand edit had been made). it could be that your script is to become very handy, anyway the only correct solution is pocketbook to fix things in firmware OR release as soon as possible SDK's, so users can do it by themselves.
one of the things that made me go for pocketbook, other than pdf and djvu capability, is the open and constructive policy of the company with users and open source community. I hope they won't deceive us now.
teofrast is offline   Reply With Quote