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.
Subject:Re: Warning re: importing by reference From:Barbara Karst-Sabin <barbara -at- QUOTE -dot- COM> Date:Thu, 27 Aug 1998 13:08:24 -0700
I agree, absolutely. I know most production-types swear by the
"reference" method, but after you've had to spend about 16 hours on a
very tight deadline trying to recreate "screen shots" for a now obsolete
version of Windows from bits and pieces of other vintage graphics,
you'll think twice about the so-called efficiency of the reference
method.
(in case you were wondering why we'd be printing a manual based on an
obsolete version of Windows, it was a localization "patch" until we
could get the next rev completed for translation)
BJ
Elizabeth Kane wrote:
>
> Suzette,
The trouble with importing by ref is that any time
> you copy or move those chapters to another location, you have to make
> sure to also copy every one of the graphic files that are imported by
> ref. You might also have to redefine the path to them. It's a pain!
> What if you lose one of them, or they all get deleted by mistake? The
> only way to make the file usable again is to recreate the captures.
