7 ms·
If this is such a serious problem, please demonstrate at least one example in Google Books where a scan shows the wrong letter or number. That really can’t be
by joosters 4y ago
If this is such a serious problem, please demonstrate at least one example in Google Books where a scan shows the wrong letter or number.
That really can’t be hard to do, since there are lots of common books in GB, there are even OCRs available so you could even do the error checking automatically for thousands of books.
If you can’t show a single case of JBIG data corruption in GOogle Books, you have absolutely no justification in calling it such a serious problem!
- j16sdiz 4y agoIt is quite common on archive.org. Google know what they are doing and don't have these error.
- adhesive_wombat 4y agoGoogle Book has atrocious scan quality in general, though (compared to, say, the Microsoft-sponsored archive.org ones). Some pages are completely unreadable and sometimes images are completely deleted as the compressor mistakes them for background.
- vlovich123 4y agoWouldn’t you need to have an original scan not compressed in JBIG? I’m not sure I understand the suggestion on how to find it in Google Books…
- kfichter 4y agoPresumably OCR on the Google Books scans then compare to some known text from a different source (Gutenberg or something)