On 20 December 2014 22:44:24 GMT, Alain Williams <a...@phcomp.co.uk> wrote: >Fixing this would require a lot of work as well as some way of >determining what >character encoding the source file was written in ... different >includes might >have different encodings. > >We recently talked about a way of specifying source file encoding and >decided >that it was not something to look at now (IIRC).
I haven't read the whole thread yet, so apologies if someone's mentioned this already, but far from being a rejected feature, specifying source file encoding is already possible, using declare(encoding=...) The problem is what to do with that information: presumably, identifiers would need to be converted to an internal encoding (prob utf8), case folded, and normalised (in the Unicode sense of that term). Ideally, this would happen during compilation and stored appropriately in the OpCache, but a run-time path for userland strings would also be necessary. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
