Re: Problems with mime encoding of Japanese Characters in Subject
[email protected] (Darren Cook) Fri, 09 May 2008 12:56:41 +0900
| Newsgroups | php.i18n |
|---|---|
| Message-ID | <[email protected]> |
(This is a reply to a problem in the archives, from March: http://marc.info/?l=php-i18n&m=120595161128203&w=2 ) As you obviously have the mb_string extension installed, have you tried using mb_send_mail() instead of mail()? Then you shouldn't need to mess around encoding your own mimeheaders. <minor rant> Later in the thread Tomas suggested using UTF-8 instead of ISO-2022-JP, and getting Docomo to change. The problem is all those handsets in existence. Not to mention all the other legacy email clients that don't work well with UTF-8, but real people still use. Docomo could convert from UTF-8 to ISO-2022-JP at the gateway of course, which apparently is what softbank and kddi actually do, but Docomo deal with a lot of email so care about the cost of the extra CPU cycles, and you're going to need better motivation for them than "PHP cannot write proper MIME headers" I suspect. </minor rant> Darren P.S. If still no luck, and you want to try writing your own solution in PHP, I seem to have a function called jis_loop() in mail.inc in my open-source fclib ( http://dcook.org/software/fclib/ ) that does this. It is 5 years since I touched that file, and probably 7-8 years since I wrote that function, and just looking at it now I cannot make head nor tail of it. So I'd regard that as a last resort :-) -- Darren Cook http://dcook.org/mlsn/ (English-Japanese-German-Chinese free dictionary) http://dcook.org/work/ (About me and my work) http://dcook.org/work/charts/ (My flash charting demos)