Re: Admin: a suggestion on the script corruption problem.
Re: Admin: a suggestion on the script corruption problem.
- Subject: Re: Admin: a suggestion on the script corruption problem.
- From: Christopher Nebel <email@hidden>
- Date: Fri, 16 Feb 2001 13:41:46 -0800
On Friday, February 16, 2001, at 09:56 AM, Chuq Von Rospach wrote:
Brad's suggestion was to create a tool that would take an AppleScript
and
convert it into a form that isn't corrupted by the list server. That
script
could then be posted safely, and that tool (or a mirror one) could then
be
used to decode it on the other side to be used.
I filed an enhancement request a month or two back for 7-bit clean
AppleScript, i.e., nothing but pure ASCII. This whole list brouhaha was
the main reason, but there are others -- e.g., Mac OS X is supposed to
play nice in a multi-platform world, so relying on Mac encodings is not
a good idea.
Anyway, if you use the same "encoding" here on the list as I plan to use
in AppleScript itself, then at some point in the future, you can throw
away the encoder and go back to straight copy and paste. Here's the
plan:
There are only two places where AppleScript requires the use of
Mac-specific characters: the raw code brackets and continuation
characters. There are several others where AppleScript prefers to use
Mac characters, but has a pure ASCII equivalent: not-equal, greater- (or
less-) than-or-equal-to.
My suggested equivalents for B, (continuation), B+ (left chevron), and B;
(right chevron) are \, << , and >>. Currently, none of them can occur
in AppleScript source outside of strings, so they won't introduce any
ambiguity. For other Mac characters, use the ASCII versions, e.g. >=
for b % (greater-than-or-equal-to).
--Chris Nebel
AppleScript Engineering