RE: international language support
Igor, I've looked at your rex program and am impressed.
I don't have a cyrilic code page and so it is not as pretty
as you see it I'm sure, but still beyond what I had imagined.
I only see jumbled accented letters and graphic symbols
where you see cyrillic text. Anyway it got me to looking
at the code for the editor and maybe it won't be as hard
to change a few things as I thought.
The problem I was worried about - clashing keywords with
other people's variable names - doesn't really exist. If the
Foreign LAnguage PRogrammer (FLAPR) includes a file
that uses variable names that conflict with his version of the
keywords it won't be a problem because the preprocessor
doesn't translate the included file, just the current document.
Euphoria then runs (reads) the included file at the same time
as the translated program. No problem at all. The conflicting
keyword has all ready been changed into english. The FLAPR
cannot try to include unprocessed files in their program, they
must only include the translated version.
The message catalog idea can be used not for the program
itself, but for the editor! What I would have done is leave the
editor commands - open, save, help, quit, etc. in english, but
these can be placed in the lang.ini file as well as the keyword
substitutions, and voila, you have a foreign language editing
environment. Even easier for the FLAPR to use euphoria. One
more reason that they should use (buy) euphoria instead of some
other old-fashioned single language language.
I'm sure that english will continue to become the main global
language even if euphoria can be used by FLAPR's for another
50 or 60 or 200 years. It could even be the stepping stone to
allow comprehension, a bridge between their language and
english.
JOHN
|
Not Categorized, Please Help
|
|
