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:Dan Goldstein <DGoldstein -at- nuot -dot- com> To:"TECHWR-L (techwr-l -at- lists -dot- techwr-l -dot- com)" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 24 Nov 2014 12:35:43 -0500
No apologies necessary! I know nothing except what I've learned from others - mostly on the Word-PC list, which is pure gold. The good news is, Word is not a lousy word-processing program, it's an excellent one. But unlike Frame, Word is ubiquitous, so people assume that it requires minimal training for power use. Anyway, some details:
The problem with change tracking is that it's cumulative, it's messy, it burdens the document with unnecessary data, and it prevents you from properly applying styles. By "accept and reject all changes," my unclear point was that you want to get rid of the current tracked changes by accepting the ones you agree with and rejecting the ones you don't. Change tracking is sometimes necessary when you're working with a team, but you shouldn't have to track your own changes for your own view.
I include my initials and the date in the file name of any draft that I send to other people, and not just for Word documents! I update that date when I make significant changes. So if I distributed "DudleyDoRight DJG 2014-11-21.xlsx" on Friday and now I'm making significant changes, I'm gonna call the new one "DudleyDoRight DJG 2014-11-24.xlsx."
How large are the graphic files that cause catastrophic crashes, and what file types are they?
An anchored picture is one where text wrapping is in line with text. A floating picture is any of the other options. This is in the Picture Tools ribbon tab (ecch), under Wrap Text.
Text wrapping for tables is in the Table Properties dialog box.
Linking a picture works only if you control the file locations. When you go to the Insert tab, click Picture, and select the image, first click the little arrow next to the word "Insert." One of your options is "Link to File."
Word document section breaks should be used only for page format changes: columns, headers and footers, etc. People tend to throw them in too much, especially in imported documents that were created in other applications.
From: Lynne Wright
Sent: Monday, November 24, 2014 12:04 PM
To: Dan Goldstein; TECHWR-L
Subject: RE: Large Documents in Word
Thanks Dan... forgive my Word ignorance, but I've got a few questions:
- "Accept and reject all current changes and save with a new file name."
I'm confused... how can you both accept AND reject something? What do you mean by "current changes"?
And EVERY time I work on a file, I have to save it under a new name? If I work on the same file every day for a month, that's a LOT of renamed drafts.
" Insert graphics from a file"
- If you mean that in the Insert tab, click Picture, then navigate to and select the image, then that's what I've been doing. I'd say that leads to a catastrophic crash about 1 in 20 times.
- how do you anchor a picture or a table?
- "link graphics" ... to what?
- "If the document causes trouble, Maggie it." What does "Maggie it" mean?
- "minimize section breaks" ??? meaning avoid breaking up the material into logical and workable chunks?
Overall, this just confirms my suspicion that Word is actually a pretty lousy word processing program. Which is kind of a relief... I thought the problem was me.
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l