Re: ?Tried Convert Script on encoded script in msg 2 of digest, Vol 2 #388, but...
Re: ?Tried Convert Script on encoded script in msg 2 of digest, Vol 2 #388, but...
- Subject: Re: ?Tried Convert Script on encoded script in msg 2 of digest, Vol 2 #388, but...
- From: Paul Berkowitz <email@hidden>
- Date: Sat, 17 Feb 2001 14:06:58 -0800
On 2/17/01 1:47 PM, "Bill Christens-Barry" <email@hidden> wrote:
>
What I did was copy the script code and then run Convert Script 1.0d2
>
from the OSA menu. Then I pasted back into ScriptEditor. There, I
>
noticed that the line break before the 'then' command fragment, that
>
was present before processing, was still there after processing.
>
>
Have I misunderstood Convert Script's intended scope? Is this kind of
>
email-imposed line break not handled by the encoding side? Did the
>
line break arise after the encoding, and if so, is this an event that
>
Convert Script is not intended to deal with? In any case,
>
ScriptEditor gags on it without further repair.
>
>
What to do?
it doesn't deal with plaintext email-imposed line breaks? How could it know
which were intended and which were not?
But if you know you'll be using the Convert Script, then you can write short
lines using the line-continuation character, which will be converted back to
what it should be from the comma that the server mangles it into.
That doesn't help, you when someone else has posted long lines which
hardwrap, of course. I personally find the easiest thing to read is
indenting all lines of a script so that you know that any lines not indented
are continuations of long lines. You have to fix these yourself in a script
editor.
Eventually Chuq plans to convert all his lists to HTML, which softwraps
lines, so this particular problem need never crop up again. I am on some
mailing lists which do this already (and where everyone has an
HTML-compliant email reader by definition) and it works great.
--
Paul Berkowitz