2009/1/20 Bart C. Wise <bntgcont...@wiseguysweb.com>:
> I talked to the publisher again and he said that he would send me the exact
> error message, but I have not received it yet. But he did say that his
> printing shop wants the ability to download just the header information from a
> pdf rather than the whole pdf file which may be up to 80 mbytes. From that
> header information they will have the ability to render individual pages
> rather than the whole document. For example, they could request page 264 and
> render that single page as a jpeg.
This sounds like "web optimized" PDFs, those contain a second object
index at the start ("normal" PDFs have it at the end), so a *browser*
can request selected pages from the *webserver* without loading the
whole document.
It's meant as a web technology, and I never heard of anyone using it
in a print workflow. But it's not impossible.
Tha has *nothing* to do with tagged PDF!
"Tagged" is a technology to enable re-flowing text contents to e.g.
small devices or extracting of content for alternative readers, e.g.
screenreaders.
PDFs for print should *not* be tagged in this way, for it can confuse
a print workflow.
Printshops should adhere to printing standards like PDF/X-1a and
PDF/X-3 - and these never need web optimization or tagging!
Greetlings, Hraban
(printing engineer and PDF workflow techie)
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
