Mike Muszynski

I can confirm that this is still happening on the Sonoma release. The same issue just now when I exported the file using Publisher version 2.1.1. EDIT: I spoke too soon, because the issue is fixed after updating to 2.2.0. Thanks everybody, we can close this thread now!

Correct, this part. I am in Monterey 12.6 on my second computer, and it's exporting fine there. It's just the Sonoma beta that isn't working, so I'll see if maybe something gets fixed once the final version is out. Weird that it is only happening in TNR, but my Font Book looks the same as yours. I'll keep an eye on it as Sonoma goes master.

This seems to not be a problem on Publisher v2.1.1 on earlier versions of macOS. I just successfully exported the PDF on macOS 12.

I have a problem that I haven't seen before. When trying to output the attached document, the italicized title "Senza Sordino" comes out with the wrong font (see the PDF version with [BUG] in the title). I have attempted to embed the font, and have played around with other settings down there, but so far nothing works besides converting the fonts into curves. This appears to make the text not selectable, so it's definitely not a preferred solution. Is there anything else I could be trying? I am using a 2023 M2 Pro Macbook Pro running the latest macOS Sonoma Beta 7. Is this reproducible elsewhere? 20230829 Press Release Governing Board Election.afpub 20230829 Press Release Governing Board Election [BUG].pdf

They do not display. They are marked as missing and I am required to choose a replacement font. Agreed, I will complain with Apple next.

Because the font does show up in other apps, including Apple provided ones. And from the topic above, these apparently are document-support fonts, so they are supposed to be available if they are used in the document, which they are.

I have had a small amount of success downloading FontForge and creating a NEW font out of Athelas, with the only change being to call it Athelas 2020. For some reason, it still shows up as Athelas in the font menu, but it's missing in the font manager in Publisher and can be replaced by... Athelas. This whole thing is just bizarre.

Unfortunately, the procedure linked in this thread no longer works in Ventura, as the location that files must be deleted from is a "read-only filesystem."

This is exactly what it looks like.

I'm not sure what I'm supposed to do with them once they are in Typeface. They still don't show up in either Font Book or the Affinity suite apps. Progress: if I unpack the ttc and install the ttf files separately, they are recognized in Font Book and other apps, just not Affinity suite.

Athelas and its four variants. Book Antiqua. Times. I suppose it is only 6 fonts.

Many times. I have tried removing the font cache and then restarting. I have tried moving the fonts to different places and then restarting. Beyond Font Book, no.

Gabe, Sent a ttc that had previously worked and also the four ttf that also do not work. MM

No change after deleting the font cache. Affinity is still the only suite that has this issue.

Okay, thanks. I should have asked a better question, like delete them from macOS or from Affinity. I'll have a look and report back.

How? I couldn't find a good answer googling that earlier.

Three font families, and a total of 7 fonts. The rest are still there.

That's where the Font Manager installed them.

Affinity Publisher 2 (and 1) and the rest of the Affinity suite are not loading fonts that are installed in ~/Library/Fonts after upgrading to macOS 13.0 (Ventura). This has caused Publisher to report that there are essential fonts missing from documents. These fonts were unavailable across the os after upgrading, but upon reinstalling, they are available to other apps, just not Affinity apps. Please advise if there is more information necessary to help resolve this issue.

100%, this is a necessary feature.