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: Richard 23 <email@hidden>
- Date: Sat, 17 Feb 2001 21:51:06 -0800
>
Well done, richard! Until Chris Nebel's new ASCII-7 AppleScript is released
>
(talk about cart before the horse: changing the language as a solution for a
>
mailing list's illiterate server!), this is a real help here.
Thanks. I suppose if nothing else the tool can be used to unmangle
scripts in
the archives which weren't preprocessed (from Oct 28, 2000 thru ?)...of
course
it should have a 100% rate on preprocessed (R23) script snippets during
that
period.
Version 1.0d1 handles translations using the mangle method employed when I
first started actively reading the list around june/july 2000.
Version 1.0d3 will be up tonight. It will contain one or two default
"beeps"
so that the script won't use the system beep if the default "processed"
sound
is missing. I suppose not everybody has "Whit".
It also fixes a little glitch I noticed where two continuation characters
in
a row (which shouldn't happen anyway) are mistranslated when run multiple
times (to email/to script/etc).
If anyone who takes the time to read the docs finds something unclear,
let me
know so it makes more sense to the next person.
The only other thing that really needs to be done is to re-join the lines
which wrap prematurely due to a length greater than 76-80 characters.
Probably not too difficult to do do on the email --> script side... it's
just a matter of detecting if the previous line is indented, and joining
the non-indented (continuation) to the previous line.
The reason I hadn't done it up to this point is that the join possibly
shouldn't occur if the line breaks in the midst of a quoted string.
I have handlers that do this sort of thing, but there's a certain amount
of psychic ability needed in the script to know for sure, so it would be
an optional decode action.
R23