J
Jonathan Sachs
I had to migrate to Word 2003 this summer, and I'm still discovering
situations where it creates problems for me by trying to be too
clever.
One: the clipboard list. The first time I copy something to the
clipboard, everything is fine. The second time I copy something, Word
displays a list of clipboard contents down the right side of the
window, cutting off part of the document. I don't need that list, but
I do need to see the full width of my document without constantly
closing the stupid list. I can't find anything in Options to turn it
off. What must I do?
Two: filetype interpretation. Today I had to open a large number of
text files (extension TXT) which contained USENET posts. Word simply
refused to open most of them, saying, "<filename> is not a valid
Single File Web Page." Very clever, Word -- you're absolutely right.
They're not Single File Web Pages, whatever those are. They're text
files!!! What part of TXT don't you understand?
It seems to be confused by the USENET headers at the start of each
file, which it takes for some kind of HTML thing... CSS declarations,
perhaps. Again, how do I make it stop?
situations where it creates problems for me by trying to be too
clever.
One: the clipboard list. The first time I copy something to the
clipboard, everything is fine. The second time I copy something, Word
displays a list of clipboard contents down the right side of the
window, cutting off part of the document. I don't need that list, but
I do need to see the full width of my document without constantly
closing the stupid list. I can't find anything in Options to turn it
off. What must I do?
Two: filetype interpretation. Today I had to open a large number of
text files (extension TXT) which contained USENET posts. Word simply
refused to open most of them, saying, "<filename> is not a valid
Single File Web Page." Very clever, Word -- you're absolutely right.
They're not Single File Web Pages, whatever those are. They're text
files!!! What part of TXT don't you understand?
It seems to be confused by the USENET headers at the start of each
file, which it takes for some kind of HTML thing... CSS declarations,
perhaps. Again, how do I make it stop?