Leigh

I've not forgotten about your issue @Demys. I've been trying to replicate it, on and off, with my Synology using 2.4 & 2.4.2 and different files, but still struggling to replicate. I can see that Nathan logged a similar issue in this thread that could be related and when fixed, may resolve your issue too. Would it be possible to provide a screen recording of the process you're going through and the issue occurring? Might help us replicate - feel free to DM me with a link to a recording if you're not wanting to share it publicly. I can also provide a Dropbox link if needed to upload the files to.

I have logged your document with our developers to see if they can figure out what's causing the issue. When I have an update, I will let you know.

Pruned and locked. William has provided his feature request but as others have pointed out, it's been requested before. No need for another thread on this.

Hi @Hilltop - Just wanted to let you know that I can replicate this on Windows using both 2.4.2 and the 2.5 beta. I'm just waiting to hear back from our QA team to see if they have any idea what this issue could be or if the document needs logging with our developers. Will get back to you as soon as possible.

@Hangman I'm being lazy, so here's a link to @Lee D response in another thread that relates to this one

Sorry about this - I will get someone to look into this ASAP and get back to you with an update.

Thanks for your patience @Granddaddy you'll understand we've had a much higher volume of contacts to respond to since the announcement but to answer your question, things will remain the same i.e the forums and Technical Support will remain free.

Thank you for the PM and Link - will have a look and get back to you ASAP.

Thanks for posting and sorry for the delayed response. I think i've found the post you're referring to and you're right, there's no real outcome. So that I can look into this further and hopefully get some answers, can you send me an example Publisher document showing this on export? If you require a dropbox link, just let me know.

That's disappointing to hear. If you haven't already, can you update to 2.4 and send me a Crash Report from this version? Is it also possible to send me your Log.txt from %APPDATA%\Affinity\Publisher\2.0\

Just wanted to let you know that I've logged this with our developers.

Sorry to hear that you're having these issues when making changes. Can you check to see if you have OpenCL enabled in Edit > Settings > Performance. If you have, please disable it and try again.

Welcome to forum @Feystag - I don't have much experience with FontForge but I've just created a crude font with it and wasn't able to replicate the issue on macOS. After updating my font, exporting and importing in Font Book, it's still detected in my AFD document correctly and the characters remain. If you could provide more details of the steps you're taking or some example files we can investigate this further for you.

@NotMyFault Just wanted to let you know that we've not forgotten about this post - we're trying to get some clarification on this issue for you. When we have an update, we'll let you know.

No need to apologise