Re: mb_encode_mimeheader problem
| From: | Gary Ross | Date: | Wed, 26 Mar 2003 03:48:18 +0000 |
| Subject: | Re: mb_encode_mimeheader problem | ||
| References: | 1 | Groups: | php.i18n |
| Request: | Send a blank email to php-i18n+get-517@lists.php.net to get a copy of this message | ||
Hello,
But it seems that on many/some(?) emailers the \n in "STUFF_?=\n =?ISO-2022-JP?B" is interpreted as a new header line, not as part of the subject. I'm not very familiar with the exact rfc rules, does the choice of \n over other possibilities have an effect?
Should I be doing something like this:
$subject =
mb_encode_mimeheader(
trim(mb_convert_encoding($subject, "ISO-2022-JP","AUTO")),
'ISO-2022-JP',
'B',
"\r\n\t "
);
Thanks,
Gary
On Wednesday, March 26, 2003, at 12:23 pm, Moriyoshi Koizumi wrote:
Hi, Gary Ross <php_i18n@j-w3.com> wrote:When I try to use mb_encode_mimeheader on the subject line on an email like so: $subject = mb_encode_mimeheader ( mb_convert_encoding($subject, "ISO-2022-JP","AUTO"), "ISO-2022-JP", "B" ); the result is split up into a lots of parts something like this: "=?ISO-2022-JP?B?_SOMESTUFF_?=\n =?ISO-2022-JP?B?_SOMESTUFF2_?=\n =?ISO-2022-JP?B?_SOMESTUFF3_?=";The behaviour is not wrong, as mbstring is made to be compliant with RFC2047 (http://www.rfc-editor.org/rfc/rfc2047.txt). Moriyoshi