Matthew Dickerson Posted November 17, 2022 Posted November 17, 2022 PDFs are showing the wrong glyphs for certain fonts when exported - In my case FontAwesome 6 Glyphs were wrong, also other fonts I had used. Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
kenmcd Posted November 17, 2022 Posted November 17, 2022 It would be helpful to examine the PDF to see what actually got embedded. So please attach it if you can. Or at least a page. It would be helpful to examine the original document, so please attach if you can. Which fonts specifically? Quote
Matthew Dickerson Posted November 19, 2022 Author Posted November 19, 2022 On 11/17/2022 at 2:54 PM, kenmcd said: It would be helpful to examine the PDF to see what actually got embedded. So please attach it if you can. Or at least a page. It would be helpful to examine the original document, so please attach if you can. Which fonts specifically? Hi, Ive Attached a pdf and a png.. the png shows the correct glyphs and exports correctly.. Bug.pdf Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
MikeTO Posted November 19, 2022 Posted November 19, 2022 The font FontAwesome 6 is not embedded in the PDF. At the bottom of the Export window is an option to embed fonts. What do you have it set to? Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.3, MacBook Pro (M4 Pro) and iPad Air (M2)
kenmcd Posted November 19, 2022 Posted November 19, 2022 2 hours ago, MDI said: Hi, Ive Attached a pdf and a png.. the png shows the correct glyphs and exports correctly.. Need to see the original document. How did you enter these characters? The codes behind the characters are odd. So there is definitely an issue here. I can see sub-sets of both FontAwesome6Brands-Regular and FontAwesome6Free-Solid embedded for that one line. What version of FontAwesome Free do you have? v6.2.1 came out a few days ago (2022-11-10). What language is assigned to the text? The Inter sample text looks odd. Please attach the document you used to create this PDF. Quote
MikeTO Posted November 19, 2022 Posted November 19, 2022 Oh I didn't check for subset. Agree, need to see the original document. kenmcd 1 Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.3, MacBook Pro (M4 Pro) and iPad Air (M2)
Matthew Dickerson Posted November 19, 2022 Author Posted November 19, 2022 'Sorry, an unknown server error occurred when uploading this file. (Error code: -200) ' - I get this message when trying to uplaod .apub file to this thread.. Here's a .zip file instead Bug.zip Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
Matthew Dickerson Posted November 19, 2022 Author Posted November 19, 2022 I enetered the characters by double clicking on the ones I wanted from the gylph browser Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
Matthew Dickerson Posted November 19, 2022 Author Posted November 19, 2022 Also exporting is fine in V1 definitely a V2 bug.. kenmcd 1 Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
kenmcd Posted November 19, 2022 Posted November 19, 2022 Can you please attach the v1 PDF? This is definitely a bug. Need to do some more testing to see what is going on, but the fonts have a lot of multi-mapped characters, and it appears the PDF library has an issue with this. Like to see the v1 PDF to see the codes behind the characters in it. There may be a work-around that we can test. The multi-mapped characters appear to all have at least one of the codes up in PUA (Private Use Area). So maybe by restricting the Glyph Browser to the Private Use Area (instead of All) the codes embedded will all be in the PUA, and may work. Have to test this theory (or WAG). But that still does not explain the odd Inter text. Gotta go at the moment, but will be back to look at this in a couple hours. Quote
Matthew Dickerson Posted November 19, 2022 Author Posted November 19, 2022 5 minutes ago, kenmcd said: There may be a work-around that we can test. The multi-mapped characters appear to all have at least one of the codes up in PUA (Private Use Area). So maybe by restricting the Glyph Browser to the Private Use Area (instead of All) the codes embedded will all be in the PUA, and may work. Have to test this theory (or WAG). Lol I have no idea what this means but it sounds like you know what to do Here is a pdf from V1 displaying correctly. V1.pdf Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
kenmcd Posted November 19, 2022 Posted November 19, 2022 And the plot thickens... When I do Export to PDF in APub2 on Win10 it looks as expected. And it looks just like your v1 PDF. And the encoding errors on the characters in the PDF are the same in both. The glyphs (shapes) are correct, but the character codes behind them are wrong. Your v2 PDF has different encoding errors, and wrong glyphs (shapes) embedded. So something has changed on the Mac. And apparently it is a new-improved version of the encoding bugs. 😁 Your v2 PDF Inter font text errors are also encoding bugs. Which is quite alarming as Inter is not at all like Font Awesome internally. Regarding the Private Use Area in Glyphs Browser - first open the hamburger menu at top right and select Unicode - then in the drop-down list which initially says "All" select Private Use Area. Then use that to insert the characters. May work, may not. Actually, now that I think about it, doubtful. Those characters are still multi-mapped (more than one Unicode code point). While there are encoding errors on Windows too (which should also be fixed). Something is really wrong on the Mac. We need someone from Affinity to have their devs check this. EDIT: What version of macOS are you using? Matthew Dickerson 1 Quote
Matthew Dickerson Posted November 19, 2022 Author Posted November 19, 2022 15 minutes ago, kenmcd said: And the plot thickens... When I do Export to PDF in APub2 on Win10 it looks as expected. And it looks just like your v1 PDF. And the encoding errors on the characters in the PDF are the same in both. The glyphs (shapes) are correct, but the character codes behind them are wrong. Your v2 PDF has different encoding errors, and wrong glyphs (shapes) embedded. So something has changed on the Mac. And apparently it is a new-improved version of the encoding bugs. 😁 Your v2 PDF Inter font text errors are also encoding bugs. Which is quite alarming as Inter is not at all like Font Awesome internally. Regarding the Private Use Area in Glyphs Browser - first open the hamburger menu at top right and select Unicode - then in the drop-down list which initially says "All" select Private Use Area. Then use that to insert the characters. May work, may not. Actually, now that I think about it, doubtful. Those characters are still multi-mapped (more than one Unicode code point). While there are encoding errors on Windows too (which should also be fixed). Something is really wrong on the Mac. We need someone from Affinity to have their devs check this. EDIT: What version of macOS are you using? Ahh.. yikes, well thanks for investigating for me! hopefully the devs can fix it soon I'm using macOS Monterey 12.6.1 kenmcd 1 Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
kenmcd Posted November 19, 2022 Posted November 19, 2022 @Matthew Dickerson Was thinking about this ... Font Awesome is actually designed as a bunch of ligatures. You type the text and the ligature code converts it to an icon. I did some quick tests and that is working here in APub2 on Windows 10. So give that a try. The ligature words are available on the website. Free + Brands filters on:https://fontawesome.com/search?o=a&m=free&f=brands Set the font, type the text - and it will display the icon. Now will the Export to PDF of the ligatures work on Mac? Please test and let us know how it goes. Quote
Matthew Dickerson Posted November 21, 2022 Author Posted November 21, 2022 On 11/19/2022 at 9:54 PM, kenmcd said: @Matthew Dickerson Was thinking about this ... Font Awesome is actually designed as a bunch of ligatures. You type the text and the ligature code converts it to an icon. I did some quick tests and that is working here in APub2 on Windows 10. So give that a try. The ligature words are available on the website. Free + Brands filters on:https://fontawesome.com/search?o=a&m=free&f=brands Set the font, type the text - and it will display the icon. Now will the Export to PDF of the ligatures work on Mac? Please test and let us know how it goes. I gave this a try and it did not work, possibly just a mac problem, also searching for glyphs with Unicode does not work on both v1 and v2, I never noticed before because I don't use the search feature for glyphs.. Quote Artstation - https://www.artstation.com/matthew-dickerson Website - https://matthewdickerson.art/
kenmcd Posted November 21, 2022 Posted November 21, 2022 The issue with the Inter font text may be caused by a font cache corruption. Shut down all Affinity applications and clear the macOS font cache. When you restart the Affinity applications they should also rebuild their font cache. Then try Export to PDF again with your doc above. Quote
kenmcd Posted November 22, 2022 Posted November 22, 2022 10 hours ago, Matthew Dickerson said: I gave this a try and it did not work, possibly just a mac problem, also searching for glyphs with Unicode does not work on both v1 and v2, I never noticed before because I don't use the search feature for glyphs.. I have found on Win10 that the search does work, but it does not always bring the result into view. If I go scrolling down, I can eventually find the highlighted glyph/character. Definitely not working as it should. Another bug. Quote
Staff Pauls Posted November 30, 2022 Staff Posted November 30, 2022 I've tried this using a fresh install of FontAwesome and the export is working fine for me. The fault does look like a duplicate font is installed or a font cache issue (although we usually see those on Windows). I've logged an issue regarding some differences I see in the glyph browser compared to Indesign Quote
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.