• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: ?Tried Convert Script on encoded script in msg 2 of digest, Vol
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ?Tried Convert Script on encoded script in msg 2 of digest, Vol


  • Subject: Re: ?Tried Convert Script on encoded script in msg 2 of digest, Vol
  • From: email@hidden
  • Date: Sat, 17 Feb 2001 22:05:14 EST

In a message dated 2/17/01 9:36:37 PM,
email@hidden writes:

>I decided to try out Convert Script 1.0d2 on the following
>preprocessed script in msg 2 of the digest of Vol 2 #388:

I didn't shorten the lines before posting. That only occurred to me later.
After going through the same problem on the OneClick list, the general
consensus was that indenting all lines of a script was the most practical
solution. Any lines starting at the first character would have been wrapped,
are easily identified and need to be rejoined.

This is something that Richard could easily incorporate into his Convert
Script on both sides. Add tab or spaces at the beginning of each line while
pre-processing, and on post-processing, if a line starts on the first
character, the script can re-join them. R23, do you think that's a good idea
and that you might add this feature? I think your tool works great otherwise.

So does anyone else have any ideas for me about my actual question?

Thanks.

Ken Fleisher
email@hidden


  • Prev by Date: Re: scripting -quicktime
  • Next by Date: Facespan 3.5.1: Is it good, or bad, for you?
  • Previous by thread: Re: scripting -quicktime
  • Next by thread: Facespan 3.5.1: Is it good, or bad, for you?
  • Index(es):
    • Date
    • Thread