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: Trouble with Word's Mark Index Entry box From:"Jessica N. Lange" <jlange -at- OEE -dot- COM> Date:Tue, 3 Aug 1999 14:43:43 -0400
Kimber,
No ideas, no help. Just wanted to let you know you're not alone.
My Mark Index Entry box does the same thing.
My co-workers on the other hand do *not* have this problem.
(Same computers, same OS, same version of Word 97 (SR 2).
The only difference is that I have *lots* of other programs
that they don't (for winhlp & html editing), plus I'm always
downloading programs to try them out; they don't.
I figure I've hosed this window by something I downloaded,
and I just live with it. However, I do a lot more cut-n-paste
of the XE codes. It's a lot easier, especially with sub-entries.
(For example, I'll copy { XE "printing:" }, then paste that
& type the text after the ":". It goes pretty fast.)
Sorry I couldn't help. If someone provides a solution for
you, please let me know!
Cheers!
Jessica
----------------------------------------------------
Jessica N. Lange mailto:jlange -at- oee -dot- com
Technical Communicator, Ohio Electronic Engravers, Inc.
-----Original Message-----
All of the text fields display only the top 1/2 of the text. So you can't
see
exactly what you're typing. I've made it about halfway through this
medium-sized
manual, but a preliminary look at the index is showing me that I'm going to
have
to do more editing than I wanted to. I've brought my client's application up
to
date with both of the service-pack updates, but the problem remains. Can't
find
anything in this archive or Microsoft's. Any ideas?