1. Foreign language support
Rob,
After reading Igor's post I just tested 2.4 and found the following:
integer =D1
=D1=3D1
? =D1
if getc(0) then end if
(where =D1 is alt-165) and it worked without a hitch, however using x=D1
or =D1x does not work.
I assume that =D1 is being interpreted as a bytecode for some inbuilt
routine & it is letting me redefine it.
If so, how difficult would it be to allow eg x\=D1 or some other lead-in
character to suppress the bytecode interpretation?
=46or foreign language users I could then hide all the \ inserting on
file load and save in MEditor.
Pete
2. Re: Foreign language support
id <20030603035223.BEXQ1059.tomts23-srv.bellnexxia.net@RapidEupho=
ria.com>
for <EUforum at topica.com>; Mon, 2 Jun 2003 23:52:23 -0400
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko=
/20030208 Netscape/7.02
X-Accept-Language: en-us, en
1463747838-1054602436 at boing.topica.com>
Pete Lomax wrote:
> After reading Igor's post I just tested 2.4 and found the following:
>=20
> integer =D1
> =D1=3D1
> ? =D1
> if getc(0) then end if
>=20
> (where =D1 is alt-165) and it worked without a hitch, however using x=D1
> or =D1x does not work.
>=20
> I assume that =D1 is being interpreted as a bytecode for some inbuilt
> routine & it is letting me redefine it.
Yes, most of the codes over 127 are reserved for use as short
single-byte codes for keywords/builtins by the shrouder/binder.
> If so, how difficult would it be to allow eg x\=D1 or some other lead-in
> character to suppress the bytecode interpretation?
I guess it would be possible.
> For foreign language users I could then hide all the \ inserting on
> file load and save in MEditor.
I'm not sure what you are trying to do.
Are you storing Euphoria programs using your own
set of compressed codes? How does that affect foreign users?
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: Foreign language support
> id
<20030603035223.BEXQ1059.tomts23-srv.bellnexxia.net@RapidEupho=
> ria.com>
> for <EUforum at topica.com>; Mon, 2 Jun 2003 23:52:23 -0400
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
Gecko=
> /20030208 Netscape/7.02
> X-Accept-Language: en-us, en
<1456078044-=
> 1463747838-1054602436 at boing.topica.com>
>
> Pete Lomax wrote:
> > After reading Igor's post I just tested 2.4 and found the following:
> >=20
> > integer =D1
> > =D1=3D1
> > ? =D1
> > if getc(0) then end if
> >=20
> > (where =D1 is alt-165) and it worked without a hitch, however using
x=D1
> > or =D1x does not work.
> >=20
> > I assume that =D1 is being interpreted as a bytecode for some inbuilt
> > routine & it is letting me redefine it.
>
> Yes, most of the codes over 127 are reserved for use as short
> single-byte codes for keywords/builtins by the shrouder/binder.
>
> > If so, how difficult would it be to allow eg x\=D1 or some other
lead-in
> > character to suppress the bytecode interpretation?
>
> I guess it would be possible.
>
> > For foreign language users I could then hide all the \ inserting on
> > file load and save in MEditor.
>
> I'm not sure what you are trying to do.
> Are you storing Euphoria programs using your own
> set of compressed codes? How does that affect foreign users?
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> http://www.RapidEuphoria.com
-----------------
Rob, this salad on top is a Topica's bug.
It doesn't like 128..255 codes now.
A few months ago, there was a good
understanding of these codes on Topica.
Regards,
Igor Kachan
kinz at peterlink.ru
4. Re: Foreign language support
On Mon, 02 Jun 2003 23:52:27 -0400, Robert Craig
<rds at RapidEuphoria.com> wrote:
>I'm not sure what you are trying to do.
>Are you storing Euphoria programs using your own
>set of compressed codes? How does that affect foreign users?
MEditor already stores keywords internally in memory using bytecodes
(1..24) and splits lines into appropriate chunks for colourisation.
(As an aside, mainly for anyone else reading this, it also currently
stores builtins as bytecodes 128..212, and either that would need to
be changed to a leadin (probably 29) and a bytecode 0..127, or better
any user-keyed #80..#FF characters held as {leadin,#00..#7F}).
So all this is happening internally already, not that you'd ever guess
from a binary dump of the source files MEditor creates.
Realising a significant start is already in place, I was thinking of
storing the Euphoria code on file, eg (a terrible stab at French):
pour =C7=D1 =3D 1 =E0 10 fait
as
for \=C7\=D1=3D1 to 10 do
and just modify the editor to map one to the other mechanically.
Pete
