Multi page spread - crop marks

[bpu]

Hello,

I used the search and did not find if this has been talked. I'm very happy the new Publisher 2.6 version is including multi page spread, I've started using beta just to try this feature.

One thing I've found while exporting a .pdf with crop marks, is that it only has edge marks. I think there should be an option (or by default), to also add marks to each page division. This is useful when folding leaflets, creasing book cover spines and flaps, etc. because its better to use the guide than relay on ruler measurements or eyeballing.

Thanks for all your work!

[Patrick Connor]

We have done a lot of work on pages and spreads in 2.6.0 beta 

• Advanced Page Management:
  • Multiple Pages Feature 
  • Page Reflow Control
  • Page Migration Improvements
  • General Improvements

As part of these changes, multi-page spread fold marks in exported PDFs will be coming to this NEXT 2.6.0.xxx beta release, due to be available Tuesday or Wednesday this week.

If you would rather not use the 2.6.0 beta version (please note, 2.5.x files saved in the 2.6.0 beta cannot be reopened in the 2.5.x release build) then you can rest assured this feature will be coming to the future 2.6.0 release (no date for that has been announced yet)

[Affinity Info Bot]

An issue raised in this thread ("Multipage spreads don't produce fold marks") has now been reported to the developers by the testing team (Ref: AF-3695). Thank you very much for reporting this issue to us.

[Dazmondo77]

3 hours ago, Patrick Connor said:

As part of these changes, multi-page spread fold marks in exported PDFs will be coming to this NEXT 2.6.0.xxx beta release, due to be available Tuesday or Wednesday this week.

Excellent news 👍

[bpu]

Great! Thanks for the reply, sorry for not finding it, I am not english speaker so I did not think about the english name "fold mark".

Thanks!

[Affinity Info Bot]

The issue "Multipage spreads don't produce fold marks" (REF: AF-3695) has been fixed by the developers in the latest beta build (2.6.0.2900). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.