Sam Neil

The suggestion by Alfred makes total sense if licensing is an issue.

Chris choosing a font that is not part of the user’s computer is not expected behaviour. If that’s the case this particular message should be suppressed.

I simply installed the latest BETA and that was it. This is my whole point. If I install the software, it should assume I have the font and if I don't throw an error message and further more substitute it with another font. I did not create those assets. The machine I used had never had Affinity installed on it. So I don't think my point is very hard to understand.

I appreciate that Walt but what I am saying is why is it relying on a font that the user might or might not have installed to have to substitute for something similar?

Is this normal? Should it not install the font? Perhaps it should use the system fonts....?

It’s a 64bit only I think the installer does not detect this (yet)

I use it and swear by. Was hoping Serif would buy him out and add it to the collection. Has a mac version too but not as good as Windows.

+1

Fair point.

@MikeW & @Patrick Connor and why not? I hate to bring up the old chestnut but PagePlus has this feature and works like a charm. In fact I had to use it today. What is stopping you from adding this feature to APUB?

I am using Windows 10 (Build 17134.286)

Same here.

I believe that is coming to "New Document" as it has been mentioned. Bleed should hereditary in a document IMHO.

Yes I thought I was doing something wrong or there was a global setting I was missing. The current state is most annoying.

Yes Ditto!