AlainP Posted December 11, 2020 Share Posted December 11, 2020 I just noticed that some PDF files opened in Publisher (exactly the same behavior in Photo and Designer) display the wrong characters. Here is the original text in the PDF file: Les moteurs et actionneurs OKIN de technologie allemande procurent performance, fiabilité et un fonctionnement silencieux. And here is what is displayed in Affinity apps when opened: Les moteurs et acÃonneurs OKIN de technologie allemande procurent performance, fiabilité et un foncÃonnement silencieux. As you can see, all occurences of the "ti" are changed to "Ã". This is all over the document. This text uses Calibri font with nothing special. I edited the text to get the correct spelling in Publisher and Designer, exported the files as PDF. When I open them back I always get the replacement. This is with beta and release version of all Affinity apps. This is a normal font and I don't get any warning when I open the files. I created new files and exported to PDF and I don't get this problem. I think the problems occurs with files created with the 1.7 version of Designer. -- Window 11 - 32 gb - Intel I7 - 8700 - NVIDIA GeForce GTX 1060 -- iPad Pro 2020 - 12,9 - 256 gb - Apple Pencil 2 -- iPad 9th gen 256 gb - Apple Pencil 1 -- Macbook Air 15" - Mac mini M2-Pro - 16 gb Link to comment Share on other sites More sharing options...
walt.farrell Posted December 11, 2020 Share Posted December 11, 2020 4 minutes ago, AlainP said: This text uses Calibri font with nothing special. I edited the text to get the correct spelling in Publisher and Designer, exported the files as PDF. When I open them back I always get the replacement. If the PDF files are always ones created in Affinity, then this seems to happen based on the Export settings. During Export, if you press More... one of the options near the bottom is "Embed Fonts". It has a suboption of "Subset Fonts", which is the default. If you have Ligatures enabled (also a default), and you let Affinity subset the embedded fonts, then when Affinity loads the PDF again the ligatures are messed up. If you turn off the Subset Fonts option that is usually fixed, from what I've seen here in the forums. Or you could disable the use of ligatures for your text before exporting. I'm not sure if this is on file with Serif as a bug. -- 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...
AlainP Posted December 11, 2020 Author Share Posted December 11, 2020 Unchecking "Subset fonts" makes it work fine ! Thanks Walt. walt.farrell 1 -- Window 11 - 32 gb - Intel I7 - 8700 - NVIDIA GeForce GTX 1060 -- iPad Pro 2020 - 12,9 - 256 gb - Apple Pencil 2 -- iPad 9th gen 256 gb - Apple Pencil 1 -- Macbook Air 15" - Mac mini M2-Pro - 16 gb Link to comment Share on other sites More sharing options...
Alfred Posted December 11, 2020 Share Posted December 11, 2020 56 minutes ago, walt.farrell said: I'm not sure if this is on file with Serif as a bug. If it isn’t, it should be! For a document with ligatures (or other OpenType features such as Contextual Alternates) enabled, the embedded subset needs to include the extra glyphs that allow those characters to be displayed correctly. walt.farrell 1 Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen) Link to comment Share on other sites More sharing options...
walt.farrell Posted December 11, 2020 Share Posted December 11, 2020 17 minutes ago, Alfred said: If it isn’t, it should be! For a document with ligatures (or other OpenType features such as Contextual Alternates) enabled, the embedded subset needs to include the extra glyphs that allow those characters to be displayed correctly. After some more research, I think it has been logged: AlainP and Alfred 2 -- 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...
Recommended Posts