|
From what it looks like, you are basically adding UTF-8 as another charset, correct?
At this point we support thre charsets: I am wondering if there is some sort of master list of charsets we should add. If we have KOI8_R, and (In reply to comment #2)
> From what it looks like, you are basically adding UTF-8 as another charset, correct? > > At this point we support thre charsets: > /** */ > public static final String KOI8_R = "koi8-r"; > /** */ > public static final String ISO_8859_1 = "iso-8859-1"; > /** */ > public static final String US_ASCII = "us-ascii"; > > I am wondering if there is some sort of master list of charsets we should add. If we have KOI8_R, and > are now adding UTF-8, what other obscure charsets should we take care off? Hello, I'm Japanese. Created an attachment (id=17239)
patch for "order fixed calling methods". Hello Philip, For example... In this case, charset "ISO-2022-JP" won't be used. then I tried to make patch Please check it, and give me some comments.
Henri Yandell made changes - 16/May/06 10:00 AM
Henri Yandell made changes - 16/May/06 11:33 AM
Henri Yandell made changes - 16/May/06 12:09 PM
Ben Speakmon made changes - 10/Jan/07 08:23 PM
Adding link to related issue.
I've submitted a patch for this issue in
Henri Yandell made changes - 17/Feb/07 09:52 AM
dion gillard made changes - 22/Feb/07 11:57 PM
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Properly sets the value of setCharset() into the resultant email message
That's a bug. The input to setCharset() is ignored in all cases. I'm trying
to send mail in UTF-8 and I'm having a similar problem as the previous person.
Here's a patch that fixes the problem.