Re: Resource fork interferes with text parsing
Re: Resource fork interferes with text parsing
- Subject: Re: Resource fork interferes with text parsing
- From: email@hidden
- Date: Wed, 3 Apr 2002 11:11:15 EST
I would first read the text file as text, then use the TIDs to change the
text block to a list.
With all the changes in Applescript and the MacOS over the past few years, I
have learned to do everything with "baby steps," so that if one small part
breaks, I need only fix that one small part.
Jeff Baumann
email@hidden
www.linkedresources.com
In a message dated 4/3/02 8:06:33 AM, Joe Lester wrote:
>
I have an AppleScript that reads any text file into a list variable using the
>
"read ___ using delimiter {return}" command. The problem is that if the text
>
file I'm reading happens to have a resource fork, like text exports from
>
TeamAgenda do, my script cannot see the {return} delimiter! Instead it will
>
return with a list containing only 1 element even though the text file has
>
over 50 return characters. I can replace the return with a tab, or any other
>
delimiter, and it works just fine. Is this a known bug with the "read ___
>
using delimiter {return}" command?
>
>
BTY, I downloaded the GTQ Scripting Library which enabled me to delete the
>
resource fork prior to opening the text file using the Kill Resource Fork
>
command. That part works, but still no luck getting AppleScript to recognize
>
the return delimiters. It's almost like, if the text file EVER HAD a resource
>
fork, AppleScript does not recognize return delimiter.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.