gEP1000

Hi, I use the Affinity Publisher version 1.8.6 and anew I have the problem as described in December 2018: it doesn't save my chosen spreads/pages, when the PDF changed externally. The bug might have already (re)occurred in some versions earlier. In my general settings I currently use the option "Automatically update linked resources when modified externally". Thank you for your efforts.

Thank you a lot! Your last message helped us, because until now we always printed with the "preview" from Mac OS 10.14.6. When using Acrobat, the printed-out quality is good as expected! Thank you for your fast replies and the time and effort you spent on helping us. We are really pleased with the customer support and the Affinity Publisher itself. Thank you.

Yes, that's correct.

If I do the following: 1. Create the pdf from Publisher by using the macOS printing dialog (we get a very big file > Using ghostscript on the command line with either default /ebook or /printer options shrinks down the filesize), then print it out Result: the printing quality is good as expected. 2. Print it out directly from Affinity Publisher Result: the printing quality is good as expected. 3. Export a PDF with compatibility: PDFX3, then print it out Result: the printing quality is a little worse, but still ok. 4. Export a PDF with e.g. compatibility: PDF1.7(Acrobat) Result: Blurry text and numbers, does not fulfill quality standards and can not be handed out to our customers. So something with the PDF1.7 (Acrobat) is wrong. On-screen it looks fine, but the printed-out version is not, especially when comparing it to 1., 2. or 3. The printer, the printer driver, the network and the printing workflow are working correctly. This is tested by trying option 1 or 2 and nothing is changed when replicating the issue. I just uploaded the scan of the printed-out PDF1.7(acrobat)-version (option 4, "20190920110323_PDF17.pdf") to the writable dropbox Link you sent me so you can have a look at it. Thank you for your help!

I tried this also with the latest beta and the result is still the same. The printed-out result of the PDF-1.7-exported PDF is of course not totally blurry. But when I compare it directly to a printed-out PDF using the „Workaround“ (see below) or printing directly from Affinity Publisher, obviously the PDF-1.7-exported PDF is more blurry and does not fulfil the quality standard for printing out for our customers. Just to avoid misunderstandings: printing directly from Affinity Publisher or using the „Workaround“ described below, from the same printer and from the same Mac results in perfect quality. We also tried it from different Macs. Workaround If we create the pdf from Publisher by using the macOS printing dialog we get a very big file. Using ghostscript on the command line with either default /ebook or /printer options shrinks down the filesize and the printing quality is just fine.

Thanks. I just uploaded the files. Thank you in advance.

Hi Gabe, thanks for your help. Could you please send me a writable dropbox Link to upload the files just for your review? Thanks in advance!

Hey, first of all thanks for this very nice software. We discovered an issue with the pdf export quality (latest and latest beta macOS Version of Publisher, macOS Version 10.14.6). Workflow of what we do 1 Create a pdf with the macOS printing dialog from an Excel file. 2 Link the pdf-from-excel file into a new Publisher document. The numbers of the Excel file are still numbers and not pictures. 3 Add a text field with some text to the Publisher document. 4 Export to pdf from Publisher with e.g. compatibility pdf 1.7 profile. 5 Print the document on a Canon laser printer. Result Blurry and bad quality of the text on the print for the numbers on the linked pdf-excel-file and for the text inserted in Publisher itself. The quality of the PDF on the screen in Acrobat or Preview looks, but the printing quality varies a lot. We tried all compatibility pdf profiles with the same result. Only the PDF/X-3 profile results in a better printing quality. Workaround If we create the pdf from Publisher by using the macOS printing dialog we get a very big file. Using ghostscript on the command line with either default /ebook or /printer options shrinks down the filesize and the printing quality is just fine. Conclusion I assume there is something wrong within the pdf export options/workflow in the background in Publisher. It would be nice to see this fixed in the next version. Thanks a lot.

Hi, in version 1.7.0.292 it is fixed! Thank you a lot!

Hi, I sent you a PM with an example PDF. Thanks

When I placed a PDF (which has been created in Excel and then printed as a PDF) in the document, some of the "cells" of my PDF were not recognized correctly. When the text in nearby cells is a bit more close to the text of the next cell, Affinity Publisher just merges them together to one selection. Is there any possibility to get these merged cells separated correctly? Thank you a lot.

The following might be a bug: We use linked PDF files with more than one pages. By clicking on the PDF we have the possibility to choose which page we want to be visible in our document (“Spread”). We have e.g. a 4 pages AffinityPublisher document and a linked PDF with 4 pages. On each Affinity page we want another page of the PDF to be visible. The problem here is, when we update a modified PDF in the resource manager, the program doesn’t save our chosen spread. Instead it just sets all of the 4 links to “Spread: Page 1”. Thank you for your efforts.

We are using linked PDF files in our document. When we replace the PDF files (we update the content), we need the program to recognize this. In the “Resource Manager” we can see that the new PDF is recognized (it’s now labeled as “Modified”). Now, what we need to do is to click “update” in the resource manager, so that the NEW PDF is updated. In the program we used before, when we opened a document and the linked PDF has changed, there was immediately appearing a Pop-Up-Window asking, if we want the modified linked PDF to be updated or if we want to leave it like it is. Such a Pop-Up-Window would be really helpful.

Another +1 for data-merge