Re: Font book scripts in 10.8.x? Is this another sandboxing issue?
Re: Font book scripts in 10.8.x? Is this another sandboxing issue?
- Subject: Re: Font book scripts in 10.8.x? Is this another sandboxing issue?
- From: Alex Zavatone <email@hidden>
- Date: Thu, 22 Aug 2013 09:28:07 -0400
On Aug 22, 2013, at 7:02 AM, Nigel Garvey wrote:
>
> • The script's identical in my Mountain Lion, Leopard, and Tiger
> installations.
> • It works equally well and in the same way in both Mountain Lion and
> Leopard and so presumably in Snow Leopard and Lion too.
> • It does not select any fonts ('font families') itself. That's for the
> user to do. There'd be no point in bothering with the selection
> otherwise.
> • Any minor changes in what happens when Command-A's pressed are
> therefore irrelevant in the context of the supplied script.
> • Sandboxing is obviously off the hook too.
> • Either you're used to using a customised version of the script or the
> matter is indeed, on this list, a waste of people's time.
>
> NG
So, the reason why I reported this in the first place was that I was on a brand new Mac Mini under 10.8.3 with a fresh install of the OS.
Font Book had never been opened before since I am the only person to have booted this Mac.
I ran the script from the AppleScript menu and it reported 0 families and 0 font typefaces.
I got my MBP back yesterday and was able to boot to 10.6.8 where I ran the script and it worked fine.
Back in 10.8.3, I opened the script, the AppleScript editor complained that I did not own it so I could only open a duplicate, which I did.
Running the script, I could see that the lines of code I outlined copied the selected fonts.
It is entirely possible that this script requires the user to have previously selected the fonts they want to create a preview of within the Font Book, but there is no dialog telling the user "Please select the fonts you want to create a preview of within Font Book".
This could easily generates inconsistent behaviour. To test this, I have selected "Windows Office Compatible Fonts" in Font Book on 10.6.8 and have then quit Font Book and run the script. All installed fonts are displayed after running the script, not all of the Windows Office Compatible Fonts.
This is as expected.
The 10.8.3 Mac has been upgraded to 10.8.4. Running the script still reports 0, 0. Selecting "Windows Office Compatible Fonts" and running the script reports 0, 0. Selecting ANY FONT or all fonts from the font list in Font Book's Font pane produces the expected results.
Something changed.
Let's verify this.
On a completely different Mac, my 10.8.3 OS X Server, I just ran the script from the AppleScript menu. Result:
Font Samples - 0 families 0 typefaces.
Something changed.
I've got to put this issue to rest now. Cheers.
_______________________________________________
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