Re: Keychain Leopard->Tiger broken (unicode related?)
Re: Keychain Leopard->Tiger broken (unicode related?)
- Subject: Re: Keychain Leopard->Tiger broken (unicode related?)
- From: Loren Ryter <email@hidden>
- Date: Fri, 16 Nov 2007 16:13:28 -0500
- Thread-topic: Keychain Leopard->Tiger broken (unicode related?)
On 11/16/07 3:44 PM, "Christopher Nebel" <email@hidden> wrote:
> If your guess is correct -- and it's a pretty good one -- then an
> explicit "as string" would solve it:
>
> set thekey to "some_existing_generic_key_name" as string
>
> In Tiger, that will coerce the text constant (which is actually a
> "Unicode text" object) to the old-style "string" object that Tiger
> Keychain Scripting apparently wants. In Leopard, the "as string" does
> nothing, but Leopard Keychain Scripting is apparently ok with that.
>
>
> --Chris Nebel
> AppleScript Engineering
>
Chris,
Nope, unfortunately that does not work. That was one of the first things I
tried. "as string" compiled on Leopard stays as unicode apparently -- at
least as far as I can figure. But perhaps that is not it. Possibly
declaring the text "as string" outside or inside the "keychain access" tell
block might make a difference, which I will try.
But I can forsee this unicode only thing in Leopard is going to create big
backward compatibility problems. Can't Leopard do better to support
explicit "as string" declarations and stay that way even when compiled?
Thanks.
Loren
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden