User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168pre) Gecko/20070130 SeaMonkey/1.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124pre) Gecko/20070130 SeaMonkey/1.1 I doubt it makes sense to override the encoding specified _correctly_in an email with the encoding selected by the user from menu View/Character_encoding. In this case, if user selects iso-8859-1 encoding, the Subject: line is not rendered correctly. The line contains: Subject: =?iso-8859-2?Q?Objedn=E1vka_byla_p=F8ijata_pod_=E8=EDslem_:_2007015591_.?= and I don't think this should ever be overriden. Possibly same problem would happen with From: and other lines in the header as well? Reproducible: Always Steps to Reproduce: 1. 2. 3.
WFM using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008032201 SeaMonkey/2.0a1pre Martin, do you still see this using current builds from http://www.seamonkey-project.org/ ?
With current cvs HEAD build I get: 1. correctly rendered Subject line 2. the textual attachment is NOT marked to actually be in iso-8859-2 (bug in sender mailer app), so unless I specify View encoding iso-8859-2 it is wrongly rendered 3. however, the View encoding also enforces display over the html attachment, which is in qp and has at least specified the charset withinh the html head (I know mailer ignores that but maybe somebody would improve it): Content-Type: text/html; name="objednavka.htm" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="objednavka.htm" <!doctype html public "-//W3C//DTD HTML 4.0 = Transitional//EN"><html><head><title>Objedn=E1vka</title><meta = http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dwindows-1250"> ...
Assignee: mail → nobody
QA Contact: message-display
You need to log in before you can comment on or make changes to this bug.