Lisa Salazar Posted September 13 Share Posted September 13 I have an InDesign file exported as an IDML file using the package command in InDesign. All the linked images are in the Links folder as required, but every attempt I have made to opne the file results in AP2 crashing. Any suggestions? Project files attached: VCH-PrayerBooklet(PrinterSpreads)April 9 at 1130 Folder.zip Quote Link to comment Share on other sites More sharing options...
Hangman Posted September 13 Share Posted September 13 Hi @Lisa Salazar and welcome to the forums, The issue is with Prayer Booklet Build March 27_49.eps on Page 13... That particular EPS file is causing the Affinity Apps to crash so I've resaved that file and replaced it... Affinity Publisher shows the Plant background image on the front cover with an Original DPI of zero so I've replaced the EPS file. It now displays the correct Original Placed DPI in Resource Manager... I noticed that: All the EPS files dated March 16 have text converted to Curves, i.e., the text remains in vector format All the EPS files dated March 27 (except 1.eps) have rasterised text (except the page numbers) so the text appears as Image layers in the EPS files Was this intentional or should all pages have vector (converted to curves) text? The rasterised text is noticeable on the printed output... I've attached the updated Publisher file which should now open without issue... You may find that the Linked EPS files display a little blurry when opening the Publisher file... This appears to be a screen redraw issue with Linked files in Publisher where what looks like a cached preview is displayed in place of the full-resolution file... Zooming the pages in or out will display the EPS files correctly as will changing the Linked files to Embedded in Resource Manager, Saving, Closing and then Reopening the Publisher file though I appreciate you likely wish to keep the files Linked... This issue has been raised in a couple of other threads as well so I'll raise a separate bug report for the issue and link it back to this thread... Note: The display redraw issue with Linked files doesn't affect the PDF export... Updated File VCH-PrayerBooklet(PrinterSpreads).zip Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
MikeW Posted September 13 Share Posted September 13 @Hangman, The .idml files loads with all the .eps files in QXP, Viva Designer and Scribus. If APub is choking on that particular file, which is a perfectly valid file, perhaps this thread should be flagged as an error in APub and Serif take a look at improving it. lacerto 1 Quote Link to comment Share on other sites More sharing options...
lacerto Posted September 13 Share Posted September 13 Obsolete. Quote Link to comment Share on other sites More sharing options...
lacerto Posted September 13 Share Posted September 13 Obsolete. MikeW 1 Quote Link to comment Share on other sites More sharing options...
R C-R Posted September 14 Share Posted September 14 4 hours ago, lacerto said: My point is: EPS really is a standard. These kinds of errors should not exist, if the standard is included (even if it is no longer developed, or if it has been superceded). Even if Serif chooses not to support EPS fully, the apps should not crash when trying to open one with unsupported features! Quote All 3 1.10.8, & all 3 V2.5.5 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
Hangman Posted September 14 Share Posted September 14 5 hours ago, R C-R said: Even if Serif chooses not to support EPS fully, the apps should not crash when trying to open one with unsupported features! There are several issues with the EPS files... All the EPS files dated March 16 have text converted to Curves, i.e., it remains in vector format All the EPS files dated March 27 (except 1.eps) have rasterised text (except the page numbers) and so appear as Image layers in the eps files The Plant background image on the front cover shows an Original DPI of zero so needs to be replaced It looks as though there are font issues with the later batch of eps files since I'm pretty sure the text shouldn't appear rasterised but should match the March 16 files... I suspect Publisher is having issues with the 'Traditional #20 Arabic' font on 49.eps since there is nothing else on the page other than rasterised text... Not that it helps but on Windows, 49.eps doesn't crash the app but instead results in the never-ending 'Loading 1 document' scenario when attempting to open it in Affinity apps... As others have mentioned 49.eps opens in other software... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse Link to comment Share on other sites More sharing options...
MikeW Posted September 14 Share Posted September 14 7 hours ago, Hangman said: There are several issues with the EPS files... All the EPS files dated March 16 have text converted to Curves, i.e., it remains in vector format All the EPS files dated March 27 (except 1.eps) have rasterised text (except the page numbers) and so appear as Image layers in the eps files The Plant background image on the front cover shows an Original DPI of zero so needs to be replaced It looks as though there are font issues with the later batch of eps files since I'm pretty sure the text shouldn't appear rasterised but should match the March 16 files... I suspect Publisher is having issues with the 'Traditional #20 Arabic' font on 49.eps since there is nothing else on the page other than rasterised text... Not that it helps but on Windows, 49.eps doesn't crash the app but instead results in the never-ending 'Loading 1 document' scenario when attempting to open it in Affinity apps... As others have mentioned 49.eps opens in other software... The plant background image at the size of placement produces an image in a generated pdf of ~220 dpi. There is nothing wrong about the .eps file. Unless/until that image is extracted, Serif shouldn't actually try to estimate dpi in a vector .eps that contains an image resource. I believe at some point this these .eps files were generated from a pdf where the original source originated in MS Word 365 or were technically printed/exported to Acrobat's MS Word plugin for MS Word. lacerto 1 Quote Link to comment Share on other sites More sharing options...
lacerto Posted September 14 Share Posted September 14 Obsolete. Quote Link to comment Share on other sites More sharing options...
MikeW Posted September 15 Share Posted September 15 2 hours ago, lacerto said: The file that causes issues in Affinity apps is a kind of a maturity test for robustness of an app as regards interpreting PostScript. Adobe apps, QuarkXPress and CorelDRAW have no issues (but surprisingly the macOS version of CorelDRAW fails), nor does Inkscape, or GIMP, and even Macromedia FreeHand passes the test (prints the placed EPS e.g. to a PDF file without problems), as does macOS Preview, and Pages. VectorStyler passes the test partially since on Windows the "English" part fails to render properly (but no issues on macOS). Xara Designer Pro fails. I assume your Windows CorelDraw installation uses GhostScript and the Mac version doesn't? If so, that is likely the reason the Windows version will parse the eps file as well as it does. GS would be a good addition to Affinity applications. Especially the way CD uses it. At start up, CD checks the registry for GS and simply uses it if installed. lacerto 1 Quote Link to comment Share on other sites More sharing options...
lacerto Posted September 15 Share Posted September 15 Obsolete. MikeW 1 Quote Link to comment Share on other sites More sharing options...
Staff stokerg Posted September 24 Staff Share Posted September 24 Hi @Lisa Salazar, Thanks for reporting this and thanks to @Hangmanfor tracking it down to the EPS file. I've logged the EPS file with the Developers, as a crash is always unwanted behaviour. I'll update this thread with any information i get from the Developers on this issue issue Hangman 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.