PDF export 0,01mm to large

[Jens_Ri]

Hy,

at first sorry for my bad english, i hope you understand my problem

i will build a din a4 brochure with 8 pages. 
i start a new dokument and say print / din a 4. 

i make 1 single page and 1 2side page - the pages are abolutly blank. i export this and i have in the pdf:
- the single page: 21,0x29,7 cm is normal din a 4 but in my pdf are: 21,1 and 29,71cm
- the doubleside: 29,7x42,0cm is normal din a 3 but in my pdf are: 42,0 and 29,71cm

with din a 5 is the same problem always 0,01mm to large in the pdf export. 
the same problem was with affinity designer and i have no idea whats going on or what i can do.

p.s. i look for the format with the mac preview app

hope you have an idea for my problem

[woefi]

Are you sure, you didn't acccidently include bleed?

[Jens_Ri]

Hi yes there is no bleed in the Documents 

[Patrick Connor]

Sorry.

Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script.

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build.