tmwhale Posted January 8, 2021 Share Posted January 8, 2021 Hello! Affinity Publisher Preflight is reporting missing font but Font Manager is Reporting OK or not displaying Status. Font's look bad when exporting. Font is installed. How can this be resolved? I appreciate the help. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 8, 2021 Share Posted January 8, 2021 If you have any embedded or linked PDF files in your document, possibly the fonts it's complaining about are in them? Also, I'm not sure that "Franklin Gothic Demi" and "FranklinGothicDemi" are the same font. The naming may require an exact match. tmwhale and Old Bruce 2 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
Old Bruce Posted January 8, 2021 Share Posted January 8, 2021 Just now, walt.farrell said: If you have any embedded or linked PDF files in your document, possibly the fonts it's complaining about are in them? Also, I'm not sure that "Franklin Gothic Demi" and "FranklinGothicDemi" are the same font. The naming may require an exact match. The names can be exactly the same in the font lists and still be two separate fonts. The names presented in the lists are rarely the actual font name that the OS and Applications use to find the font and store in the document. walt.farrell 1 Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
tmwhale Posted January 8, 2021 Author Share Posted January 8, 2021 Thank you both. Check this out. The problem is with the embedded files. The one on the left is Bluebeam viewing the export from Revit (my drawing program), the right is the embedded pdf in Publisher. Any ideas on how to resolve this? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 8, 2021 Share Posted January 8, 2021 Until 1.9 (currently only available in beta testing) Affinity must interpret any Placed PDF files, and it cannot make use of any embedded font information in the PDF. That means that you need to have the exact fonts installed on your system that the PDF uses, by the exact names that Affinity expects them to have. It seems from those screenshots that you do not have the right fonts installed, at least as Affinity expects them to be named. In 1.9 that will be resolved by allowing you to Place the PDF file in PassThrough mode, where no interpretation takes place, and the PDF should look and act exactly as you would want it to. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
tmwhale Posted January 9, 2021 Author Share Posted January 9, 2021 Thanks Walt, I don't think I'm knowledgeable enough to resolve the naming issue. I created the pdfs in Revit on the same machine and I have the fonts in windows. I don't know how to verify what Publisher is looking for. I may do a work around exporting my pdfs as images until 1.9 arrives. Any ideas when 1.9 will be released? I appreciate the guidance you've provided. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 9, 2021 Share Posted January 9, 2021 You're welcome. No one who knows anything about the release date will say anything, so it could be soon, or a few months. Serif generally just says "when it's ready". Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
kenmcd Posted January 26, 2021 Share Posted January 26, 2021 Some PDF creation software embeds the fonts with non-standard names ... names which often do not match the PostScript Name field in the font as it should. Commas in the font name are a dead giveaway. And no dashes is also a sign. In your image in the first post I can see the names of the "missing" fonts are the problem. Arial,Bold should be Arial-Bold FranklinGothicBook should be FranklinGothic-Book etc. ... Then the PostScript Name would match your installed fonts, and there would be no "missing" fonts. Adopy apps are smart enough to know these should match, and that just because some PDF creators are stupid, users should not have to suffer. For the 3rd or 4th time ... Affinity apps should know that Arial,Bold = Arial-Bold and make the font match. 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.