Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29636
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain gravitonic.com from 204.11.219.139 cause and error)
In-Reply-To: <48916.88.118.163.159.1179771974.squirrel@avilys.eik.lt>
References: <51491.88.118.163.159.1179577357.squirrel@avilys.eik.lt> <464EEF4B.1030002@zend.com> <40865.88.118.163.159.1179583186.squirrel@avilys.eik.lt> <464F090A.9090200@zend.com> <35054.88.118.163.159.1179589687.squirrel@avilys.eik.lt> <464F650B.6090802@zend.com> <59165.88.118.163.159.1179641635.squirrel@avilys.eik.lt> <335A483A-55B1-4A1D-A2CF-A6DB0EDDFA5F@gravitonic.com> <48916.88.118.163.159.1179771974.squirrel@avilys.eik.lt>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <AE1365A4-5358-4DE1-8A48-2EB8756351DD@gravitonic.com>
Cc: internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Mon, 21 May 2007 12:46:55 -0700
To: Tomas Kuliavas <tokul@users.sourceforge.net>
Subject: Re: [PHP-DEV] PHP Unicode extension in PHP6
From: andrei@gravitonic.com (Andrei Zmievski)

> They are not documented and I am testing configurations that might  
> break
> scripts. If I test things and want to make code portable,  
> configuration is
> not supposed to be rational. I can set option with ini_set(), if I
> understand what option does and it fixes the issue.
>
> http://www.php.net/unicode
>
> Do you have updated documentation version which explains encoding  
> settings
> and lists available configuration values? Or am I testing PHP6 too  
> early
> and you are still months or years away from 6.0.0 betas and rcs?  
> Could you
> implement pseudo encoding similar to 'pass' encoding used in mbstring?
> Current implementation does not give controls needed by script  
> writers.

Have you looked at any of the talks I've given on this topic?

http://www.gravitonic.com/talks

That's the closest thing to documentation you'll find right now.  
Unfortunately, documentation always lags behind the actual development.

> SquirrelMail scripts are not written in unicode. They are in ascii. If
> some 8bit value is used, it is always written in octal or hex  
> notation.
> These hex values are not written in one character set. In some cases
> scripts use byte values. For example, locating first utf-8 byte or  
> looking
> for 0x80-0xFF bytes in string. In other cases they are written in  
> source
> or target character set. For example, iso-8859-2 decoding function
> contains array with iso-8859-2 hex values mapped to html codes.  
> Code can't
> use raw 8bit strings, because they might be corrupted in misconfigured
> editor used by developer and it is very hard to track such corruption.
> 8bit data can come only from user input (composed emails and  
> preferences,
> html forms, one common charset) and imap server (received emails,  
> lots of
> different charsets and encodings).

Maybe you don't need to turn unicode.semantics=on, if you are working  
only with 8-bit strings.

-Andrei