Hangman

not yet - just got too busy at work... but it is still on my list. This week for sure

Hi @vincentlepes,
I can certainly confirm the issue with both your document and a new document... It definitely appears to be a bug, I see the same incorrect behaviour as far back as V1.7.3 though unsure if this has been previously reported and logged.

Hi @Uschi59 and welcome to the forums,
From your description, this sounds like a known bug reported in the 2.2 release... Does your file use the 'Euroscale Coated V2 'profile?
A Beta Patch, v2.2.1.2052 was released on Friday which will hopefully fix this issue for you so if you are part of the Beta program you could install this patch and try it to see if it resolves your export problem. The Beta software can be installed alongside the retail version and both can run together side by side.
If you're not yet enrolled in the Beta program and would like to join you can do so by clicking the link in @Ash's post here...
If you try this let us know how you get on and if it resolves the issue you are experiencing...
In the meantime, if you are happy to upload your Publisher file along with any Linked graphics we can take a look to make sure there is nothing else going on that could be causing the export issue.

Thanks for confirming - I've updated the development log to include this info

I ran a quick test copying the entire graphic to an earlier version of Designer using 'Copy as SVG'. Doing so copies all the 'Texture Line Style' curve layers as curve fill layers. All layers copy apart from the two with issues. When you attempt to copy those two layers individually, no layers are pasted.
Pressure also appears to have an impact... changing the pressure setting for the two lines in question fails the export when using the both default Pressure and Velocity settings but works when using either None or Velocity (Inverse) though I suspect that's just another variation of your tests where Flip Horizontal also works...

Hi @Marcocampo,
A Beta Patch, v2.2.1.2052 was released on Friday which may potentially fix this issue (assuming it is actually caused by the same bug) so if you are part of the Beta program you could install this patch and give it a try to see if it resolves your issue. The Beta software can be installed alongside the retail version and both can run together side by side.
If you're not yet enrolled in the Beta program and would like to join you can do so by clicking the link in @Ash's post here...
The obvious caveat here being that your particular issue may turn out not to be related to this specific bug so may not fix the issue but I think it is wirth trying since I didn't experience the bug in the first place and likewise had no issues exporting your file.

Hi @antoine-b,
This is logged as fixed in the latest Beta Patch, v2.2.1.2052 so if you are part of the Beta program you could install this patch and give it a try to see if it resolves your issue. The Beta software can be installed alongside the retail version and both can run together side by side.
If you're not yet enrolled in the Beta program and would like to join you can do so by clicking the link in @Ash's post here...

Hi @LambdaRed,
A new Beta Patch was released on Friday V2.2.1.2025 which suggests it fixes this particular issue...
If you're signed up for the Beta program you could perhaps download and try that version first. The Beta version can be installed alongside the Retail version.
If you're not already signed up for the Beta program you can do so here...
Let us know if that is an option and if so how you get on...
In terms of the closest alternative profile my assumption would be Coated Forgra 39 ISO 12647-2:2004.

For me, it is dependent on whether or not you've had an Affinity document opened prior to opening the multiple PDF files.
If you reboot Designer or Publisher then select multiple PDF files, right-click and select 'Open With' then they all open...
  If you reboot Designer or Publisher, create a new Designer or Publisher document, then close it (leaving the app open) when you then select multiple PDF files, right-click and select 'Open With' this is what I get... Results After Creating a New Document and then Closing the New Documenty Leaving Affinity Designer or Publisher Open
One pdf selected - one pdf opens Two pdf's selected - one pdf opens Three pdf's selected - two pdf's open Four pdf's selected - two pdf's open Five pdf's selected - three pdf's open Six pdf's selected - three pdf's open Seven pdf's selected - four pdf's open Eight pdf's selected - four pdf's open Nine pdf's selected - five pdf's open Ten pdf's selected - five pdf's open Eleven pdf's selected - six pdf's open Twelve pdf's selected - six pdf's open  

This happens when the opposing node handle for a node is missing... Holding Cmd (Ctrl) and dragging the existing node handle until the opposing node appears tends to fix the problem...

Unicorn Invitation.mp4

Stokerg is gone for the weekend  I did set back everything to a older version (software and original files) It is still very unstabel and crashes all the time but i managed to get to the end of the list. It is not a very good solution but i have my list for my tasting days next week. I hope dat @stokerg wil be able to find the bug in the days to come.

https://forum.affinity.serif.com/index.php?/search/&tags=AFD-5459

Thanks for your reply. I appreciate the difference between editable content and "clipart". I get content from variable sources in .PDF format where I'm using the content "as is".
I simply dragged the file onto the page and wasn't intending to edit content. Thanks for clearing up the issue for me.

To be honest, I would hold off updating to Sonoma, there have been numerous reported issues with Sonoma affecting the opening of Affinity files and various other issues so I think you may regret updating at this stage. I would be inclined to wait until some of those issues have been ironed out and fixed before updating as I think, at the moment, it could lead to more problems...
I've not been to Belgium for many years, but maybe it's time for another visit...

