#23192 [Asn]: mb_encode_mimeheader mangles long lines?

ID: 23192 User updated by: jc at mega-bucks dot co dot jp Reported By: jc at mega-bucks dot co dot jp Status: Assigned Bug Type: Documentation problem Operating System: Red Hat Linux 8.0 PHP Version: 4.3.2RC1 Assigned To: moriyoshi New Comment: I want to make PHP better and of course make the work of the people in charge of checking bug reports easier so I have to ask: Why doesn't this belong in a bug report? From what I have understood from your comments, there is no bug in mb_encode_mimeheader() *but* there is a problem with the documentation. So there is a bug, not with the function but with the documentation no? For me a bug is when a function does not behave as documented or gives a "broken" result when given valid input. In this case I gave valid input to the function (the RFC says what to do when the input string is longer than 76 chars) and the function gave back a broken header ... At the very least there is bug in the docs because it does not state that mb_encode_mimeheader() is not guaranteed to work will double-byte strings that are too long? I'll happilly submit "report" these to the i18n list instead, I just thought here was the better place since the function *is* broken and should be fixed or the documentation should fixed :) Oh, and what is "HTML-ENTITIES"? Previous Comments: ------------------------------------------------------------------------ [2003-04-16 21:11:27] moriyoshi@php.net Yep, you are always welcome; but I'd rather to see your mb reports such as this one at the php-i18n list first than at the bug database.. ------------------------------------------------------------------------ [2003-04-16 20:45:26] jc at mega-bucks dot co dot jp Thanks. Should I also submit a documentation bug then concerning mb_encode_mimeheader()? I'll try out your solution. But what is "HTML-ENTITIES"? I cannot find any mention of that in the mb_string documenation? ------------------------------------------------------------------------ [2003-04-16 20:36:01] moriyoshi@php.net Hmm, yes, you are right and this is absolutely a problem that is caused by lack of words in the misleading documentation. Besides I forgot to append the correct diagnosis of this problem. mb_encode_mimeheader() can only deal with the most basic elements of strings. That is, it simply treats such a charcter that is represented by a numeric html entity as separate components. Therefore if line folding is done in the middle of a entity compounded of several characters, it inserts CRLF & space there and ends up cluttering the structure of the html entity. To avoid this, you have to do the following conversion on the string before passing it to mb_encode_mimeheader() $subject = mb_convert_encoding($subject, "ISO-2022-JP", "HTML-ENTITIES"); var_dump($subject); var_dump(mb_encode_mimeheader($subject, "ISO-2022-JP", "B")); ------------------------------------------------------------------------ [2003-04-16 20:14:04] jc at mega-bucks dot co dot jp Oh, and you said: >Although mb_send_mail() seems to resolve your problem How does mb_send_mail() seem to solve my problem? I cannot find anything in mb_send_mail() documentation that says it will act differently than mb_encode_mimeheader(). But it does solve the problem I will certainly use it :) ------------------------------------------------------------------------ [2003-04-16 19:51:33] jc at mega-bucks dot co dot jp >Please double-check the documentation Ok, #1 I can't find anywhere in the docs that say that mb_encode_mimeheader() follows RFC2047. #2 Just becuase it follows RFC2047 doesn't say anything about how mb_encode_mimeheader() treats lines that are too long. Nowhere in the documentation does it say that mb_encode_mimeheader() truncates lines ... #3 Since the documentation doesn't say anything I had assumed that mb_encode_mimeheader() would trim correctly convert strings that are too long into "CRLF space" encoded words. Is this right? If so it should be added to the documentation #4 It seems that mb_encode_mimeheader() *did* correctly detect that my headers line was too long and did split the header properly. *However* the subject was garbled when my mail reader put it back together. I am assuming this is because the string is double-byte and mb_encode_mimeheader() cut the string *inside* a double-byte. If this is the case then I would consider *that* a bug. I'm not conversant in double-byte characters ... Did mb_encode_mimeheader() incorrectly cut the string inside a double-byte character? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/23192 -- Edit this bug report at http://bugs.php.net/?id=23192&edit=1