News for hackers. Stuff that matters.

A comment on Xerox responds to the recent character substitution issue. Parent comment

Re:Xerox responds to the recent character substitution issue by gpvos on Tuesday August 06, 2013 @03:13PM (#6168565)
JBIG2 is not the problem. It is perfectly possible to do lossless compression with JBIG2. They just set its options to do some overly aggressive compression.
[ Parent | on HN ]
Re:Xerox responds to the recent character substitution issue by ToothlessJake on Tuesday August 06, 2013 @03:21PM (#6168593)
I would wager JBIG2 is the problem when Xerox couldn't implement it properly.

"Normal" is an overly aggressive compression setting? Is that an overly aggressive setting for the end-user or for Xerox to be implementing in their hardware marketed to law firms?

[ Parent | on HN ]