Closed Bug 604628 Opened 14 years ago Closed 14 years ago

Messages in Greek that are recognized as ISO-8859-1 and are displayed correctly when you forward these messages text gets unreadable-scrumbled

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1026989

People

(Reporter: amoraitis, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; el; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; el; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 Messages written in greek are recognized as ISO-8859-1 and are displayed correctly. When I try to forward these messages the text previously in greek becomes unreadable in the new window (e-mail editor). In order to resolve this I have to manually choose in the original message ISO-8859-7 (greek). Reproducible: Always Steps to Reproduce: 1.Receive incoming mail in greek (ask me and I can send you one) 2.If not already put ISO-8859-1 encoding (You will notice no change) 3.Try to forward this message (suddenly greek is scrumbled) Actual Results: The problem was reproduced greek were unreadble Expected Results: Should keep the text readable
What happens when you reply? It behaves the same as forward?
I just checked. Yes same behavior
(In reply to comment #1) > What happens when you reply? It behaves the same as forward? I just checked. Yes same behavior
Same problem as Bug 597821? If not, can you attach mail data to this bug? (Save as .eml file, attach the file, not paste)
I use AVG and Bug 597821 seems quite the same. I deactivated now the AVG signature on incoming e-mails and I will try later on the day to check whether I have the same problems or not.
Closing as dup of Bug 597821, per comment #5.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Root cause of "charset is pcked up from last attachment" was resolved by bug 1026989 at last. Some valuable bug reports from users were hidden/lost/ignored by "duping to bug 716983, then duping bug 716983 to other bug". Unfortunately, or fotunately, only "garbled display in Forward Inline case" was resolved by unknown bug while the other bug was being processed, so nothing was resolved by the other bug. Duping this bug to bug 1026989, for ease of tracking, search, understanding current status of problem.
FYI. Patch of bug 1026989, one liner patch, was proposed in the other bug to which bug 716983(and bug 701818 too) had been duped to. The patch was dig out from the other bug by bug 1026989, and long lived "charset is picked up from last attachment" issue has been resolved by bug 1026989. Why such "digging out hidden important patch from the other bug" should be needed in B.M.O?
You need to log in before you can comment on or make changes to this bug.