I've created a font family, but Font Book refuses to include it in the English language set, despite my best efforts. The font has every glyph in the OpenType "Std" set, plus several others. I've checked various boxes for Latin 1 and Macintosh Character Codepages; plus Unicode ranges for Basic Latin, additional Latin, etc, etc. I've compared it to several other fonts that are in the English set, and I can't see anything that they have that my fonts don't. (In fact, many of them seem to have much less!) I've created other fonts that are in the English set, but I've no idea what the difference is. Given that macOS relies on these Language sets, in order to hide the thousands of unnecessary fonts that are permanently installed in the OS, there ought to be some guidance on how to do this.

I'm a font developer. In the development process, I will revise a font and overwrite the OTF file that is currently enabled (registered) with macOS. If I then launch an app, it will immediately use the revised version of the font; while apps that are already loaded will continue to use the old version. This suggests that each app is loading new and separate font data, rather than getting it from some existing cache in memory. Yet macOS does have a "font cache" of some sort. Some apps, like TextEdit, seem to only load the fonts that they need to use. However, other apps, like Pages, load every enabled (registered) font on the OS!! (According to the Open Files list in Activity Monitor.) Given that /System/Library/Fonts/ is 625 Mb, and we can't disable any of it, isn't that a lot of data to be repeating? How many fonts is too many fonts? I can't find much documentation about the process.

I see that pstopdf and the PSNormalizer framework have been removed from Sonoma. A sad day, given the importance of PostScript in making the Mac a success.

I have a MacOS app with a memory leak. According to the Leaks.app, there's a problem with NSIdleTimer's setHandler method. I'm not using that object (which I can't find any documentation on). But I am using: sleep(1) as a means of preventing a race condition. Might that be the cause? Anything I need to do with sleep to deallocate memory? Or is it an OS bug?

I'm trying to create a Command Line Tool that uses the ArgumentParser swift package. I've added the package to my project, and initially I got a lot of errors: Library not loaded (code signature in PackageFrameworks/ArgumentParser.framework/Versions/A/ArgumentParser' not valid for use in process: (no such file, not in dyld cache) I fixed it by disabling Library Validation in the Build Options, and my tool runs in Xcode beautifully. But the compiled executable won't work in Terminal, flagging the same errors. I presume it's some signing/security thing (as usual), and I just need to set the right Build Options, but I haven't a clue which ones. I tried "Always Embed Swift Libraries", but that produced a warning message: the product type 'com.apple.product-type.tool' is not a wrapper type. Anyone know what might be going on?

I'm trying to create a custom Quick Look preview on macOS. I've found the Quick Look Preview Extension target, which is brilliant, and does most of the 'heavy' lifting, but I've run into a few problems. I'm implementing a preview for MIDI files (which has been missing since 2009...) using AVMIDIPlayer. The player keeps playing when the file is no longer selected! What's the mechanism for fixing that? Some sort of check that the view exists..? I notice that the OS preview for audio files has a different interface for the Finder's preview column and for the QuickLook 'pop-up' window. Again, I can't see how you define different views for those two environments. Is there any documentation that's specifically "Mac"? I can only find iOS stuff. (Same for third-party tutorials.)

I've added a new target to my macOS project -- a quicklook preview extension. Now, when I try to build the project, I get a dialog saying "Select App to Run". QuickLook Simulator launches, but my app doesn't build -- by which I mean it doesn't attempt to build. What do I have to do to build the whole thing?

I have a real problem trying to get to grips with the whole Optionals/wrapping thing, and associated type issues. Here's my code: import Quartz import Foundation func listFilters() -> Void { let theFilters = QuartzFilterManager.filters(inDomains: nil)! for eachFilter in theFilters as! [QuartzFilter] { print(eachFilter.localizedName()!, ":", eachFilter.url().path) } } listFilters() So, in the first line of the function, I have to explicitly force unwrap the result of the method that returns a list of QuartzFilters. (Why?) The very next line, I have to force them to be of type QuartzFilters, (because why wouldn't the method return the actual type of thing that they are?) And then on the third line, I still have to force unwrap one of the properties of something that I've already unwrapped (otherwise I get optionals), but not the other one. Yes, I understand it's all about trying to prevent a null condition, but nearly everything is never null. Even if I use if let on the first line, I'm still unwrapping stuff inside that if.

Apple seems to have archived its documentation for making PKG packages, and PackageMaker hasn't been seen since 2012. Are packages deprecated, or are there new ways for creating them?

Now that CUPS backends, filters and PPDs are deprecated, I'm trying to set up a print to file queue using ippeveprinter. But I can't get it to work. Anyone know anything about it? I've tried: ippeveprinter -D file:///Users/Shared/Print/Out -F application/pdf -c /usr/local/bin/pscommand.sh myprinter and then created a shell command that runs: cupsfilter $1 I've tried it without the -c flag as well. Sometimes I've produced .prn files, and occasionally .urf files (but without changing anything I've also got zero length files). But I just can't get a PDF into my destination folder.

Since Big Sur, the printtool process has been sandboxed, with the result that it's now so secure, it can't do anything. As a consequence, PDF Services (items in ~/Library/PDF Services) no longer work. An alias to a folder outside the user domain, such as /Users/Shared/, no longer saves the PDF file to that location. Shell scripts, python, and even compiled Swift binaries no long run. Even Automator Print plug-ins no longer function. Adding printtool to Full Disk Access doesn't work either. ("If in doubt, add the process to Full Disk Access.") The ability to process PDFs directly from the print dialog goes back to Tiger (I think) and has been massively useful for years. Yes, I suppose some malware could save a script to the user PDF Services folder, and then some unwitting user could run it from the print dialog, but.... At the very least, some new documentation about how PDF Services are now supposed to work would be crucial.

Pages, Numbers, KeyNote use a sheet dialog for choosing options when exporting graphics. Is that using a public API, or is it just a bit of bespoke code? I notice a few other apps having similar sheets.

I want to create an application that does nothing, except 'hand-over' to another application. So double-clicking on the app launches another app; and double-clicking on the app's files opens them in the other app. Why? Because I want to set custom file icons to a particular file type. So I'm using a dummy app as the 'default' app for the file type, before handing to the real app. In Mojave, I can do this: create a boilerplate application in Xcode, add the document type and icons; then switch out the app's binary for a hard link to the binary of the app I want. However, this doesn't work on Catalina , for 'security reasons'. <rolls eyes> I even tried re-signing my app with the hard link in the bundle, but that still doesn't work. The app just crashes on launch. Is there another way that I can do this? Or are such things forbidden? I've tried creating an Automator or AppleScript application that just opens the target app, passing the documents to it, but I can't work out how to modify the Info.plist without getting a 'No Entry' sign on the app. PS: How do you browse through these forums? I'll be amazed if anyone reads this.

Apple's documentation on creating Application Extensions shows Xcode offering project templates for Application Extensions. https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/ExtensionCreation.htmlThese no longer seem to be in Xcode when I start a new project. Has Apple moved the goalposts again, or is there a place where I can download a template?Thanks

It seems that the PDFAnnotation classes have all been deprecated, and that we're now supposed to use PDFAnnotationSubtype instead.Any documentation on how? ..... tumbleweed ....