Solaris is now using some non standard mime charset names in the dtmail, would you please add them into the charsetalias.properties file? The following are the entries we'd like to add: zh_tw-euc=x-euc-tw zh_tw-big5=Big5 zh_cn.euc=GB2312 iso8859-11=TIS-620 Thanks.
reassign to nhotta
Assignee: ducarroz → nhotta
Katakai san, could you take care this?
Assignee: nhotta → katakai
Component: MIME → Internationalization
Product: MailNews → Browser
katakai- make a patch and I will r= it and you got sr= and ask for drivers approval to land into m1.0
Assignee: katakai → ftang
Status: ASSIGNED → NEW
reassign to email@example.com
Assignee: ftang → katakai
I've added the following, which are important for Solaris platform. +zh_tw-big5=Big5 +zh_cn.euc=GB2312 +zh_tw-euc=x-euc-tw +iso8859-11=TIS-620 Also added one for iso-8859-11 and iso885911, which may be important for other platform. +iso-8859-11=TIS-620 -iso885911=ISO-8859-11 +iso885911=TIS-620 I understand we don't have ISO-8859-11 charset encoding and need to use TIS-620 instead. Frank, could you r= please?
Status: NEW → ASSIGNED
Just found another bug about ISO-8859-11 and TIS-620 support in Mozilla: http://bugzilla.mozilla.org/show_bug.cgi?id=127755 If both ISO-8859-11 and TIS-620 will be supported in Mozilla separately, then the line iso8859-11=TIS-620 in my original description should be: iso8859-11=ISO-8859-11 Thanks. Brian.
Yes, I understood. But bug 127755 will be into 1.0? Frank, what do you think?
Comment on attachment 84868 [details] [diff] [review] patch for charsetalias.properties good
Attachment #84868 - Flags: review+
Comment on attachment 84868 [details] [diff] [review] patch for charsetalias.properties sr=alecf
Attachment #84868 - Flags: superreview+
Comment on attachment 84868 [details] [diff] [review] patch for charsetalias.properties please check into the 1.0.1 branch ASAP. once landed remove the mozilla1.0.1+ keyword and add the fixed1.0.1 keyword
Attachment #84868 - Flags: approval+
checked into branch and trunk. Thank you very much for your supports.
verified on mozilla builds 20020710
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.