Why
should you care?
You should care about OG files and formats because
the printing industry is compatible with two graphic file formats,
and two alone. The first is .eps (Encapsulated PostScript) and the
second is .tif (Tagged Image File). Other file formats, like those
listed as OG Files, will likely cause output problems for the print
industry. The majority of OG Apps fail to support .tif and .eps. Ergo,
we have a problem. Even in rare cases where OG Apps can create .tif
or .eps files, data contained in those files is usually incorrectly
defined. See the next issue of ePUB Illustrated for more on this,
and other problems. ePUB Law #2 - If it is an OG App, the resulting
file is NOT OK for print publishing without significant "extra" work.
Quite simply: the printing industry works
best with properly prepared files, properly created in professional
graphics applications. It is a very proper industry. Any application
or file that interrupts this process, or is outside the normal production
workflow becomes the proverbial monkey wrench. Since the majority of
OG applications fail to properly support these formats, the use of OG-anything
usually causes output problems.
Can
I Use OG Applications and Files?
Yes, just not for any print publishing
that will be produced via commercial offset. Camera copy is your best
friend if you are an OG user, whereas the resulting OG files are your
enemy. For commercial offset print publishing, OG Apps and Files simply
are not a good fit. The reasons vary, some technical and some not, but
the print industry does a poor job of supporting OG files. In fact,
using OG applications for print design is the cause of many of the production
delays and cost increases that currently plague GPO customers. The use
of OG applications is one reason why many customers find that supplying
Electronic Design and PrePress Files (EDPP) costs more than supplying
negatives or camera copy.
Why are OG Files
used?
It is no secret that OG files cause output
problems for the print industry. Given this fact, most sane people wonder:
if files from OG applications are so bad, why do Content Creators (CCs)
use them to create documents? The answer is frustratingly simple. OG
files are submitted for print publishing because OG Apps are readily
available to CCs. OG applications are what creators have, so they are
what creators use. Word, PowerPoint, Excel, and/or WordPerfect are on
most desktop computers, and in most cases, CCs have OG application training.
Creators are comfortable creating publications and documents in these
Apps. Consequently, most CCs begin work on projects using OG applications.
Little thought is given to how the file will be output.
It is this last fact, that little thought
goes into how files will be output, that makes our problem a problem.
To the average CC, OG Apps seem custom made for design and publishing.
After all, with today's advances in desktop printers, CCs can print
remarkably high-quality documents in their office. In fact, we do not
have a problem if the OG Files stay local to the desktop printer. The
problems only occur when you pass OG Files to a vendor. OG Apps may
be desktop publishing applications; however, they are not prepress
applications. ePUB Law #3 - If you think there is any chance
that your document, publication, etc. may be printed by the print industry,
do not use OG Apps or Files for anything other than keying text.
- Case Study: Customer X is tasked with creating a
report. Customer X starts creating the report in Microsoft Word. X's
boss asks for charts, graphs and clip art (to add impact). X creates
charts in Excel, and finds clever clipart in PowerPoint. X continues
updating and revising the report. Finally, the report is finished
(after months of work), and printed on a color ink-jet or laser printer.
The boss loves report, thinks it is "gorgeous." The boss brags to
management who consequently decides that the "Public" needs to see
the report. X sends the report to GPO as Word files for a 4000 copy
run. GPO bids the job, and vendors run, screaming into the night -
"Why didn't they use Quark?"
(OK, that last bit may be an exaggeration - but only slightly.)
Why
do OG applications cause problems?
Simply put, files from OG applications
are incompatible with the process of commercial offset printing. OG
applications are not designed to support the process of print publishing,
and print publishing does not support OG Apps or Files. Production problems
are so numerous that successful output of OG files is more a matter
of luck than of skill. Vendors that successfully output OG Files usually
factor in extensive work-a rounds that raise costs, and may introduce
new and exciting problems. Based on this incompatibility, GPO recommends
that CCs avoid using OG software for any facet of print design. The
continuation of this article details OG problems and causes.
The End!
CCs who use OG software are typically
new to the world of print publishing. These users are confused by the
commercial offset printing process, and cannot be expected to create
proper files. Additionally, most customers who use OG applications have
unrealistic expectations regarding output. OG users have a tendency
to not understand Color or Color Gamut. They do not understand resolution
issues for print. They do not understand spot colors. In general, they
do not understand the print publishing world. But, we like them anyway!
These are the folks that we can reach out to and educate, to make the
better designer for tomorrow. That is why ePUB Illustrated is
here!
The fork is in, and the subject of Background
is done. OG applications should not be used, but are. They cause output
problems, which cause cost increases and schedule delays. But, they
are used because OG applications are what customers have. As professional
printers, we all wish it was not the case, but it is. There seems to
be nothing much we can do, or is there…?
Look for the continuation of this article
in the next issue of ePUB Illustrated.
| "If
they have it, they will use it!" |
|
|
- Devin Dostner in "Field of PrePress Dreams"
|
