Gianni Becattini

Sorry, I was rathe messy... ALL MY STORAGE is local - simply there is a background process that replicates my files on the iCloud in-cloud storage. I ALWAYS take care, before I begin to work, that all the cloud storage is replicated locally - so Affinity should not neither perceive that my local storage is replicated elsewhere. iCloud for me is essential, because I need to use two different computers and I must say that, being sure that the files are correctly synced before starting to work, I have no problems with Publisher (apart of a small problem if I don't wait a few second after loaded the file - but I am not sure that this depends on iCloud). However, this replication process can operate ONLY on the main disk and I could not find a way to add an external disk and make it synced as well with iCloud. If I am not wrong, I could with OneDrive when I used Windows. The delay that Thomaso said, which I can confirm, is the value reported in the lower part of Finder window. When I deleted all the temp files (28 G), that value didn't change but changed after rebooting.

Yes, you are right, I posted the screenshot from another computer Good to know! No, I didn't Ahhh, that makes my doubts clear! I pay for 2 Tbyte iCloud space, but my computers have just 1 T (sorry, not G...)- My wishes were: to expand these disks, but in my Macs it is impossible - the chips are soldered on the CPU board; or to add an external hard disk, to keep synced as well, but this seems impossible with iCloud So, the only way is to spare space... Thanks for the help Gianni

Today my 1G hard disk is becoming small, so I chase all the space I can. The iMac i9 2020 does not allow to expand the hard disk and an external disk cannot be set under iCloud.

I deleted them as you suggested me, it seems to work! Thanks!

This is what I can see - I would say it's a binary file.

Hi, Mike. You are probably right, but this test would be rather heavy: my image folder is about 600 Gbytes and I try to avoid exposing the perfidious iCloud to temptations... However, I tried to switch off the Internet connection and could not replicate the problem. So the problem could be there...

Hi found that this folder contains about 30 gigabytes - can be safely deleted? /Users/giovannibecattini/Library/Application Support/Affinity Publisher 2/temp Thanks

With the last 3439 release, things go worse. Again, the important is to keep your hands to yourself just after opening the file for several seconds. The fault mode changed: now the block is more often total. Again you have no choice but to kill the application. If you pass the first period, in my experience Publisher remains very stable (occasional freezes, but rare).

Formerly, when you inserted pages from file, they were inserted after the page currently selected. Now you must insert the page number where you want the insertion or they are added at the end of the document.

Thanks for answering. I am surprised to be alone in this claim; the bug simply forbid to export a file for a commercial printer if you were so fool to link in Publisher affinity documents instead of TIFF or JPG. You could ask why I don't replace them. Because the books under discussion are three, each with about 1,000 photos, a huge job indeed. I repeat that I am a sustainer of Serif solutions and that in a large part of my life I used to be a software developer, so I well know the problems a software house encounters. But leaving an unlucky customer without a solution for so long is not very ..let's say, correct?

Sorry, you are right. With Affinity ...it's better to have no hopes. We are talking about a totally blocking bug, not solved after several months. If you like so...

I see that your promise was not kept... the last beta has still the same bug! I have no words...

Yes, it depends on the developer opinion. For me any way is good...

I tested with 2.6.3 (production); the problem is identical.

??? for what I can understand I should revert to 2.5, not 2.6. Wrong?

Thanks for your contribution. Sorry, I was a bit unclear earlier: Bug AF-6599 was my immediate concern. Serif has promised to fix it in the next release, and I want to trust they will. However, the issue with oversized PDFs during export will likely remain, blocking, from my side, on-demand printing services. Given this, having better control over the export process to eliminate the problem would be ideal — a perfect long-term solution. The workaround I proposed… is indeed just a workaround. It still places some burden on the user, but it could probably be implemented in just an hour of development time. It would offer a practical interim solution while waiting for a more comprehensive improvement.

I learned the hard way that Publisher technically supports the inclusion of .afphoto images, but this approach is neither well supported nor recommended. Nevertheless, in my case, it’s essential—converting each image to TIFF every time would be extremely time-consuming. Using .afphoto files also has a major drawback: the resulting PDF files are 5 to 7 times larger than those generated with TIFF images. This makes it impossible to use certain on-demand printing services, such as Lulu. So here’s a small suggestion that could greatly simplify things: when loading linked .afphoto resources, the software could first check for a .TIFF file with the same name. If it exists, load the TIFF instead; if not, fall back to the .afphotofile. As a software developer, I believe this would be a simple and quick change to implement. Any other solution that allows for an easy switch between .afphoto and TIFF—without requiring manual relinking—would however be greatly appreciated. Thanks

Thanks for answering. I hope they really do.

I think I’ve found a workaround — not very practical, but potentially viable. I’d appreciate any criticism in case I’ve overlooked something. Exporting a single page always works. Exporting a list of pages also works, as long as the list includes only even or only odd pages. So, instead of exporting the entire book in one go, I export each chapter twice: First, using the odd-numbered pages (e.g. 1, 3, 5, 7, …) Then, using the even-numbered pages (e.g. 2, 4, 6, 8, …) This gives me two PDFs: one with odd pages, one with even. Then I merge them using PDFSam Basic (free), using the “Alternate Mix” function to interleave the pages properly. Clearly, it’s a cumbersome process — but still far better than manually converting and managing 2,000 TIFF images. And since this would only be done as the final step before printing, it’s tolerable. I’m still not sure whether I might be missing some hidden issue — for example, how to verify the correctness of the bleed in this two-pass export process. In any case, Serif really should fix this bug. Am I the only person in the universe who links .afphoto files as sources, instead of converting everything to TIFF? For me, there’s simply no alternative. I’m a one-person operation managing over 4,000 pages and 6,000 photos — I can’t afford duplication. It’s like programming: I need pointers, not data copies. Thanks PDFsam_alternatemix.pdf

Sorry for having disappeared, I am back again, and sorry also for the "typography" - probably a "false friend" with Italian "tipografia" which means, as you said, a commercial printer. I discovered something but not too useful: a picture "that works" (see the attached files, and afpub and the linked afphoto). It is exported correctly, but even the minimal modification returns back to the error condition. Test.zip

Thanks Rat! The problem is that when I EXPORT the pdf as PAGES (as all typographies want), many image placed on the right pages I mean: if i want to export also the bleed in the first pdf, I just thought "I can increase the page size". But when I change it in Document Setup, nothing changes. .... I finish this evening ... I am dragged away

Thanks for the Idea, Rat, but how to add the bleed to the first pdf?

One of the problems is to export also the bleeds. If I buy a Windows PC and buy Acrobat or something like that, can I Print with the bleeds etc. (color profile, printer marks etc.)?

But how can make Publisher to add the bleed to the produced file? Is there a better printer driver than the native one by Apple? Years ago, Acrobat could operate also as a printer driver, but this possibility was removed in the later versions.

Thanks also for your willing to give me a solution, but it cannot work. I have a lot of pictures across the spread (see the example below). If I unset the "Facing pages", the picture remains only on one page but doesn't appear on the other (or there is some way that I didn't understand?)