Re: imap_utf7_decode doesn't work
| From: | Andrew Skalski | Date: | Mon, 24 Apr 2000 20:47:29 +0000 |
| Subject: | Re: imap_utf7_decode doesn't work | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-14003@lists.php.net to get a copy of this message | ||
I tested this with the latest CVS's of php4 and zend, and this is
what happened... it misbehaved as an apache module, but it worked
properly when compiled standalone (CGI).
Between now and the time I commited the original utf7 functions, someone
modified the decode function to output wide characters. The result,
each letter of output is now two characters wide: a zero byte followed
by an ASCII byte. The CGI sapi flush function simply does a "fwrite".
I suspect that something inside apache is stopping the flush after it
hits the first zero byte.
Which leaves us with how to resolve the problem.. does apache get changed,
does sapi get changed, or do we roll back those wide character changes
in utf7_decode?
andy
On Sat, Apr 22, 2000 at 12:26:22AM -0500, chagenbu@wso.williams.edu wrote:
> In php4 cvs, imap_utf7_decode doesn't return anything once it hits an encoded
> character. For instance:
>
> imap_utf7_decode('&APYA9gD2-');
>
> ... will return an empty string.
>
> imap_utf7_decode('abc&APYA9gD2-foo');
>
> ... returns 'abc'.
>
> However, it all seems to work fine with php3. I can't figure out what's
> different - it must be something in the Zend/PHP API, but I have no idea what.
> Can someone take a look, or at least verify the behavior?
>
> -chuck