Pyanepsion Posted December 11, 2022 Share Posted December 11, 2022 Beta 2.0.3.1670. I have created a page containing some Angsana fonts. This is a collection containing 8 free Microsoft fonts: AngsanaUPC in Regular, Italic, Bold, Bold Italic, and Angsana New in Regular, Italic, Bold, Bold Italic. 🟩All export formats work correctly except for some PDFs, all previews work correctly, everything works correctly on the screen, everything works correctly in printing. 🟩PDF (Flatten), PDFX (1a:2003) are correct. These two formats are hardly ever used in in the printing industry anymore. 🟥No other PDF exports are correct and they usually display one or 2 of the 4 AngsanaUPC fonts. It is therefore impossible to publish a digital or print book with an Opentype collection.  AngsanaUPC.afpub angsana.ttc 6 cœurs, 12 processus - Windows 11 pro - 4K - DirectX 12 - Suite universelle Affinity (Affinity Publisher, Affinity Designer, Affinity Photo). ███ Mais je vous le demande, peut-on imaginer une police sans sérifs ? Link to comment Share on other sites More sharing options...
walt.farrell Posted December 11, 2022 Share Posted December 11, 2022 Isn't this the same problem you've already reported against V1? If so, it probably just isn't fixed yet:  -- 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...
Pyanepsion Posted December 11, 2022 Author Share Posted December 11, 2022 It turns out that the bug has still not been completely fixed. It's a bit like building a nice car where everything works but you forgot to make the ignition key. Without usable PDFs, all the work done on the TTC is useless. This old format is now usable everywhere except in the Affinity suite. For those interested: FileFormat and Microsoft.  6 cœurs, 12 processus - Windows 11 pro - 4K - DirectX 12 - Suite universelle Affinity (Affinity Publisher, Affinity Designer, Affinity Photo). ███ Mais je vous le demande, peut-on imaginer une police sans sérifs ? Link to comment Share on other sites More sharing options...
kenmcd Posted December 11, 2022 Share Posted December 11, 2022 The issue appears to be with this particular TTC. Windows and macOS both include an increasing number of TTC files - and most appear to work as expected (now). When you posted this the 2nd time, I took a look at this. Confirmed the same problem when testing your doc. So I extracted the TTC to the separate TTF files expecting to find some sort of names issue - and found nothing wrong. Quite baffled. Other TTC files appear to be working correctly. And this TTC works correctly in other applications. So Affinity devs need to look at why this TTC does not Export to PDF correctly in APub. Link to comment Share on other sites More sharing options...
Staff Jon P Posted December 12, 2022 Staff Share Posted December 12, 2022 The bug report created from the forum thread Walt linked is still open, so it's not expected to be fixed in this beta walt.farrell 1 Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Recommended Posts