There are more in the fourth column.
https://github.com/mozilla/mozjpeg/issues/139
I said in another comment that we'd release 3.0 tomorrow, we'll probably hold up the release to investigate this.
They already fixed the bug. I'm impressed.
@joshmoz Hopefully, you can re-run the image and share it with us in case we can find something else. :D
http://i.imgur.com/2wAcBdL.png (23.43 KB)
For nicer looking images, scan as grayscale and then use Photoshop's Image -> Adjustments -> Curves to turn everything almost-white to white and everything almost-black to black:
http://i.imgur.com/ktj8WkE.png
Alternatively, do a high-DPI 1bit scan, convert the document to 8bit, and then scale it down.
E.g. when you go from 1600 DPI to 100 DPI, you have 16x16 1bit pixels per 8bit pixel. The result will look smooth and crispy.
The fact that a single difference in a configuration bit (lossy/non-lossy) can introduce subtle and easy-to-miss errors (to the point that this went unnoticed by Xerox QA and thousands of their customers!) is an indication to me that while JBIG2 might be superior in terms of the compression it offers, it's not a solution I would use without very serious consideration and deliberation.
Just to make this more clear: if you borked the compression setting on jpeg, you get smeared images. If you bork the lossy/nonlossy flag on JBIG2, you get images that look great but may have a random letter or digit swapped for another.
[0] http://www.theregister.co.uk/2013/08/06/xerox_copier_flaw_me...
Original - 327kb - http://i.imgur.com/DTxTcLp.jpg
MozJPEG - 127kb - http://i.imgur.com/jVESWGS.jpg
Stared at both side by side and really struggled to tell the difference. Great job!
Sorry WebP is great but I just don't see it getting adapted unless all browsers get on board as well as big software. JPEG is practically a household name, photographers, artists, insta-grammers,all know what it is and short of a mild revolution I just don't see it.