Nordseher Posted October 15, 2019 Share Posted October 15, 2019 In the moment I add the following graphic, PDF Export failed. I got a message: Fehler beim Export in <filename> The Export of the pdf is given by my Online - printer - service Could you help me please? I have embedded the image file Fehler.afpub Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted October 15, 2019 Staff Share Posted October 15, 2019 This file exports fine for me. What export settings are you using? I am missing 4-5 of the fonts used in this document that might also be the cause, I've installed the Chaparral Pro font from Adobe, but can you upload your versions of the "Futura Regular", "RotisSandSerif Bold" and "Times" font here Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Nordseher Posted October 16, 2019 Author Share Posted October 16, 2019 As far as I understand you can export the file, is that right? I have further reduced the file to 1 page, the error remains while exporting. If I change the export settings "Compatibility" to "PDF/X4" I can export the file. Then everything works. When I go back to the recommendation of my online printer "PDF/X3:2003" the same error happens reproducibly over and over again. I uploaded the Font files too but in my document just now there is no text kind regars Ingo Jakubke# Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted October 16, 2019 Staff Share Posted October 16, 2019 Thanks, I think this is because (and correct me if i'm wrong) you have set Rasterize set to Nothing in export options. This is tripping up a PDF X-3 export with your file because it has to Rasterize the filter effects on the image in the file you provided, X-3 doesn't support live transparency so it can't export it without rasterizing it. We should handle this scenario a bit better (like just not export the filter effects if you've explicity stated for it to not rasterize), so I'll log this, but you'll need to leave the Rastersize settings to "Unsupported Properties" to get an export out. I edited your post to remove the fonts, since some were protected fonts and shouldn't be on a public forum Nordseher 1 Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Nordseher Posted October 17, 2019 Author Share Posted October 17, 2019 On 10/16/2019 at 12:01 PM, Jon P said: Thanks, I think this is because (and correct me if i'm wrong) you have set Rasterize set to Nothing in export options. This is tripping up a PDF X-3 export with your file because it has to Rasterize the filter effects on the image in the file you provided, X-3 doesn't support live transparency so it can't export it without rasterizing it. We should handle this scenario a bit better (like just not export the filter effects if you've explicity stated for it to not rasterize), so I'll log this, but you'll need to leave the Rastersize settings to "Unsupported Properties" to get an export out. I edited your post to remove the fonts, since some were protected fonts and shouldn't be on a public forum Yes, that's correct. Your assumption is correct. I strictly followed the printer's guidelines and even received a sample Affinity Publisher document from the printer which exactly had the export settings. However, not a single "raster effect" had been used in the document. I did the crosscheck and copied my graphic into this document and then I had the same error as with my document. It's solely due to the setting for rasterizing "unsupported properties". The error message that comes up doesn't really help. It would be useful to specify the page number in the output. The same applies to the warning: There is an overflow text in the document. The reference to the page number is also missing here. That would be nice. Otherwise I have now understood when a graphic must be rasterized and how this affects the PDF export. I think the idea to solve it differently is good. If a raster effect is necessary for the output, a hint would be useful. I don't think simply suppressing the raster effects is the right way to go. Many thanks Ingo Jakubke Translated with www.DeepL.com/Translator Jon P 1 Quote Link to comment Share on other sites More sharing options...
Eric Louw Posted November 7, 2019 Share Posted November 7, 2019 (edited) I had the exact same issue with the export failing when rasterize was set to "unsupported properties" for my most recent design. Quite frustrating until I was able to switch it to rasterize all or none. The issue appears to be caused when I have font embedding on and vanishes when I convert fonts to curves. Edited November 7, 2019 by Eric Louw Quote Link to comment Share on other sites More sharing options...
ricoho Posted November 7, 2019 Share Posted November 7, 2019 7 hours ago, Eric Louw said: I had the exact same issue with the export failing when rasterize was set to "unsupported properties" for my most recent design. Quite frustrating until I was able to switch it to rasterize all or none. The issue appears to be caused when I have font embedding on and vanishes when I convert fonts to curves. I have the same problem with some documents. Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 7, 2019 Staff Share Posted November 7, 2019 @Eric Louw It may have been trying to embed a protected font at a guess, could be another reason though If both of you want to upload the documents and let me know what export settings you are using I can make sure it is included in the above bug report, we are working on giving better feedback with these sorts of errors. If you want to keep the documents private use this link Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Eric Louw Posted November 8, 2019 Share Posted November 8, 2019 9 hours ago, Jon P said: @Eric Louw It may have been trying to embed a protected font at a guess, could be another reason though If both of you want to upload the documents and let me know what export settings you are using I can make sure it is included in the above bug report, we are working on giving better feedback with these sorts of errors. If you want to keep the documents private use this link Done. Perhaps on a related topic, I'm finding that when I place a pdf I received from a customer, it does not recognize and render the fonts properly, yet photoshop, indesign, etc. have no problem. Thus, it's not just exporting fonts that seems to be problematic, but importing as well. I could probably share the pdf if you want to look at that too. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted November 8, 2019 Share Posted November 8, 2019 6 minutes ago, Eric Louw said: Done. Perhaps on a related topic, I'm finding that when I place a pdf I received from a customer, it does not recognize and render the fonts properly, yet photoshop, indesign, etc. have no problem. Thus, it's not just exporting fonts that seems to be problematic, but importing as well. I could probably share the pdf if you want to look at that too. The Affinity applications require that you have all needed fonts installed locally. They do not make use of the fonts embedded in a PDF that you Open or Place. So the first question you need to ask is whether you have the fonts your customer used to make that PDF. Eric Louw 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
MikeW Posted November 8, 2019 Share Posted November 8, 2019 4 minutes ago, Eric Louw said: ...Perhaps on a related topic, I'm finding that when I place a pdf I received from a customer, it does not recognize and render the fonts properly... Unlike other layout software, APub does not have the capability to use what is called pdf passthrough. Nor can it utilize embedded font outline data to say converting type to either curves nor a bitmap. In other words, what you are experiencing with regards to Affinity products "recognizing" the embedded fonts is a current limitation but is "as designed." So no need to hand over a pdf for this issue. Eric Louw 1 Quote Link to comment Share on other sites More sharing options...
Eric Louw Posted November 8, 2019 Share Posted November 8, 2019 (edited) 3 minutes ago, walt.farrell said: The Affinity applications require that you have all needed fonts installed locally. They do not make use of the fonts embedded in a PDF that you Open or Place. So the first question you need to ask is whether you have the fonts your customer used to make that PDF. Ah, well that's a logical reason. That's also a pretty significant downside though for those of us with businesses in graphic design and printing. Any idea if that will ever change? Edited November 8, 2019 by Eric Louw Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted November 8, 2019 Share Posted November 8, 2019 Just now, Eric Louw said: Ah, well there's the reason. That's a pretty significant downside though for those of us with businesses in graphic design and printing. Any idea if that will ever change? We all hope it will, someday. But only Serif knows if it will, or when. Eric Louw 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 8, 2019 Staff Share Posted November 8, 2019 @Eric Louw Can you upload your vesion of the Advent Sans fonts and IBM Plex Sans to the above link too? As it's currently exporting fine for me but I'm missing a couple of fonts on my local machine Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Eric Louw Posted November 8, 2019 Share Posted November 8, 2019 1 hour ago, Jon P said: @Eric Louw Can you upload your vesion of the Advent Sans fonts and IBM Plex Sans to the above link too? As it's currently exporting fine for me but I'm missing a couple of fonts on my local machine Done. Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 8, 2019 Staff Share Posted November 8, 2019 The issue is the registered symbol in the Advent Sans font, if you remove the use of this from your text frame it will export. I'll get this logged. Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Eric Louw Posted November 8, 2019 Share Posted November 8, 2019 1 minute ago, Jon P said: The issue is the registered symbol in the Advent Sans font, if you remove the use of this from your text frame it will export. I'll get this logged. Hmm. Remove my use of the entire font I presume? I don't think I was using the registered symbol from that font in this file. The symbol on the left of the file was a separate eps, though I am aware that the font contains one as well. Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 8, 2019 Staff Share Posted November 8, 2019 The font is fine, there's an error when we are trying to write out the registered symbol it uses though. Remove this character and it should export fine (it does for me in the current 1.8 beta): Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Eric Louw Posted November 8, 2019 Share Posted November 8, 2019 (edited) 1 minute ago, Jon P said: The font is fine, there's an error when we are trying to write out the registered symbol it uses though. Remove this character and it should export fine (it does for me in the current 1.8 beta): Ah, I didn't even notice that. It adds automatically when I type in that word with that official font. Thanks! Edited November 8, 2019 by Eric Louw Jon P 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.