From: John Culleton <john@wexfordpress.com>
To: ntg-context@ntg.nl
Subject: Re: Producing PDF x/1-a:2001 output.
Date: Fri, 30 Oct 2009 12:48:32 -0400 [thread overview]
Message-ID: <200910301248.32191.john@wexfordpress.com> (raw)
In-Reply-To: <fe8d59da0910300903h342fc4daq5164c5a80d7f564c@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2477 bytes --]
On Friday 30 October 2009 12:03:33 luigi scarso wrote:
> On Fri, Oct 30, 2009 at 4:48 PM, John Culleton
<john@wexfordpress.com> wrote:
> > At least two commercial printers that I use prefer or insist on
the
> > format PDF X/1-a:2001 output. The only way I have found to
> > produce such in TeX without a pass through Adobe Acrobat
> > Distiller or the shareware program Pstill is via the package
> > pdfx.sty
> > authored by CV Radhakrishnan and Han The Thanh. This in
turn
> > uses some other files such as xmpincl.sty.
> >
> > I wonder if this setup could be incorporated into some flavor
of
> > Context? Or even pdftex? I prefer not to live within the
strictures
> > of pdflatex.
>
> is not Ghostscript OK ?
> (I have seen
> http://www.ghostscript.com/pipermail/gs-devel/2009-
September/008566.html)
Yes, I started that thread also. It seems that the spec can be met
via Ghostscript. What is also needed is the internal labeling of the
file as pdf X/1-a:2001, and some xml add-ins.
The prepress staff will look at the file and if it is not labeled
correctly run it through Distiller, which can degrade text and
barcodes by converting them to bitmaps. LSI handles hundreds
of pdf cover files each week, many of which are out of spec. If it
does not look like X/1-a:2001 they will bitmap it, and in the
process mess it up to a degree, or so I am told. So getting the file
within spec is necessary but it also has to look like it is in spec.
Their Customer Service Rep specifically mentioned Ghostscript as
producing non-acceptable pdf files.
This is not the only hoop to be leapt through in dealing with LSI.
they have a limit on total ink coverage that is more restrictive
than the usual formulation for CMYK rich black. They want only
%240 total coverage so I cobbled up CMYK 60,40,40,100 which
adds up to 240%. In brief, they are a royal pain. But they have a
near-monopoly on POD printing for bookstores in the US and their
pricing for Amazon beats anyone including Amazon's own subsidy
Createspace.
Hans:
The needed files and the documentation for pdfx.sty are located
here:
http://www.ctan.org/tex-archive/macros/latex/contrib/pdfx/
The files in the package include:
README
glyphtounicode-cmr.tex
manifest.txt
pdfa-1b.xmp
pdfx-1a.xmp
pdfx.pdf
pdfx.sty
small2e.pdf
small2e.tex
small2e.xmpdata
--
John Culleton
"Create Book Covers with Scribus"
http://www.booklocker.com/books/4055.html
[-- Attachment #1.2: Type: text/html, Size: 4938 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-10-30 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 15:48 John Culleton
2009-10-30 15:52 ` Hans Hagen
2009-10-30 16:03 ` luigi scarso
2009-10-30 16:48 ` John Culleton [this message]
2009-10-30 18:24 ` Hans Hagen
2009-11-02 13:22 ` John Culleton
2009-11-02 13:36 ` Hans Hagen
2009-11-17 13:57 ` John Culleton
2009-11-17 16:05 ` Hans Hagen
2009-10-30 16:27 ` luigi scarso
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=200910301248.32191.john@wexfordpress.com \
--to=john@wexfordpress.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).