Closed Bug 366981 Opened 18 years ago Closed 18 years ago

Too long From: line makes the window with attachments not rendered

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mmokrejs, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070104 SeaMonkey/1.0.7 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070104 SeaMonkey/1.0.7 Bug 1: I have received an email which for some encoding reasons has in the From: line a very long user name, followed by his email address. Because this string is very long there is no space to render the window with attached files in the frame. Either there should be a horizontal scroll-bar introduced when user wants to view email headers or attached files (preferred) or the output should be rewrapped. In my case, the latter would not help because there was not a single space in the 1251 characters shown below in the next bug. Bug 2: Please fix a problem with displaying the cp1250 encoded username in the From: line. It has been sent from a yahoo account and I guess the user has cp1250 on his computer while there is indication of encoding in the From: line itself. Interestingly, after displaying "Message source" the line is correctly displayed in newly opened window using my default UTF8 settings, except one letter: To: "Tomáš" "Mráèek" <xx@xx>, Aaa Bbb CC <xx@xx>, Aaa "bbb" CCC <xx@xx> ----------------^č (there should have been accetend c character instead) The accented letter 'c' I guess has different encoding in UTF8 and cp1250. Copying the email address using mouse right click and "Copy Email Address" I got the following only: "Tom��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������" Reproducible: Always Steps to Reproduce: 1. 2. 3.
Sorry, wanted to say in the second sentence describing Bug 2 "while there is NO indication of encoding in the From: line itself".
This bug is INVALID because you opened one bug for two entirely different problems. Don't do that again. One issue per bug. "Bug 1" is bug 247833. I'm not sure what the problem is in "Bug 2" but, if the header is not properly encoded, there is little to be done to figure out the correct way to display it; many different encodings use similar values. Address-names and Subjects in UTF-8 encoding should be recognized and displayed correctly in recent builds (this was a fairly recent change); otherwise, the header is assumed to be in whatever the default encoding is for the folder containing the message. (Set this in the Folder Properties dialog.)
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.