Quote:
Originally Posted by Guessed
Can you explain what it is you actually do with the content of such a large document? It doesn't sound like Word is the best tool for this scale of content because I'm not sure how you would ever totally avoid the WYSIWYG tendencies that underpin Word. It isn't just holding the text, it is continuously working out where that text sits on a page based on the formatting applied to it. Notepad++ (or a database for that matter) doesn't have the same processing overheads.
If you are considering staying with Word, the suggestions I would have are much like those of Charles and Paul above:
1. Minimise repagination by using either Draft (or possibly Web view)
2. Remove all local/direct formatting by selecting all and pressing Ctrl-Q and Ctrl-Space
3. Turn off all proofing so background spell/grammar is not happening
I'm pretty sure the drastic slowdowns you are seeing are unavoidable in Word so I think if it were me, I'd be looking to other software packages rather than persisting with Word.
|
Yes, I've come to that same conclusion. I've decided to go with Notepad++ - I already tested it, and it does everything I need, with instaneous response times. It also has automatic formatting by content, which Word does not - you have to apply formatting to the actual text, either by styles or directly, but you have to do it. Notepad++ allows a formatting definition, so specific patterns of text are automatically displayed formatted. That also serves as a check on content. If I define, for instance, the pattern .AU to be formatted in blue and bold, and the user accidentally types .AV, the formatting does not apply and they have an immediate visual clue that they made a mistake.
What the users actually need to do with the contents is pretty much the same as any other text document: search/replace, and manually edit the text. I know it looks weird - it's a legacy format that serves as the source for a historical book and manuscript library catalogging system. The results then get vacuumed up by Access into a custom database, but that's outside the scope of this issue, and it works well in any case.
Word is great for a great many things, and is the default for any work with text in our institution, but there are peculiar cases that give it fits, and this is clearly one of them.