Hi,
On Do, 2019-04-11 at 15:32 -0500, Michael Morris 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-spea
> k-english/
>
Oh, memories. Microsoft Office has (or had) localised macros. This lead
to many problems since localisaton depends on language installed and
macros from one don't work on the other ...
I don't believe the language itself should be translated. This limits
portability and there are just a few keywords.
If somebody wants to create localised libraries they can of course do
...
An area I would find interesting is error messages. To a little degree
we already have them localized:
$ php -r 'setlocale(LC_ALL, "de_DE");fopen("/etc/passwd", "w");'
PHP Warning: fopen(/etc/passwd): failed to open stream: Keine
Berechtigung in Command line code on line 1
Expanding might be interesting, but it is not a trivial task, as this
might make error reporting (also suppressed one, i.e. deprecation
warnings) slower and it is a big translation and maintenance work and
has impact on support (I myself run my machines typically in English so
I can Google error messages and receive better results or can grep the
source for the origin)
johannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
