http://zeitlin.homeunix.com/cgi-bin/mbugs/show_bug.cgi?id=842
Summary: Mahogany encodes Umlaute wrong in Subject line - and
twice using Outbox
Product: Mahogany
Version: 0.65
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Message compose/edit
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
It seems, that Mahogany wrongly encodes some Subject-Lines containing
Non-ASCII-characters.
Those lines aren't correctly displayed by most MUAs, funnily enough
sometimes including Mahogany.
| Subject: =?ISO-8859-1?Q?=E4=F6=FC=C4=D6=DC=DF=20-=20Du=20 wolltest:
| =20es=20nicht?==?ISO-8859-1?Q?=
That subject line ends with an illegal MIME encoded tag:
=?ISO-8859-1?Q?=
It should be:
=?ISO-8859-1?Q?...?=
where '...' was some legitimate encoded data. If there is no encoded data
then it should not be present at all according to the spec.
From: Vadim Zeitlin <[EMAIL PROTECTED]>
Subject: Re[3]: [M-Dev] Foreign Chars's in subject line gets wrongly encoded
To: mahogany-developers <[EMAIL PROTECTED]>
MJ> Ok, the problem seems to be that Mahogany seems to mess with it, when
MJ> actualy sending using the Outbox-Folder.
Ok, I see. Could you please create a bug report about this so that I don't
forget it? Please make sure to mention that this happens when using Outbox
only.
MJ> - I write a message with a subject containing German Umlaute. ()
MJ> - I click "Send", the message gets put in the Outbox-folder
MJ> - I look at the outbox folder, the Subject displays ok
MJ> - I go online and send the message out
Here the problem lies: it encodes it the 2nd time.
MJ> - I get back a reply from my friend, that it is still broken
MJ> - I look at the message in the Sent-mail folder and now - SURPRISE - the
MJ> Subject-line seems to be empty, because M no longer understands its own
MJ> Subject line.
This is another bug. It should decode it...
MJ> Note the part after the second ISO-8859-1, e.g.
MJ> ISO-8859-1=3FQ=3F=3DE4
MJ> === ====
MJ>
MJ> Three or four chars after an '=', smells fishy !
No, it isn't. It's wrong but not fishy :-) After (first) decoding it would
be "ISO-8859-1?Q?=E4" which is a start of a QP-encoded word. So this still
doesn't explain the original string (which was really invalid) :-(
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Mahogany-Developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-developers
