Is there ever a time when I need to give a printer my source?

  • Thread starter Graham via OfficeKB.com
  • Start date
G

Graham via OfficeKB.com

Hi all,

Newbie to the forum so feel free to point me to FAQs

I'm trying to get to grips with the pushback that commercial printers keep
giving me. They want graphics in format xyz and copies of all fonts and
more often than not 'MAC format'.

What I would like to achieve is providing a standard output file. CMYK PDF
for example. When I suggest this I get strong pushback and invariably they
ask for source.

Should I cave in or keep looking for a compliant printer?

Cheers
Graham
 
J

JoAnn Paules [MSFT MVP]

Cave in - sometimes it's easier to switch than it is to fight. (To anyone
over 45, do you remember the old Tareyton cigarette commercials?)
 
M

Mike Koewler

Graham said:
Hi all,

Newbie to the forum so feel free to point me to FAQs

I'm trying to get to grips with the pushback that commercial printers keep
giving me. They want graphics in format xyz and copies of all fonts and
more often than not 'MAC format'.

What I would like to achieve is providing a standard output file. CMYK PDF
for example. When I suggest this I get strong pushback and invariably they
ask for source.

Should I cave in or keep looking for a compliant printer?

Cheers
Graham
Tell the printer thanks, but no thanks. If a commercial printer cannot
handle a pdf file, then they really are not a commercial printer - just
a pretender.

Mike
 
D

dominic.martin

