Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24972
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <006501c6b036$2f6f3e60$0100a8c0@pc07653>
To: "PHPdev" <internals@lists.php.net>
Date: Tue, 25 Jul 2006 23:03:39 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: upgrading the zlib extension to unicode
From: nlopess@php.net ("Nuno Lopes")

Hello,

So Andrei asked me to upgrade the zlib extension, but I have a few questions 
I would like to discuss with you:
 * when receiving an unicode string, what should we do? compress with as-is, 
prepend a BOM header (and skip it while uncompressing)?  (now I'm unsure if 
PHP/ICU uses utf16 in the machine endianess or not)
 * when uncompressing, check for a BOM header and return a unicode string if 
it is present? return always a binary string?

I also have another question, but unrelated with the zlib extension, that is 
what is a binary string in PHP 6? I think there were some changes on that 
part (and there isn't the IS_BINARY by now) and I don't really now the 
difference between a binary string and the old string (aka runtime_encode'd 
string)


I hope my questions are clear and make sense,
Nuno