2 ms·
Sorry, this article is low on content and high on fearmongering. This issue was known years ago and the only example of it seems to be one implementation from X
by userbinator 4y ago
Sorry, this article is low on content and high on fearmongering. This issue was known years ago and the only example of it seems to be one implementation from Xerox, which was also set to lossy mode --- and I believe that was subsequently fixed too.
The other comments here have linked to the previous articles about this, which do give far more detailed information about the problem. JBIG2 in lossless mode won't do this.
- Brian_K_White 4y agoSaying "jbig2 in lossless mode won't do this" is as relevant as saying "png won't do this" The problem is the existence and use of a codec for a purpose, that harms that purpose. It doesn't matter what it's name is. Are scans being produced with this codec? And is it not true that not only is there data loss or corruption like with jpg, but that unlike jpg artifacts you can sometimes not know that the data loss or corruption occurred? That does make it not merely a problem of "I wish they scanned this in higher quality" but a far worse problem of "this document looks good so I trust it" when in fact it was corrupt.
- iforgotpassword 4y agoThe according talk is linked here in the comments - no, it wasn't just lossy mode. It was much harder, but in the end it was reproduced on other quality levels. But if it happened once, who's gonna guarantee this won't happen again? When it happens with numbers, worst case it can have fatal consequences.
- adhesive_wombat 4y agoIf you can't reconstruct the original bit-for-bit, for whatever reason, it must be lossy.