Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105575
MIME-Version: 1.0
References: <CAEUnE0dNCv3hQL0JTAfi7GAmiBixdRV-Vm+rxudgYt6iS+=ZeQ@mail.gmail.com>
 <CAG9XoMSWeCPLB7mjnXjTOzuFX1ZSdYjC7SJ2A6DO+JxgQZys1g@mail.gmail.com>
In-Reply-To: <CAG9XoMSWeCPLB7mjnXjTOzuFX1ZSdYjC7SJ2A6DO+JxgQZys1g@mail.gmail.com>
Date: Fri, 3 May 2019 00:23:55 +0200
Message-ID: <CACDmYyd9Qqbk=tG+G4ca_OW+fz5ugrOudU3Jo+iJk8qUucrdVA@mail.gmail.com>
To: Benjamin Morel <benjamin.morel@gmail.com>
Cc: Michael Morris <tendoaki@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009f2b3c0587ef17ef"
Subject: Re: [PHP-DEV][DISCUSSION] Multilingual PHP
From: legale.legale@gmail.com (Legale Legage)

--0000000000009f2b3c0587ef17ef
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

We (Russians) have got such experience already. The language is 1S where
syntax is Cyrillic. This kind of syntax doesn=E2=80=99t like even Russian p=
atriots.

=D1=87=D1=82, 11 =D0=B0=D0=BF=D1=80. 2019 =D0=B3., 23:16 Benjamin Morel <be=
njamin.morel@gmail.com>:

> The problem with this approach is that while it may become more readable
> for the native speaker, it becomes pretty much impossible to read for the
> rest of the world.
> Having one single syntax for everyone allows all programmers in the world
> to share code. I can't imagine a world where I'd find a library based on
> Russian PHP on GitHub, that I can't contribute to or even understand (I
> probably wouldn't use it).
> English has the huge advantage to be quite simple to learn for basic
> purposes, and it has a limited alphabet, composed only of ASCII letters.
>
> I'm not a native English speaker but have never been bothered by keywords
> being called IF and THEN, even when reading BASIC books as a child before
> taking any English course at school.
>
> This may be harder for people having a native language with a different
> alphabet, though.
>
> - Ben
>
>
> On Thu, 11 Apr 2019 at 22:32, Michael Morris <tendoaki@gmail.com> wrote:
>
> > Submitted to the floor is a Wired article from 2 days ago I came across
> >
> >
> >
> https://www.wired.com/story/coding-is-for-everyoneas-long-as-you-speak-en=
glish/
> >
> > The manual of PHP is translated into multiple languages - but what are
> the
> > development hurdles of the language itself being multilingual?
> >
> > From what I understand of the compiler - maybe not that much.  The
> language
> > requires an opening tag, so we could hook into that like this example f=
or
> > Japanese
> >
> > <?php[=E3=83=9E=E3=83=8B=E3=83=A5=E3=82=A2=E3=83=AB]
> >
> > A PHP opening tag with such a qualifier would change over all function
> > names and reserved words. Could these would be set on a per file basis?
> >
> > The php.ini file could set the default language, the .htaccess file cou=
ld
> > also on per directory.
> >
> > I'll stop there cause I know there are problems I haven't thought of. A=
nd
> > I'm not going to argue the syntax I just kicked out from the top of my
> head
> > is the best either.
> >
> > But I think it's worth the effort to at least look into the problem.
> Wired
> > has a point - people learn to code faster when they are working with
> their
> > own language. One of the stated goals of PHP's design has been
> > accessibility so this seems to be appropriate.
> >
> > I yield the floor to those smarter and wiser than I.
> >
>

--0000000000009f2b3c0587ef17ef--