| What font are you using in the Read Message window? You could be
using a proportional font for reading, in which case, yes, the
spacing and alignment would look different from what you sent.
Try selecting a monospaced font (such as Courier) in the Read Message
window (Options -> Font).
Another culprit might be the "Wrap Lines When Sent or Saved" option for
the text style that you're using when you create messages. If it's on,
try turning it off. (In the Create Message window, choose Format->Current
Message and look on the Options tab. Use Format->Cover Memo Style if you
want to change it for all messages created using a particular style.)
One other thing you could try when reading a text message is turning
"Rewrap Text Attachments" on or off (it's on the Options menu in the Read
Message window; when it's on, the label changes to Don't Rewrap Text
Attachments).
> Also, all notes show a time with PM as the time of day even though it
> is AM. ????
Notes in this conference, you mean? They are given the timestamp of the
system on which the conference resides, and that system is located in ZKO,
Nashua, NH, USA. You, judging by your node name, are located in Australia.
Hence the time difference. :-)
- Nina
|
| Thanks Nina,
It was the ReWrap Text Attachments that was causing the problem. Much
Appreciated !
On the AM PM issue, it is my Teamlinks Inbox (and all other folders for
that matter) that is showing PM against each note. This one makes it
really difficult to tell what time something was sent.
regards
Chris
|
| Chris,
> On the AM PM issue, it is my Teamlinks Inbox (and all other folders for
> that matter) that is showing PM against each note. This one makes it
> really difficult to tell what time something was sent.
I've seen this problem on WinNT 4.0 if you use 24 hour time. I've never
seen it on Windows 95. Is that what you have?
MS has a bug in Windows NT 4.0. The PM string value is supposed to be
displayed for all times when 24 hour time is used, but normally this
string value is cleared. For some reason it's not cleared in the
Windows NT Registry. MS is supposed to fix it.
I hope this isn't also happening on Windows 95. Please verify and I'll
look into it.
Bob
|