Although MT support multi-language, the build-in email system does not. Every Email send through MT system is encoding with iso-8859-1, so they are not readable for some unicode blogs.

Adding this feature to MT's next version would be greatly appreciated.

What do you have in mt.cfg for PublishCharset? That should determine the encoding for email as well (in 3.x).

in mt.cfg, it's set to:



I thought this is supposed to cover all UTF-8 issue, but the emails are still unreadable.

When I changed my PublishCharset in mt.cfg, it caused a visible change in my emails, and I can tell from the headers that the charset changed back and forth accordingly.

But I don't have the NoHTMLEntities option enabled either.

Hello Shelley,

I want to modify the default character set from ISO-8859-1 to UTF-8, I think this may solve the problem.
Could you tell me which files I should modify?
Thank you.

Changing PublishCharset in mt.cfg should modify the default setting, that's why I don't understand why it wouldn't work in your case.

I had to do just the opposite. I had to modify the mt.cfg from utf-8 to ISO-8859-1 because when my readers tried to sign into Typekey in IE6 they had to refresh the page to show they were logged in. Doing this solved that irratating problem, although I do not know why. I got that suggestion from a MT support ticket I submitted and this was what I was told.

well, I dont understand either.
But I'm positive that I have modified and updated the mt.cfg to the utf-8 as following



and the email notification still doesnt work.

One more example about this issue, I tried this comment button hack, when I submit comments, the individual archive page turned automatically to "Western European" encoding instead of "utf-8", I have to refresh the page to load the utf-8 encoding.

I think changing all the default charset (which is iso-8859-1) to utf-8 should solve this problem, I can manually do that, but I dont know which files they are in.

Right but that was for a different problem related to IE.

Well, that's my point - the setting in mt.cfg controls the default - you are using version 3.0 or higher, right?

Maybe your email program is changing the charset for reading email? I use Outlook 2003, and I can tell by the message options that the charset changes back and forth depending on what I have for that setting in mt.cfg.

I had the same problem for months. Finally couple of days ago decided to solve this problem and couple of minutes ago just figured it out!
It's so simple. Instead of the code mentioned above, place this code in your mt-config: