• 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: Stupid, Stupid Text Features [Was: Can't set creator type]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Stupid, Stupid Text Features [Was: Can't set creator type]


  • Subject: Re: Stupid, Stupid Text Features [Was: Can't set creator type]
  • From: Mr Tea <email@hidden>
  • Date: Tue, 24 Feb 2004 15:59:06 +0000

On 24 Feb 2004, at 2.18 pm, Paul Berkowitz wrote:

set theCode to <<class ktxt>> of (text returned of dRes) as record

There. I said it was hairy. Paul is one of the most knowledgeable and
experienced contributors on this list, and it's his business to know
this kind of stuff, but what about the rest of us!!!???

It was Arthur Knapp who first brought this method to light, to my
recollection (although Jon Pugh may well have mentioned it before I knew
what was what). I just picked it up here on this list - it was discussed
many times.

Yes. I remember thinking 'what's this ktxt thing that Arthur's on about, it sounds significant', then filing it away with other AS esoterica that seldom impinges upon those of us who stumble around the lower foothills of the slopes of scripting's Mount Olympus.

When Paul posted a reminder of Arthur's handler previously, on Sept 18th 2002, (Re: Unicode to Plain Text) I thought it important enough to keep, but I could not possibly have known then that it would hold the key to fixing a bunch of scripts that would break in OS X 10.3 (still more than a year away) when the then current version was 10.2.1 (issued, coincidentally, on the same day as Paul's reminder).

Even when the bugs started to bite, it wasn't immediately clear that Arthur's handler contained the necessary repellant - especially when the System Events dictionary claimed that the creator type property required unicode text, and the only clue to why the script was failing was the error message that some data couln't be made into the expected type. At one point I had convinced myself that the script was failing because somewhere along the way it was converting the unicode input to, er, 'ordinary' text - I even tried to insert a routine to convert it back to unicode, which is surely a textbook example of an exercise in futility.

Is this one a bug, Chris E. ?


Regards,


Nick
_______________________________________________
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.

  • Follow-Ups:
    • Re: Stupid, Stupid Text Features [Was: Can't set creator type]
      • From: Christopher Nebel <email@hidden>
References: 
 >Re: Stupid, Stupid Text Features [Was: Can't set creator type] (From: Paul Berkowitz <email@hidden>)

  • Prev by Date: Re: Stupid, Stupid Text Features [Was: Can't set creator type]
  • Next by Date: Re: Stupid, Stupid Text Features [Was: Can't set creator type]
  • Previous by thread: Re: Stupid, Stupid Text Features [Was: Can't set creator type]
  • Next by thread: Re: Stupid, Stupid Text Features [Was: Can't set creator type]
  • Index(es):
    • Date
    • Thread