TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
::: Again, that depends upon the printer and what they can most
::: conveniently handle. For example, I recently did a job in
::: which the printer could most conveniently handle InDesign
::: files, which is what the particular piece was created in.
If a printer cannot most conveniently handle my desired format then they are
not most convenient for me. Period. Sorry, but this is business, not a
happy, bend a little forward bend a little back relationship. My deadlines,
my requirements, my money. Put out or shove off.
I hate to be blunt, but there is absolutely no reason why a print vendor who
wants to remain competitive should not be able to except an electronic file
set up and ready for press in the year 2004.
::: Imposition systems at the printer are critical, and trying
::: to manipulate a .pdf is cumbersome using some of these
::: systems.
Systems current with the technology do not have these problems.
::: In addition, from the source files it is somewhat
::: easier to do separations.
I challenge you to prove that.
::: However, I am curious: why do you *never, ever* send source
::: files to a printer? What "evils" do you avoid in this process?
Error.
Bill Swallow
wswallow "at" nycap "dot" rr "dot" com
