-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Lukas,
> As such the conclusion can only be that investing any time in readding > this "feature" would be a bad idea. If anyone actually uses this feature > they will have to come out of the woodwork now or when 5.3 is out. At > this point we might have enough information to actually understand how > that feature is used and how we can add it to 5.3. I really don't know what is so hard for you understand with this feature. It switches the Zend Parser into another encoding that is used when reading from blah.php files. (okay there is also some auto detecting magic). The reason for this is very simple. It allows you to write f.e. Japanese in strings. If you use Shift-JIS then several Japanese characters will not work in single byte PHP. The backslash (escaping) character is part of several Japanese characters. In single byte PHP these characters are wrongly considered as escape sequences by the parser while the multi-byte parser realises that they are not escape sequences. The same is true for chinese people using GBK. (afaik GBK is not completely within utf-8) Stefan Esser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhhBgwACgkQSuF5XhWr2nivWwCghOHAq9l0wrORJ9/3d7a4/RTz Qp0AoJj3zqjxjTgEs1JlJZK5TftsCHcG =rTY0 -----END PGP SIGNATURE----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
