Woodpig

Apologies, Walt. It's the wrapping of the text over two lines - I want to shorten the first line, but when I try, the page number is no longer right aligned.

I'm still getting issues with this (see attached), but I assume there's been a workaround developed since this was 5 years ago. Can someone please point me to that, if it exists?

Thank you, both. That's a bit of a pain! I've just realised that I can actually change to smart quotes within Vellum, and then export a Word doc from there. I'm surprised that neither Affinity nor Mac Pages can do this.

Hi, In Affinity Publisher I've imported the text of a Word doc, and all single and double quotes are straight, not smart. When I go to find and replace, the search cannot distinguish between opening and closing quotes - so FaR will replace everything with left (or right), but not both. Is there a way around this? Thanks, Gareth.

Thanks very much, Lacerto. That's extremely useful. I'll digest your advice and get back if there are any issues. Best wishes, Gareth.

This is very useful - thank you! However, I can't see a "k-only" button - where would that be? I'm using Affinity Photo.

It's a PDF, so a mixture of fonts and raster images. The barcode is a raster image.

Thanks. Yes, I've checked with the publisher, and you're right. It's not registration black, it's K100, CMY 0. So what's the best way of achieving that? Via an adjustment layer?

Hi, I'm putting a barcode on the back of a book cover, and I need it to be registration black (CMYK - 0% CMY, 100% K!). Is it enough to add an adjustment layer (Black and white adjustment) and set all the vales to maximum negative (-200%)? Or is there a better way? THanks! Gareth.

Thank you! I knew it was there somewhere!

Hi all, Quick question. I have a page with a heading and subheading. I want both to appear in the ToC, but for there to be no page number for the subheading entry. How do I do that? Thanks! Gareth.

100% with you on that. Some of the people on the Apple support forum are quite prejudiced in Apple's favour, unsurprisingly, and some are happy to give unasked for advice on which apps I should use! It's all quite exhausting. And a disgrace, on Apple's part. I'll find a cheap Athelas clone, I think.

It certainly is! Yes, I'll explain the situation to the client and see what they want to do. I think there's probably a cheap Athelas clone out there that I can go with that will work.

Didn't work for me

Is this the copying workaround? https://www.macworld.com/article/233868/font-chaos-in-macos-catalina-and-how-to-deal-with-it.html

I absolutely agree. But Apple official support, and the people on the forum, seem to imply that it isn't. Which sucks. Yes, the Apple representatives took me through various steps to try to get it to work (before they realised that this was a deliberate "glitch"). I've tried everything. They even suggested I install OS Monterey instead of Ventura, which would be a big pain in the arse to do. My issue is that I've formatted the whole book in Athelas, and it's the first in a series of (potentially) eight! I don't feel it would be fair to go back to the client and charge them for the time to reformat using a different font, since it's my fault. And I can't charge them for the purchase of the replacement font.

They come as individual files - regular, etc. So, static, then.

I mistyped! Sorry. I meant variable.

Affinity doesn't use static, right?

Static, I believe - but (excuse my ignorance) how would I tell?

Yes and yes (with warnings concerning duplication, but after that they do work in Pages, for example).

But yes, Apple have been very disappointing in this whole affair. They've basically broken things so that there is no legal workaround (that I can see). If Affinity could see the duplicate fonts, then at least I could continue to use it.

Well, the issue is that no versions of the problematic fonts are showing up at all in the Affinity fonts list.

OK, I've been bounced around from Affinity to Apple to Adobe, and now I'm back here again. After hours on the phone to Apple support, it turns out that a group of fonts (including Athelas) has been "deprecated" in Mac Os Ventura, and that now it is only available as a document support font - meaning, it can be used to display documents already created with that font, but not to create new documents. The font continues to work with (e.g.) OS Monterey. So, essentially, Apple have restricted the licence for those fonts. Furthermore, they insist the emphasis is on third-party apps/font creators to make it work (though I don't really see how they can...). However, the issue is that, even if I try to install a commercial version of the font, it produces duplicates. Adobe Fonts won't install it at all for 3rd party apps (though it will work for Adobe CC apps). Installing the font directly from commercial vendors/font creators results in the same duplication, but it does then seem to work in Apple apps (e.g. Pages) - but still not in Affinity. Essentially, Apple are saying it's up to Affinity/Adobe/etc to get this working. I appreciate the workaround given above (using FontForge, etc), but this doesn't appear to be a legal route. So, does anyone have any other ideas?

That doesn't seem to work. Do you mean to rename the file before installing, or after installation? Neither work for me.