I agree with the other posts, the printer should accept a PDF. However,
at the end of the day, the printer wants to ensure that your job is
printed right first time. It costs them more than it does you
otherwise. So the source document gives them the opportunity to
`fiddle' with the job in order to get the right output. Once upon a
time, everything would be done on a Mac in Quark but the tide is
turning and (in my experience) not every printer is responding to this.

My advice is to open up a dialog with the printer. Tell them how you
created the PDF. For example, was it distilled using the X1A standard?
What was the source document created in and what settings were applied?
This should lead them into discussing their workflow with you and what
their needs are. If you do this, then both you and the printer will
reach a point where you can give them a PDF and they know that it
shouldn't surprise them with any problems. If the printer isn't willing
to talk with you, then they don't value your business.

Regards,

Dominic
 
G

Graham via OfficeKB.com

Thanks all,

The main motivation for trying to get the interface with printer to PDFs is
to enable my customers to make content changes directly in Publisher they
get the WYSIWYG feeling on a platform that they are comfortable without
having to shell out on expensive software they can't use.

We've had some amusing and some frustrating encounters with printers where
sharing the source to allow them to fiddle has introduced errors and poorer
quality (you live and learn).

I think you are right, the dialog is necessary, they need to feel
comfortable that the files are generated with the right settings and we
need to learn to trust them with source.

Cheers
Graham
 
M

Mac Townsend

I'm going to argue with you (again) on this, Mike.

A properly prepared PDF, great! BUT this is a moving standard. What is
proper for one shop may not be for another, so it is critical to find
out how they want it. Such issues as how is bleed to be handeled vis a
vis page size, and of course font embedding, and the usualy stuff.

industry-wide the percentage of pdf supplied that are properly prepared
is less than 20%.

Resolving these issues in the PDF is going to cost easily 2-10 times
what fixing it in the native applicstion would.

We frequently get business cards submitted one card floating in the
middle of a letter page. Or worse, they come in imposed 10X or something. (
10X is absurd for printing 500 business cards on press).

It all boils down to user knowledge. MS Publisher users as a group
usually have the least such knowledge of the major dtp applications. So
it is quite natural to rather not get something submitted as PDF when
the chances of it being wrong are so very high.

OTOH, there are a great many idiots on the prepress lines as well.
Idiots that think everything has to be output from Quark or must be
macintosh-based.

If a user knows what they are doing and wants to proivide proper pdf,
then they ought to discuss it with the print shop or the service bureau
that the shop uses. Do not assume you know what they want.

In your own case, you've tuned your workflow with that of your printer
over a period of time. You could submit them graven grapefruit skins
provided you know how they like them. But Joe Blow? That is going to be
a problem.

in the case at hand, the mac-only shop can't take publisher files, so
what good would it dfo them (except to let them redo the whole thing and
charge for it, blaming "stupid Microsoft" instead of themselves.
 
M

Mike Koewler

Mac said:
I'm going to argue with you (again) on this, Mike.

A properly prepared PDF, great! BUT this is a moving standard. What is
proper for one shop may not be for another, so it is critical to find
out how they want it. Such issues as how is bleed to be handeled vis a
vis page size, and of course font embedding, and the usualy stuff.

industry-wide the percentage of pdf supplied that are properly prepared
is less than 20%.

Resolving these issues in the PDF is going to cost easily 2-10 times
what fixing it in the native applicstion would.

We frequently get business cards submitted one card floating in the
middle of a letter page. Or worse, they come in imposed 10X or something. (
10X is absurd for printing 500 business cards on press).

It all boils down to user knowledge. MS Publisher users as a group
usually have the least such knowledge of the major dtp applications. So
it is quite natural to rather not get something submitted as PDF when
the chances of it being wrong are so very high.

OTOH, there are a great many idiots on the prepress lines as well.
Idiots that think everything has to be output from Quark or must be
macintosh-based.

If a user knows what they are doing and wants to proivide proper pdf,
then they ought to discuss it with the print shop or the service bureau
that the shop uses. Do not assume you know what they want.

In your own case, you've tuned your workflow with that of your printer
over a period of time. You could submit them graven grapefruit skins
provided you know how they like them. But Joe Blow? That is going to be
a problem.

in the case at hand, the mac-only shop can't take publisher files, so
what good would it dfo them (except to let them redo the whole thing and
charge for it, blaming "stupid Microsoft" instead of themselves.

Mac,

Okay, you have your points. But in this case, the printer didn't really
want to consider trying the pdf. I completely understand printers who
don't want to suffer fools, but not those who will not give a client a
chance to show they have a clue.

From my experience, which admittedly is more confined to a specific
area, I've run across some seriously inept printers. Today, a customer
wants to do a double truck featuring his menus. He had a couple of
changes so was going to have the printer send me the update. Guess what
I got - a pdf file that was a scan of the menu. Imagine trying to scan
8.5 type then make a pdf of it. When I asked if he had something a
little more useable, he sent me a pdf of the file itself. That was
better, but it still would have meant having to typeset a couple hundred
items, increasing the chances for typos, especially given that I was
supposed to get the file last week. I asked again, and found out it was
done in PageMaker. I convinced him to send me the original file. In this
case, though, I will copy/paste the items and prices, etc., then format
them to print a tabloid page. I really ought to get into a better line
of work!

Mike
 
M

Mike Bailey

Mac,

Excellent comments (you saved me the trouble). You actually have a rate as
high as 20% for good PDF files? Having said that getting a 500 page book as a
PDF file that is properly constructed makes my job a breeze for me (as little
as 5 minutes to send it to the RIP at my end). Our sales staff unfortunately
have bought Adobe's line about the PDF work flow so like to get everything in
PDF format... it would be great if Adobe hadn't managed to screw up the
process so much and keep the goal post for producing a decent PDF moving.
IMHO PDF workflow doesn't work and won't unless they stop subsetting fonts
and changing the ASCII character numbers of the subsetted font sets, but I
get into other issues here.

I've had Quark files created on a Mac that won't print, which proves and
idiot with the 'correct' software and the 'correct' platform can still make
life difficult for Prepress people.

Currently the PDF files I have the most problems with come from Adobe
InDesign CS on the PC (and adobe is supposed to know what the standards are),
the defaults for creating a PDF from InDesign are NFG.

If you want a DTP program that can make files that wont print when you move
them to another computer and often get corrupted use Adobe PageMaker (Mac or
PC, it doesn't mater they are equally as bad).

QuarkXPress 6 you say? So far I only have it on my Mac G5 and getting a file
that prints on our Heidelberg 9110 is hit and miss, but I think this is
Adobes moving goal posts for PostScript and PDF standards hitting a poorly
written RIP that is illegibly PostScript level 3 compliant.

Customers who join PDF files together themselves are a real problem (see my
rant about subsetting fonts).

Yet I have had well prepared Publisher files that print fine and just fly
through, proof that the trick is actually knowing what you are doing.

I always prefer to get the native file along with the customer's fonts and
supporting graphics even if a PDF file is supplied. If the PDF file works
great, if it doesn't I can go from there with the native file.

Mike Bailey
Richmond BC
Canada
 
M

Mike Koewler

Mike said:
Mac,

Excellent comments (you saved me the trouble). You actually have a rate as
high as 20% for good PDF files? Having said that getting a 500 page book as a
PDF file that is properly constructed makes my job a breeze for me (as little
as 5 minutes to send it to the RIP at my end). Our sales staff unfortunately
have bought Adobe's line about the PDF work flow so like to get everything in
PDF format... it would be great if Adobe hadn't managed to screw up the
process so much and keep the goal post for producing a decent PDF moving.
IMHO PDF workflow doesn't work and won't unless they stop subsetting fonts
and changing the ASCII character numbers of the subsetted font sets, but I
get into other issues here.
Customers who join PDF files together themselves are a real problem (see my
rant about subsetting fonts).

Yet I have had well prepared Publisher files that print fine and just fly
through, proof that the trick is actually knowing what you are doing.

I always prefer to get the native file along with the customer's fonts and
supporting graphics even if a PDF file is supplied. If the PDF file works
great, if it doesn't I can go from there with the native file.

Mike Bailey
Richmond BC
Canada
Mike,

Strange you find subset fonts as a matter of contention. The PDF-X1a
specs says fonts SHOULD be subset. The joboptions file my printer sent
me has subset all fonts as checked.

It works for me and that's all that counts. :)

Mike
 
M

Mike Bailey

Like Mac says, it depends. If I send the PDF as a single PDF to our Rampage
RIP not a problem, if I have several PDF files that I need to impose using so
it's a Saddle stitch book to send to our Heidelberg 9110 it can be a
disaster. Some applications (like Microsoft Word... which far too may people
think is a good program to use) make PostScript that can't be made PDF-X1a
compatible (at least I've never had any luck). Some equipment doesn't
properly RIP PDF-X1a files. Problem is there is no real standard anymore, not
like the days of level 1 PostScript. Some of our customers create PDF files
that work without issue (even from Microsoft Word) other seem to work at
making bad files... unfortunately the also keep coming back. Making a good
PDF file for print often starts with making a clean file in the native
application since a lot of objects get passed straight through the
application (but this gets into other issues... like EPS files that don't
have the fonts available or embedded, corrupt TIFF files) like objects that
are in a document and not used (like crap on a paste board). I know that the
issue of subsetting fonts is controversial, Adobe seems to embrace it
unfortunately they don't change the name of the font when it gets subsetted
and the screw with the ASCII character numbers, thus if the RIP has the font
in memory (like Arial for instance) and the character 'Z' wasn't used it may
move an opening quote to that ASCII number, the next part of the joined PDF
may need the character 'Z' (in Arial), the RIP has that font (Arial) in
memory so doesn't load it again... so instead of printing 'Z" it prints an
opening quote... apparently that's my fault according to the customer.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top