Re: international language support
Hi John,
> I have commented where changes should be made. I don't
> know if different code pages are going to bite or
> not. I have found that although the keywords can use
> accented vowels, the variables cannot. That is because
> the keywords are substituted before they hit the
> interpreter while the variables are unchanged and the
> interpreter chokes on them - uses them for internal
> tokens perhaps?
Yes, John, the accented vowels's codes are from 128
to 255 and Eu *interpreter* use these codes for own
internal needs (this is Rob's area now, he says).
So, in variables, these symbols (128..255) must be
replaced with the pure latin symbols (before 128),
same as native keywords are replaced with the standard
ones. Then any DOS standard code page must work OK.
> I hope some others on this list will produce the
> spanish, french, belgian, dutch, german etc versions.
> Just change the language.e file.
> I've just thought of an improvement. I think now that
> the language.e file should just have one line that
> says "include portuguese.e" or "include russian.e"
> Then there wouldn't be a lot of different language.e
> files around. Well, they would all be different, but
> you know what I mean, just the one line.
Yes, I think a good place for the national keywords
are files just like to keywords.e, but new, say, keywords.e
for the standard English key words and additional files --
keywords.ru, keywords.ge, keywords.fr, where "ru", "ge",
"fr" .. are the standard ISO signs for the national
languages in the Internet.
Regards,
Igor Kachan
kinz at peterlink.ru
|
Not Categorized, Please Help
|
|
