Jon P

Hey Jon, 
Clearing the user data fixed the issue.
Thanks,
L

Thanks for supplying the font.
We've taken a look into this and believe we are interpreting the font according to spec, but I've logged a feature request for us to add something similar to InDesigns World Ready Composer to help with this.

Thanks for supplying the font.
We've taken a look into this and believe we are interpreting the font according to spec, but I've logged a feature request for us to add something similar to InDesigns World Ready Composer to help with this.

@Alfred Cheers mate, that post got lost in translation somehow. My bad.
Thanks Jon, it’s on its way.

If you want to supply us the font here I'll have a look at it
Thanks

@guesthollow
 
We think that we will need to update the Affinity suite when macOS Monterey releases, so I would expect the Windows and Mac version of Affinity Publisher 1.10.2 will be live after we have made any changes needed for that (rather than patch twice in quick succession) So at least 3 weeks but perhaps not much longer than that. Thanks for your patience

Beta 1.10.2.1167 opened the file without problems. 

There is no mass delete anchor button, although you should be able to multi select in the dialog and press the delete button to delete multiple at once. But yes I would advise removing the ToC, clearing up all that is left (assuming they aren't other anchors you need!) and then re inserting the ToC, ticking to include PDF Bookmarks and then the only anchors that exist in the anchor panel should be those that the ToC is using

There is no mass delete anchor button, although you should be able to multi select in the dialog and press the delete button to delete multiple at once. But yes I would advise removing the ToC, clearing up all that is left (assuming they aren't other anchors you need!) and then re inserting the ToC, ticking to include PDF Bookmarks and then the only anchors that exist in the anchor panel should be those that the ToC is using

Yes, it's about endian-ness. But also, if you have one, you know you have a Unicode file. If you don't have one, you might have a UTF-8 file, but you might instead have ISO-8859-1 (or a variant) and you have to guess based on the data you encounter.

Because, from experimentation, Publisher is using the first 4096 bytes of the file to determine the file encoding. If nothing in the first 4096 bytes requires UTF-8 encoding, then Publisher is assuming the file to be using ANSI encoding rather than UTF-8, and interprets the rest of the file in ANSI mode rather than UTF-8 mode.
The first é, which is the first UTF-8 encoded character, is at position 4523 in that file. Therefore Publisher has decided the file is ANSI-encoded.
Edit: And any changes that shorten the file and bring that first é into the first 4096 characters will resolve the problem. As would adding some UTF-8 character to some other location, such as within the header line at the top of the file.

The bug that caused this should hopefully be fixed in the latest beta found here.
Unfortunately you will need to manually delete these anchors via the anchor panel to clear them up (you can always just delete all anchors and then re generate the ToC to get it to add the correct ones in).

Will try now @Jon P
That seems to work on both hyperlink and no hyper links now.

Many thanks for your insightful analysis.  It appears to work in the beta version.  However, it generates an error In the current production version.  Nevertheless, this seems to solve the problem.
With gratitude,

Hi @ABZ, Apologies for the late reply, bumping old threads can mean they get missed by our ticketing system, we always advise creating a new thread if possible.
Your afpub exports a PDF with hyperlinks correctly for me on both Mac and Windows, but I can see that your PDF does indeed seem to be broken.
Can you re-export your PDF from Mac and use the PDF (for export) profile, I think what might have happened here is it was exported and set to not include hyperlinks, but a viewer is adding hyperlinks itself but not doing it correctly. It can be a bit confusing as even if you export without hyperlinks enabled, the hyperlink formatting is still applied to urls within the document, combined with the viewer then noticing it's a URL and attempting to create the link itself can lead it to look like links have been broken when they go over 2 lines.
If the newly exported pdf with the (for export) profile is still broken can you upload it here and let me know what PDF viewer you are using to view it? It will also be useful if you could save the afpub as a package and upload that, as I am missing fonts used in the afpublisher file.
Thanks
 

Success! I was able to open it with no issues!! 😄 

Thanks for the report, I can reproduce this and have logged it

I'm glad it works in the beta, however the error will have been because a hyperlink in that document is not RFC compliant.
If you look at preflight in the beta it should warn you about this in the beta. It will not be exporting the hyperlink in the beta (as apposed to retail where it would attempt to export it and valid due to it being invalid)

Thanks, was fairly easily reproducible with that file so I've logged it. I thought rasterizing it might help but it does seem to be related to the wrap

There is a requirement that the three applications need to be in the Applications folder on the computer's hard drive. Then there is the need to first open the Photo and Designer applications after updating before the Publisher application will 'see' them as existing, but I think you have done that.
My system is OS 11.5.2 with the Publisher from Serif and Designer and Photo from the Mac App Store. All work well here.

This Beta solved the "fail to save or save as" problem.😃👍

The large image/picture frame on Page 32 was causing the problem
Deleted the image/picture frame - now OK- will need to be readded by you
(Image was of a house made out of cigarette packets)

Notes:
Document contains lots of Embedded images, you may wish to consider Linked images instead to keep document size to a minimum
Backup regularly - not all corrupt files can be recovered

PS I have no idea why the file name changed when I uploaded it to the forum - it was called 2005-2009_jubilumsbuch-recovered.afpub on my PC
 
494239207_2005-2009_jubilumsbuch-recovered.afpub

That file worked - thanks for the quick reply!

Thanks Jon P,
The file opened without issues, many thanks!

There is a known problem with email hyperlinks that is fixed in beta 1.10.0.1135 or later. If that might explain your problem you might try using that beta for now. You can find it in a pinned topic the top of the Publisher Beta on Windows forum.
You can also try enabling logging during the export to identify other problems, if this is only an issue with PDF exports.