Loading Profile...
Encoding of e-mail notifications
As I understand, most of Unicode related issues have been solved recently. Also, into the text part of messages all necessary links were included. But after all that we now have another one problem. In the sources of notification e-mails subject and plain text body are declared as iso-8859-1, but actually they are in Unicode.
"""
Content-type: text/html; charset=iso-8859-1;
"""
For the text/html part of the messages encoding is specified correctly as UTF-8.
"""
Content-type: text/html; charset=iso-8859-1;
"""
For the text/html part of the messages encoding is specified correctly as UTF-8.
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hmm. Have looked at the e-mail sources again. In fact, there is no text/plain part at all. My email client just convert text/html and display it as text/plain. It's not very good in my opinion, but anyway, specified encoding of the messages is incorrect.1 Comment
Add a comment
This solves the problem
-
What email client? -
Inappropriate?Thunderbird 3.0a1 (2008050714). But what's the difference? Wrong encoding in the sources of emails doesn't depend on client. The same you could see in Gmail, for example — just use "Show original" menu item.
-
Inappropriate?Some more details on this problem. Here is the subject line (it doesn't display correctly, and I wouldn't expect it to :-)
Subject: c alex commented on ξαναματαβγαίνει μπρ
The subject is HTML-encoded. This is wrong and it appears just like you see it here on email clients. If you want to be on the safe side, it should be base64 encoded, something like this:
Subject: =?UTF-8?B?UmU6IM6pz4HOsc6vzr/PgiDOvyDOk865z47Pgc6zzr/PgiE=?=
One more note. You should do some more work on the email source. Content shoud be base64 encoded, multipart, the HTML part should be real unicode (no html entities) and there should be a text/plain part for anyone that prefers plain text to HTML (my blackberry does, for example)
Panayotis.
1 Comment Add a comment
This solves the problem
-
Damn! The subject line appears correctly :-) in my previous comment because it's included in a HTML page... I'd be glad to send you by email any details.
EMPLOYEE