That worked fine. Thank you, Hangman.
Actually my shapes are much more complex than squares, and there are situations - like in the "five squares" example - where I could remove the centre one and still have the same  (empty) shape.

And now about the problem of the "packed notes": suddenly everything is working normally - as it should. I can no longer reproduce the error. Be that as it may, it's good that it's working now. Hopefully it wasn't a bug but a mistake on my part. Thank you for helping!!

Just to add to what @stokerg mentions above, I can likewise open standard RAW Z8 files despite LibRaw not 'officially' supporting the camera yet but I think that's because the Z8 uses the same sensor as the Z9 which is supported.
One thing to be aware of however is that, as far as I'm aware, Nikon Z8 and Z9 High Efficiency Raw files are still not supported. I've been trying to find one online to test but if you happen to be shooting using this RAW mode you may experience issues opening the RAW file.
Could you confirm which RAW Mode you are using with the Z8.

I believe the PDF data from the embedded file is essentially 'missing' from the Affinity document, and the app is trying to determine the file type for the data remaining - albeit incorrectly.
There are a few oddities with this embedded file, including the 'Type' shown in the resource manager, assumedly due to the unexpected status of this embedded data, which is also causing the reported issues when exporting.
As above, I've logged this file with our development team for further investigation, as without the required development tools it would be very difficult for me to be certain of the exact reason for this file being in the 'embedded' but 'missing' state that it appears to be in.

This is the first time I need support...thank you both for the quick and helpfull solution. 👏🤘

I replaced both to be sure.

The fonds where the problem! It works again! Thanks for the support. I couldn't find this myself!

Hi @Joeri Beelprez,
Many thanks for the files... I've just run a test and I didn't experience any crashes...
There did appear to be a couple of font issues, attempting to install Al Nile gave an error so I didn't install it...

And it doesn't seem to like the Adobe Song Std font glyphs, in particular, the diaresis for the letter ë used in 'Argentinië', 'Italië', 'Sicilië', 'Australië' and 'Californië' or the acute accent used for the é used in Rosé.
The accented glyphs in that font also seem to use some odd spacing...
I also noted that the country header text is outlined, I was unsure whether that was intentional but you effectively have grey text with a black outline...
 

But in terms of the Data Merge, that all seemed to go without issue...

prijslijst.mp4 I don't know if it's worth temporarily disabling the Adobe Song Std and Al Nile fonts one at a time to see whether or not either impacts the Data Merge... for you, is it literally crashing at the point you hit Generate in the Data Merge panel?

Hi @Joeri Beelprez,
Many thanks for the files... I've just run a test and I didn't experience any crashes...
There did appear to be a couple of font issues, attempting to install Al Nile gave an error so I didn't install it...

And it doesn't seem to like the Adobe Song Std font glyphs, in particular, the diaresis for the letter ë used in 'Argentinië', 'Italië', 'Sicilië', 'Australië' and 'Californië' or the acute accent used for the é used in Rosé.
The accented glyphs in that font also seem to use some odd spacing...
I also noted that the country header text is outlined, I was unsure whether that was intentional but you effectively have grey text with a black outline...
 

But in terms of the Data Merge, that all seemed to go without issue...

prijslijst.mp4 I don't know if it's worth temporarily disabling the Adobe Song Std and Al Nile fonts one at a time to see whether or not either impacts the Data Merge... for you, is it literally crashing at the point you hit Generate in the Data Merge panel?

Hi @Joeri Beelprez,
Do you still see the same crash when the images you're linking to are located on your internal Hard Drive rather than One Drive? I can open your file without issue but I suspect that's because I'm not attempting to link to the One Drive images.
You could test this in a new document by moving/copying the associated images for the first half-dozen entries on your spreadsheet to your internal Hard Drive and then restricting your Data Merge to just those records to see if you experience the same crash or if this fixes the issue.
My guess/assumption is the crash is likely caused by Publisher attempting to sync to One Drive though I'm sure someone from the moderation team will be better able to determine the cause from your crash report.

I think there are multiple issues - both font issues and formatting issues.
And you need to deal with the font issues first.
Times is an Apple "Document-support font" - so it is only supported in existing documents, and only in applications which support Apple's font controls. Apparently Word 365 does support Apple's font controls, so the font is available in your existing Word document. Affinity applications do not support Apple's font controls, so fonts which Apple has now deemed a  "Document-support font" do not appear in APub. Which is why Times got converted to a fall-back font - Times New Roman - which is still supported both by Apple, and Office 365.
I think Microsoft has now started restricting the fonts installed with Office 365 on Mac to use only in Office 365. So Calibri is normally not going to be available to APub now. That may only be on the Mac. Do not know for sure.
Calibri is installed with Office 365 for Mac.
Office 365 Cloud Fonts are not available to APub on Mac or Windows.
So the first thing to do is convert to fonts which do not have any restrictions.
There are lots of free OFL licensed high-quality text fonts with none of these OS font issues.
There are lots of commercial high-quality text fonts with none of these OS font issues.
Once you have fonts which will transfer properly then you can deal with the format issues.
Some of the format issues may be because of different character widths in the fall-back fonts.
Having fonts which transfer properly would eliminate that as a potential issue.