Jump to content

Recommended Posts

Posted

Hello Affinity-support-team,

i've just purchased and installed the great new Affinity Publisher V2 (version 2.0.0) on windows 10.

Unfortunately a bug I've reported to the affinity forums a long time ago is still present in the current 2.0.0 release.

Bug: a single standard DinA4-page (210mm x 297mm) gets added 0,1mm in width while exporting to PDF-file.

How to reproduce:

1. File > New > A4 > Create

optional: add some text on the page

2. File > Export > PDF > choose some settings for example "PDF (for export)" (bug exists on every export-setting)

3. The exported PDF-file will get 0,1mm more in width. So 210,1mm x 297,0mm instead of 210,0mm x 297,0mm.

How to "fix":

If you export more than one DinA4-page (for example just duplicate page1) the PDF-file is correct with 210,0mm x 297,0mm dimensions.

Afterswards you need some PDF-editing software and delete some pages if you only want the first page with correct millimeter-dimensions in the pdf-file.

 

Here's a video from an earlier version which i've made to report the bug:

 

Posted
On 11/12/2022 at 11:10 PM, SKAot said:

PDF-file will get 0,1mm more in width. So 210,1mm 

During export, the millimeters are obviously converted incorrectly into DTP points and/or rounding is done incorrectly somewhere. The page width of 210 millimeters corresponds to 595.55568 DTP points, if a DTP point is 0.35277 mm. The program apparently calculates with 0.35268 mm. The PDF thus has a size of 595.44 pts or (rounded) 210.1 millimeters. 

 

Ich hoffe, ich erlebe es noch, dass die deutschen Anführungszeichen in Affinity Publisher korrekt funktionieren.

Posted

You are absolutely right. Unfortunately this missbehaviour is not new 😒

 

Of course other Software handle this without hassle.

To not always quote Adobe (Illustrator, InDesign, Photoshop) i did a quick Test with the open source Inkscape:

Document Size DIN A4:

image.png.36f1cb8deadcd63ed920406b794c199c.png

 

Export PDF from Inkscape:

image.png.ca0034fec757770ba59032bf45097060.png

 

Check dimensions in Acrobat - exactly as expected:

image.png.b8c62a1c007c20b0f329cfb67dfb9e74.png

 

There seems to be no special kind of secret witchcraft to do this right ?!

Such missbehaviour in Affinity become almost ridiculous after all the years.

Do you think an open source community like Inkscape and GIMP have more money for their developers to do more precise work - just kidding 😪

Hardware: Windows 11 Pro (23H2, build 22631.4317, Windows Feature Experience Pack 1000.22700.1041.0), Intel(R) Core(TM) i9-14900K, 32 Core@3.20 GHz, 128 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas.

Posted

To be precise: use the frame tool in Acrobat pro or preflight to check PDF-X exports:

Affinity DIN A4 export:

image.png.83a680f409db2a0a18a24584c586d402.png

 

Inkscape DIN A4 export:

image.png.bc4463c511a5f4075e7f7df1996b159f.png

 

Hardware: Windows 11 Pro (23H2, build 22631.4317, Windows Feature Experience Pack 1000.22700.1041.0), Intel(R) Core(TM) i9-14900K, 32 Core@3.20 GHz, 128 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas.

  • 3 weeks later...
Posted

Okay, I have just bumped into this issue myself and I have to say that this problem exists for different types of export as well! I have a created a document of 300 x 300 mm with facing pages and exported all the spreads as loose JPEGs, they ALL have a size of 600 x 300,01 mm!

This is kind of crazy that NOTHING has been done to fix this! I mean, how can a program export something of a size different than the settings you chose? If I want to create an image of 300 x 300 pixels and the final result would have been 300 x 301 pixels without any possibility to fix that it would have been totally unacceptable and this extra 0,1 mm is just as unacceptable IMO! :(

Posted

To be honest, unfortunately Serif does not really care about such real world problems that professional user are confronted with in their daily work.

In a nutshell: We give . .... on performance and/or precision. If it does not crash our app - it is not a bug.

Read this post and the check the initial problem:

 

Hardware: Windows 11 Pro (23H2, build 22631.4317, Windows Feature Experience Pack 1000.22700.1041.0), Intel(R) Core(TM) i9-14900K, 32 Core@3.20 GHz, 128 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas.

Posted
2 hours ago, Vosje said:

exported all the spreads as loose JPEGs, they ALL have a size of 600 x 300,01 mm

See my reply why this particular scenario is not a bug: 

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Posted
On 11/12/2022 at 11:10 PM, SKAot said:

a bug I've reported to the affinity forums a long time ago

On 11/12/2022 at 11:10 PM, SKAot said:

How to reproduce

Can't reproduce v1.10.5 on MacOS El Capitan, no matter how hard I try.
All PDF/X-4 DIN A4 @ 300 ppi exports are shown in Acrobat preflight as 210.0×297.0 mm.

(Haven't checked in v2 (or the new beta for that matter) yet, as I'd have to reboot the MacBook to Catalina first, which I can't right now…)

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Posted

I do not reproduce this malfunction by using only the Property menu.

a4-00.thumb.png.3858ef964846069d0828bc94eb66adeb.png

 

The problem does occur when you go to the Page Area tool (4dimage).

a4-01.thumb.png.ef5ef6fe9490937f9bdcb2d4baf6f571.png

Note:

🟥The error seems to stem from the insufficient number of decimal digits used for the conversion from inch to cm.

8.2700" × 2.54 = 21,056 cm~210,06 mm.

11.6937" × 2.54 = 29,7019 cm~297,02 mm

🟩To correct from an inch value, use:

8.267716" × 2.54 = 21,0001 cm~210,00 mm

11,692913" × 2.54 = 29,6999 cm~29,70 mm

 

6 cœurs, 12 processus - Windows 11 pro - 4K - DirectX 12 - Suite universelle Affinity (Affinity  Publisher, Affinity Designer, Affinity Photo).

Mais je vous le demande, peut-on imaginer une police sans sérifs ?

Posted

This is an actual test in both v1 and v2.

v1:

 

 

v2:

 

 

 

 

Hardware: Windows 11 Pro (23H2, build 22631.4317, Windows Feature Experience Pack 1000.22700.1041.0), Intel(R) Core(TM) i9-14900K, 32 Core@3.20 GHz, 128 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.