Here and there I read that ASCII encoding deals only with codes 0
thru 127.
So I think that it would be fine to edit the AppleScript parser (or
the Standard Additions file) so that when someone type:
ASCII character xx or ASCII number yy
it transcode them to
MacRoman character xx or MacRoman number yy
This would better reflect what we are working with.
While having 'ASCII' in the command name IS misleading, changing it
to 'MacRoman' would also be incorrect since AppleScript strings use
the host system's primary encoding which varies depending on the
settings in the International preferences pane.
Correct. To sum up, it's a bad name, but the alternatives are worse,
so we've left it alone.
Come to think of it, I'm not sure they even work correctly with
multi-byte encodings... (it's a while since I've touched them though
so don't quote me on that).
To the extent that the encoding defines characters for code points 128
to 255, it'll work, otherwise not. "ASCII character" refuses to work
outside the 0-255 range; "ASCII number" will give bogus results. (I
think you'll get the value of the first byte of the string.)
--Chris Nebel
AppleScript Engineering
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
