ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Bart C. Wise" <bntgcontext@wiseguysweb.com>
To: ntg-context@ntg.nl
Subject: Re: PDF Meta Tags
Date: Tue, 20 Jan 2009 07:30:28 -0700	[thread overview]
Message-ID: <200901200730.28547.bntgcontext@wiseguysweb.com> (raw)
In-Reply-To: <954f61110901200606q2568ac9am1eaa997a1d86982a@mail.gmail.com>

On Tue January 20 2009 7:06:58 am Henning Hraban Ramm wrote:
> 2009/1/20 Bart C. Wise <bntgcontext@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!

Excuse the ignorance, but does LuaTeX produce a PDF based on the PDF/X-1a and
PDF/X-3 standards?

Bart



___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2009-01-20 14:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20  5:06 Bart C. Wise
2009-01-20  5:53 ` Bart C. Wise
2009-01-20  8:12   ` luigi scarso
2009-01-20  8:30 ` Martin Schröder
2009-01-20  8:37   ` luigi scarso
2009-01-20 11:10   ` Arthur Reutenauer
2009-01-20 11:33     ` luigi scarso
2009-01-20 13:51       ` Bart C. Wise
2009-01-20 13:59         ` luigi scarso
2009-01-20 14:02         ` Martin Schröder
2009-01-20 14:06         ` Henning Hraban Ramm
2009-01-20 14:30           ` Bart C. Wise [this message]
2009-01-21  9:04             ` luigi scarso
2009-01-21 11:51             ` Henning Hraban Ramm
2009-01-20 15:19         ` Arthur Reutenauer
2009-01-20 15:26           ` luigi scarso
2009-01-20 16:00           ` Bart C. Wise
2010-06-28 14:15           ` Tagged PDF Steffen Wolfrum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200901200730.28547.bntgcontext@wiseguysweb.com \
    --to=bntgcontext@wiseguysweb.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).