Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105258 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 40708 invoked from network); 12 Apr 2019 01:12:22 -0000 Received: from unknown (HELO xdebug.org) (82.113.146.227) by pb1.pair.com with SMTP; 12 Apr 2019 01:12:22 -0000 Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 452D910C7C1; Thu, 11 Apr 2019 23:09:51 +0100 (BST) Date: Thu, 11 Apr 2019 23:09:50 +0100 (BST) X-X-Sender: derick@singlemalt.home.derickrethans.nl To: Walter Parker cc: PHP internals In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: Re: [PHP-DEV][DISCUSSION] Multilingual PHP From: derick@php.net (Derick Rethans) On Thu, 11 Apr 2019, Walter Parker wrote: > I also am old enough to have used/remember using BASIC. I remember German > and Japanese friends that wrote in BASIC. It was interesting to see German > programs where all the keywords were in English and all the text was in > German. The Japanese was even more strange as the system had to switch > between the code pages for ASCII/LATIN and the one for the Japanese > Language. > > Today to get something other an ASCII/LATIN, we would have to support > Unicode for source code. Does PHP currently work if Unicode is used for > identifiers? Yes. You can use UTF-8 for function names and variables (but please don't!). My favourite annoyance is using a non breaking space in function/method names ;-) cheers, Derick