On Sat, Mar 13, 2010 at 8:09 PM, Lester Caine <les...@lsces.co.uk> wrote: > Handling unicode CONTENT is not the problem here. People nowadays expect to > be able to use their own language to write code, and create functions using > words that they recognize. In databases, table and field names are now > expected to support unicode, rather than just handling unicode data pumped > into ascii titled fields. > > Personally I'm quite happy with just using ascii names for things, but more > and more overseas customers provide contact details in 'strange' character > sets that only unicode can handle, and handling THAT in PHP5 is not a > problem. It's when people start building databases with unicode metadata and > expect the tools interfacing with that to understand unicode as well. > > It was my understanding that PHP6 was intended to provide international > users with something that they could use in their own native language? > Unicode titled files with unicode titled classes and functions.
I doubt that many people are gonna start using non-latin characters for the identifiers, as long as most of those generally use the alphabetic keyboard, with which I cannot type any Japanese words as fast as alphanumerics. In addition, I think RTL languages such as Arabic aren't supposed to use with latin punctuation marks in a programming language in the first place. Moriyoshi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
