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.
RE: Printing problems with Imbedded Excel and Visio files
Subject:RE: Printing problems with Imbedded Excel and Visio files From:"Kathleen" <keamac -at- cox -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 5 May 2005 10:17:35 -0700
Patricia,
If Joe's comments don't help, you might want to attack the problem from
a different direction: why aren't things printing? It's possible there
is a straightforward solution to this problem that someone on the list
could help you resolve.
Kathleen
-----Original Message-----
From: Joe Malin [mailto:jmalin -at- tuvox -dot- com]
I have used ClearCase to manage files, and I'm now using CVS. ClearCase
is complicated and expensive. CVS is complicated and free. SourceSafe is
similar to ClearCase.
All of them are source management systems. To explain the benefits would
take more time than *I* have, and might not be that obvious to others!
In short:
* you get multiple, trackable versions of the same file
* you get "labeling", which means that you can grab all the files that
"belong together" regardless of their version
* you get collaboration and merging, which means that two people can
work on the same file at the same time (usually) without screwing each
other (but see the downsides).
* you get a central file repository
* you can manage any type of file, text or binary. You don't get all the
benefits with binary
files, and you have to be careful to note that they're binary, because
most systems assume
text.
The downsides are:
* someone has to set it up (not trivial) and manage it (definitely not
trivial)
* you get a "file system" sitting on top of your actual file system.
This can be confusing.
* Some of the benefits are lost if you're not using real "source". You
probably can't compare
and merge proprietary formats like .fm, and you certainly can't do it
with non-text files like
Visio or Excel.
Remember that these systems were originally designed to handle text
source code.
Joe
-----Original Message----
From: Patricia Oshea
Imbedding Visio or Excel files into Word or Powerpoint has been causing
printing problems so we have resorted to putting them in as pictures or
objects. The problem this creates is that the imbedded file cannot be
edited from the document in which it resides. This is causing
repetative work because we have to continually re-format the files
submitted from engineering. If we could make files available that they
could just revise, it would save a lot of time. I searched the archives
but didn't see any titles that addressed this specific problem. Does
anyone know of a solution?
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
