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.
Chris Anderson observed: <<I think the negative comments are more related to
fear, WORD bashing and user error.>>
Don't forget that the links I posted came from the Word MVPs site. These are
hardly people who fear word, bash it, or make lots of errors in their
advice. But let's take each in turn from my perspective:
Fear: Yes, I fear Word--as the saying goes, "Word happens", and it's not
always clear why. <g> But I love the power of the software, and having come
to understand its greater and lesser weirdnesses through ongoing
hand-to-hand combat, I now use it exclusively for my writing. Wouldn't use
anything else, in fact.
Bashing: I don't bash Word, though I do frequently diss it in a loving kind
of way. I also have no hesitation about pointing out its weaknesses. Anyone
care to mention autonumbering?
User error: I'd be the last one to say that software users don't make
errors. That's always a possibility.
<<Other people say "Don't use Master Docs". Ok, so what is your solution
for producing a 1,300 page product in WORD?>>
As noted in my original post, use RD fields--much more reliable, or (if you
prefer), at least less vulnerable to user errors. Check the archives for
details.
<<So, assume you have to use word to produce a large document.>>
It wouldn't be my first choice for really long and gnarly projects, but I've
written a couple novel-length books in Word quite successfully. One simple
trick I've also used is to break the single massive file into several
smaller files (chapters). Works like a charm.
--Geoff Hart, geoff-h -at- mtl -dot- feric -dot- ca
(try ghart -at- videotron -dot- ca if you get no response)
Forest Engineering Research Institute of Canada
580 boul. St-Jean
Pointe-Claire, Que., H9R 3J9 Canada
"It's one thing to see death coming at the hands of your own creation.
That's part of the human epic tradition, after all. Oedipus and his father.
Baron Frankenstein and his monster. William Henry Gates and Windows
'09."--David Brin, _Kiln People_
ROBOHELP X4 - THE INDUSTRY STANDARD IN HELP AUTHORING
Buy RoboHelp by July 31st and receive a $100 mail-in rebate!
Find out more about RoboHelp X4: http://www.ehelp.com/techwr-l
Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.