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: Large Documents in Word From:Tony Chung <tonyc -at- tonychung -dot- ca> To:Lin Sims <ljsims -dot- ml -at- gmail -dot- com> Date:Mon, 24 Nov 2014 15:22:31 -0800
On Monday, November 24, 2014, Lin Sims <ljsims -dot- ml -at- gmail -dot- com> wrote:
> I don't suppose you'd care to share that brilliant system, would you?
> <hopeful look>
> Part of the rationale I'm being given is that they want the designers to
> be able to edit source files. This will obviously require multiple files
> and the "enforced track changes", amongst other things you mentioned.
As it wasn't my system, I probably can't share the specifics. However, I
can explain the process, and you should be able to work out a method to
achieve the same results yourself.
The concept included:
- A revision control system
- Word document masters
- Macro-enabled templates
We authored the documents in Word and stored to our local folders,
uploading versions into the revision control system to mark major changes.
A macro saved the file as a revision copy, enabling track changes
(protected by password), standardized the file name, and saved it into a
shared review folder.
The rest is pretty straightforward.
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l