Re: localized keywords, was call by name

glen herrmannsfeldt wrote:
 
>
> Not to mention keywords.
>
> I have wondered about what non-english speakers think about the
> english keywords used in the usual programming languages.

Formal (programming...) languages are not subject to nationalization,
only natural languages are. This includes numerical constants and
string quotes, which in source code never should be affected by
national conventions about punctuation. Did you know that German
strings were quoted like ,,literal", whereas in English (TeX, GNU...)
texts I often found `literal'?

Imagine what your Internet browser would do, receiving a page written in
e.g. German or Chinese HTML?


> It might be that some use a preprocessor to replace language appropriate
> keywords, but I believe most just use the usual english words.

I remember an old homecomputer (Laser), which allowed for a list of
keyword translations for the BASIC language. Not a bad idea, provided
that the token code still used the same token, and used the list only
for display and editing purposes.

While a preprocessor may be a solution for users of basically Latin
character sets, I also remember attempts to translate programming
languages into Russian, what certainly would make sense when Cyrillic
(Gr...) keyboards don't have ASCII keys at all. But unfortunately
the Russian keywords were much longer than the English ones...

Microsoft once had decided to nationalize VBA, with the very welcome
effect that my German WinWord could not be affected by foreign malware
macros <BG>. This bad decision was corrected *very* soon...

DoDi
[Back around 1960 I believe there were a lot of Fortran variants with
the keywords in local languages, but they all disappeared for the
obvious reason that it wrecked portability. -John]

Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: nnews.iecc.com
X-Trace: gal.iecc.com 1205517681 21164 208.31.42.58 (14 Mar 2008 18:01:21 GM
T)
X-Complaints-To: abuse@iecc.com
NNTP-Posting-Date: Fri, 14 Mar 2008 18:01:21 +0000 (UTC)
Keywords: i18n
Posted-Date: 14 Mar 2008 14:01:12 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
Bytes: 2641
X-Original-Bytes: 2598
Xref: number1.nntp.dca.giganews.com comp.compilers:21778

On Fri, 14 Mar 2008 04:27:31 +0100, Hans-Peter Diettrich wrote:

> glen herrmannsfeldt wrote:
> 

But the preprocessor itself should be localized as well... (:-))

> While a preprocessor may be a solution for users of basically Latin
> character sets, I also remember attempts to translate programming
> languages into Russian, what certainly would make sense when Cyrillic
> (Gr...) keyboards don't have ASCII keys at all. But unfortunately
> the Russian keywords were much longer than the English ones...

I remember a revised Algol 68 report published in USSR. All keywords were
translated into Russian. Because Russian is a heavily inflected language
with, as you said, comparably long words, they used abbreviations. It was
an utter mess. In the bookstore I first saw it, I didn't even considered to
buy the book.

> Microsoft once had decided to nationalize VBA, with the very welcome
> effect that my German WinWord could not be affected by foreign malware
> macros <BG>. This bad decision was corrected *very* soon...

Not completely. Excell stays localized. Its German version uses comma for
decimal point, with a devastating effect, as expected...

--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de