Re: Localized Euphoria identifiers

new topic     » topic index » view thread      » older message » newer message

Christian Cuvier wrote:

>> From: Pete Lomax
>>
>> <snip>
>> <snip>
>> and
>> <snip>
>> again
>>
>> my $0.02 on this:
>>
>> We should encourage, or at least not discourage, non-Engish speakers
>> to use Euphoria, even though we may not benefit directly ourselves.
>>
>> I believe it would be trivial to hack an editor to read an "english"
>> euphoria program to display localised equivalents (eg "integer" is
>> replaced with "ganzzahl" or "heltal" (if I guessed right).

I'm sorry. I see now that my German example was not perfectly
understandable, because I forgot to write some _documentation_.
However, your guess is right. smile

>> /ANY/ syntax colouring editor should be able manage this trivially.
>>
>> The actual source stored using the official RDS (english) keywords.
>> Cut and paste to clipboard/standard email is english; a Russian,
>> German or whatever version of EUforum, could equally make them appear
>> in the localised language (IDEA: maybe even cookie based??).
>> Even if not, cut and paste into said hacked editor will automatically
>> perform the expected translation of English keywords.
>>
>> You could even then share code between the forums, apart from the much
>> harder problem of the comments not being in english (viz aku).
>>
> Standardized names for vars/routines may benefit from automatic translation
> tools. This is the crudest form of commenting, but possibly better than
> nothing at all. Again, the issue is coder self-discipline to use the
> standardized stuff as much s/he can.
> As for comments... well, I'm just having the following crazy idea, based on
> the KTS library by T.Carlier, and the mechanism of pad_xml files: make all
> comments into a separate file, and have pointers to these comments in the
> actual code file. Each comment would have local specializations
> (translations). The hacked editor would load the comment in the right language
> to display it (or ask the user which available language he would accept).
> Using an external file for comments would allow adding more translations
> without any interference with raw code.
> A lot of fine points would still need a solution, but... can't that work?
> CChris
>
>>
>> So maybe we Englishers benefit after all.
>>
>> Regards,
>> Pete

These are all interesting ideas IMHO.

But CChris, concerning your suggested "comments database" there will be
a big problem: When I write a Eu program, who would then translate my
comments to say 10 other languages? And in each new version of the
program, when comments have changed, some new translation will be
required.

Regards,
   Juergen

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu