Konrad1 Posted December 11, 2023 Share Posted December 11, 2023 (edited) I'm using Affinity Publisher 2 on windows but the issue is with the entire Affinity line. I got this free font Aquire Free Font - Download Free Font (befonts.com) Inside the software the font is rendered like this But after export to pdf for example it looks like this The font renders without letter spacing in other programs as well. It's only Affinity issue. What could be the problem? Is there any setting I can change to fix this? This makes the software basically unusable because the final exported image never looks like the edited image... Edited December 11, 2023 by Konrad1 Quote Link to comment Share on other sites More sharing options...
Hangman Posted December 11, 2023 Share Posted December 11, 2023 16 minutes ago, Konrad1 said: Inside the software the font is rendered like this Hi @Konrad1 and welcome to the forums, I'm not seeing that, for me, it's renders and exports like this... are you sure you don't have any tracking applied to the text... Konrad1 1 Quote Affinity Designer 2.4.2 | Affinity Photo 2.4.2 | Affinity Publisher 2.4.2 Affinity Designer Beta 2.5.0 (2415) | Affinity Photo Beta 2.5.0 (2415) | Affinity Publisher Beta 2.5.0 (2415) Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.10.8 MacBook Pro 16GB, macOS Monterey 12.7.4, Magic Mouse Link to comment Share on other sites More sharing options...
Konrad1 Posted December 11, 2023 Author Share Posted December 11, 2023 (edited) Hi @Hangman No all font properties are set to default, are you testing this on macOS or Windows? I also found this old thread with similar issue Attached my project file. untitled.afpub Edited December 11, 2023 by Konrad1 Quote Link to comment Share on other sites More sharing options...
Hangman Posted December 11, 2023 Share Posted December 11, 2023 8 minutes ago, Konrad1 said: are you testing this on macOS or Windows? On Mac... though no obvious reason for the issue on Windows unless there is a bug lurking... Quote Affinity Designer 2.4.2 | Affinity Photo 2.4.2 | Affinity Publisher 2.4.2 Affinity Designer Beta 2.5.0 (2415) | Affinity Photo Beta 2.5.0 (2415) | Affinity Publisher Beta 2.5.0 (2415) Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.10.8 MacBook Pro 16GB, macOS Monterey 12.7.4, Magic Mouse Link to comment Share on other sites More sharing options...
Hangman Posted December 11, 2023 Share Posted December 11, 2023 So it looks like a Windows Font Rendering Issue in Publisher, opening your sample file on Mac I see this... Konrad1 1 Quote Affinity Designer 2.4.2 | Affinity Photo 2.4.2 | Affinity Publisher 2.4.2 Affinity Designer Beta 2.5.0 (2415) | Affinity Photo Beta 2.5.0 (2415) | Affinity Publisher Beta 2.5.0 (2415) Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.10.8 MacBook Pro 16GB, macOS Monterey 12.7.4, Magic Mouse Link to comment Share on other sites More sharing options...
Konrad1 Posted December 11, 2023 Author Share Posted December 11, 2023 That's sad news. I wonder if there's any fix for this Quote Link to comment Share on other sites More sharing options...
Hangman Posted December 11, 2023 Share Posted December 11, 2023 3 minutes ago, Konrad1 said: That's sad news. I wonder if there's any fix for this Well, it's been logged as a bug (AFB-4986) in the thread you linked to so hopefully, it's being looked at with a view to finding a resolution. Konrad1 1 Quote Affinity Designer 2.4.2 | Affinity Photo 2.4.2 | Affinity Publisher 2.4.2 Affinity Designer Beta 2.5.0 (2415) | Affinity Photo Beta 2.5.0 (2415) | Affinity Publisher Beta 2.5.0 (2415) Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.10.8 MacBook Pro 16GB, macOS Monterey 12.7.4, Magic Mouse Link to comment Share on other sites More sharing options...
Konrad1 Posted December 11, 2023 Author Share Posted December 11, 2023 (edited) Most likely this won't be fixed pretty soon. If not for this issue everything would be perfect 🙁 It's not only in Publisher but other tools as well Edited December 11, 2023 by Konrad1 Quote Link to comment Share on other sites More sharing options...
kenmcd Posted December 11, 2023 Share Posted December 11, 2023 @Konrad1 The problem is the Aquire font. Wadda mess. Multi-mapping is when a glyph is mapped to more than one Unicode code point. This can quite often cause problems for applications with those fonts. Adobe strongly recommends against multi-mapping. Google Fonts does not allow multi-mapping at all in their fonts. It is a dumb idea to do it. It appears this free version of the font was created by deleting the extended glyphs, and then multi-mapping the deleted glyphs code points to the base glyph. For example the capital A glyph has 14 code points mapped to it. That is beyond stupid. And it uses ranges of code points in addition to single code points. Many applications will choke on that. This "free" font is basically unusable. It may work in some situations, but not cross-platform, and not in many applications. Could not find the commercial version to take a look at it and see if it too is a mess, but, regardless, I would not trust anything made by this "font designer." MikeW, Old Bruce, Hangman and 2 others 4 1 Quote Link to comment Share on other sites More sharing options...
Konrad1 Posted December 11, 2023 Author Share Posted December 11, 2023 (edited) 1 hour ago, kenmcd said: @Konrad1 The problem is the font. Wadda mess. Multi-mapping is when a glyph is mapped to more than one Unicode code point. This can quite often cause problems for applications with those fonts. Adobe strongly recommends against multi-mapping (and is not used in their fonts). Google Fonts does not allow multi-mapping at all in their fonts. It is a dumb idea to do it. It appears this free version of the font was created by deleting the extended glyphs, and then multi-mapping the deleted glyphs' code points to the base glyph. For example the capital A has 14 code points mapped to it. The .notdef glyph has multiple code points mapped to it! That is beyond stupid. This "free" font is basically unusable. It may work in some situations, but not cross-platform, and not in many applications. Could not find the commercial version to take a look at it and see if it too is a mess, but, regardless, I would not trust anything made this "font designer." Understandable. But then why other applications render it correctly? Why does macOS render it differently than windows? Should be consistent. Edited December 11, 2023 by Konrad1 Quote Link to comment Share on other sites More sharing options...
kenmcd Posted December 11, 2023 Share Posted December 11, 2023 From within the font... Versions String: Version 1.024;Fontself Maker 3.5.0 The good thing about Fontself Maker is anybody can make a font. The bad thing about Fontself Maker is anybody can make a font. Multi-mapping is a bad practice that experienced font developers avoid. There is a reason Adobe is against it and Google Fonts does not allow it. You will not find any multi-mapped glyphs in Monotype's Helvetica Now. Because support is spotty in OSs, text shapers, PDF libraries, and applications. Given that the developer used Fontself Maker means they are on a Mac. And that particular combination of OS and text shaper (Coretext) happened to work. Doubtful they tested anywhere else. I did not examine this closely enough to determine exactly what is causing Affinity problems - but my guess is the ridiculous level of multi-mapping, and including ranges, is confusing Affinity. Regardless this font is junk. I have a pet peeve against purposely broken "free" fonts. Think it is a very sleazy practice. All the characters with diacritics which were there are now mapped to just the base. Be honest. Just make a limited version and let users know it is limited. Don't mislead and confuse them by mapping all the characters they actually need for anything other than English to just the plain base character. And the curly left/right single and double quotes are mapped to the plain versions. I assume there were actual left/right versions. Sleazy. If you just gotta have this font, you can edit it and remove all the multi-mapping, and also remove the unneeded old control characters - and then it may work properly in Affinity. So if you only need Basic Latin uppercase, and some of the normal punctuation, that may be a good option. Could also take a shot and buy the commercial version. May work. Old Bruce, Konrad1, Horizon3 and 1 other 2 2 Quote Link to comment Share on other sites More sharing options...
Horizon3 Posted January 8 Share Posted January 8 @kenmcd thanks for such good information. How to know if free font has this multi-mapping please? Same problem I am having with this Endless Sorrow Free font. Font Is okay and render fine inside Apub on Windows but when export it look like this Is suppose look like this Quote Link to comment Share on other sites More sharing options...
kenmcd Posted January 8 Share Posted January 8 12 hours ago, Horizon3 said: Font Is okay and render fine inside Apub on Windows but when export it look like this Looks like an issue with the names inside the font files (not multi-mapping). The names inside the fonts are kind of a mess which can confuse the APub font cache and/or the PDF library. One font alone may work - so shut-down APub and un-install the Catchwords font. The Regular font alone may work correctly. (and I assume you know you cannot install both the OTF and TTF versions at the same time) So test that font alone and if it works then my theory is probably correct. Would take about five minutes to fix the fonts so both will work at the same time, so let me know. Horizon3 1 Quote Link to comment Share on other sites More sharing options...
Horizon3 Posted January 8 Share Posted January 8 Quote and I assume you know you cannot install both the OTF and TTF versions at the same time No, thank you very much. No, not know this. Maybe explain why Endless free font is not render correcting when exported. Just now I do what you suggesting and waiting five minutes. Still font is smash together. Maybe I try uninstall all fonts (regular and catchwords) and see if this work. I come back and tell to you what happen. kenmcd 1 Quote Link to comment Share on other sites More sharing options...
Horizon3 Posted January 8 Share Posted January 8 @kenmcd Again thanking you very much for the help you give. Font is now rendering correct. It was as you say I had install both OTF and TTF versions at same time. I uninstall both and put only TTF and font renders correct now. kenmcd 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.