We use it
[link|http://www.lizardtech.com/products/doc/|http://www.lizardtech.com/products/doc/]
We have to allow our customers to proof printed pages before they go on the full press run. Some customers will only do this in person. This means we have customers LIVING on site for a day or 2 since the press windows might get skewed by an occasional problem. Usually it is a matter of the customer not providing what we need, but then insisting we do not release the press for the next customer. Hell of a balancing act.
When people review our work, they use a magnifying glass.
Some customers do not insist that they review the material onsite, but we have to give them the absolute best electronic version we can.
So we run a few samples and scan then using a high resolution scanner. We are not talking home scanner here.
So this might produce a file that is 400 MB per page. Really. These could be 2 Up 17" forms. And a single mail piece could be 8 forms.
And they might need to seee a dozen mail pieces since our dynamic logic might modify the output depending on the data, so we need an example for each.
So here we have a 4GB file that we have to sent to the customer ASAP over what could be T1 (on their size). Sounds like a 5 hours transfer. Zipped or bzip2 would go down to 2 hours. But then we have marketing directors dealing with VERY large files on the other end, dealing with decompression, etc? Bad idea.
Enter DjVu.
Incredible compression,
Embedded into a browser app.
Do we expect to view it years later?
No.
But it is great for this particular usage.
