Steps to reproduce: -compose a message with high ascii in the body; -open message in 4.6; -note square at the end of the string //note : if you open the source it looks like the encoder is trying to encode the space after the last char "bonj=C3=B3urs, =C3=A0mic=C3=B6s=16 "

This is not reproducable for me (both release build and local debug build). Checking if anyone else can reproduce this.

i can not reproduce it on Fr WinNT, it is reproducable only on US NT with 6/14/99 build. I'll follow up with the next build.

I am marking this as M8. This is not reproducable in mose cases. Also HTML editor to change to support non Latin1 charset (6672, so i18n smoke test uses plain text send instead). If this keep happening then we can investigate more during M8 cycle.

Using my local build (pull/build 6/28), I cannot reproduce this. I tested html send only because "mail.identity.id1.send_html" did not recognized false for plain text. Was original problem filed for plain text send or html?

It looks like after the fix for # 5521, 4214 it is not reproducable. I don't see it happening on my machine with the current build.We can mark it fixed for now and i'll follow up with futher builds.

Sending it to marina for verification.

** Checked with 7/12/99 Win32 build ** (Pinch-hitting for marina who is on vacation...) There seems to be a strange problem with headers under Latin 1 HTML mail which leads to an insertion of a square box at the end of the header string. Try the following steps 1. Compose HTML Latin 1 mail with 5.0. 2. In the header and body, input the following strings. Bonjour internationê<SP> where is says <SP>, insert a single ASCII space. 3. Send it and look at it with 4.x client. You will see that there is what seems to be a square at the end of thread pane and message pane headers. Notes: A. This looks like an attempt to encode &nbsp; . B. The length of the string was a critical factor. I could not reproduce this problem when I had more characters in the strings, e.g. Bonjour internationnê (one more "n" in the 2nd string) did not cause this problem. C. Other strings I tried were: Bênjournë<SP>, Bënjourê<SP>, Bonjour Internationalê<SP>, etc. None of them produced this problem. So there is something special about the number of characters in "Bonjour internationê<SP>". Shall I close this bug and open another one because this is an extra character for the message headers?

Whe I used the same string for the message body, the extra square character did not show up -- it may be because we are now using "&nbsp;" there now. I obeserved that indeed there is an "nbsp" in the body's representation of: Bonjour internationê<SP>

By the way, in the thread pane of 4.7 Messenger, the extra character looks like a vertical bar. In the message header area, it looks like a square box. I think I'm going to re-open this for now ...

The current problem is header specific. If body has no problem (both html and plain text), please close this and open a new one for the header specific.

Ok. I think what we are seeing is probably what marina saw earlier except that the body now uses entities and so will not see this problem. In any case, I'm resolving this bug as fixed. and marking it verified. Will open a new one for the header problem.