Jump to content
You must now use your email address to sign in [click for more info] ×

PDF 2.0 Passwords That Include Certain ASCII 2-Byte Characters Fail to Display When Placed in Affinity Apps


Recommended Posts

When placing PDF 2.0 files exported from Affinity apps that include certain ASCII 2-byte UTF-8 characters in their Require password to open passwords, the PDF fails to display when placed in Affinity 2.3.0.2096 apps. If the respective files are placed as embedded files they will be correctly displayed once edited using Edit Document.

Opening the same PDF files using File > Open displays the PDF correctly as does opening the files directly using a PDF viewer...

The ASCII characters in question are highlighted in red in the table below...

Note: the ASCII characters 129, 141, 143, 144 and 157 are unused and character 160 is a Non-Breaking Space (NBSP) which doesn't appear possible to include as part of a PDF 2.0 password.

Steps to Reproduce

  1. Export a PDF 2.0 file from Publisher using a password made up of ASCII 2-byte characters including a selection of those characters highlighted in red e.g.,

    €‚ƒ„…
    ¡¢£¤¥¦§¨©ª«¬®¯
    °±²³´µ¶
     
  2. Place the exported PDF in a new Affinity Publisher document and the placed PDF shows as a blank page up until the point an edit is made to the PDF file.

ASCII 2-byte UTF-8 Characters that Cause a Placed Password Protected PDF 2.0 file to Display Incorrectly when Placed in Affinity Apps

ASCII2byteCharacters.thumb.png.af749984ad5c4e4b7014b354218ec6d5.png

 

It would be very helpful if anyone is able to test on Windows and iPad.

Affinity Designer 2.4.2 | Affinity Photo 2.4.2 | Affinity Publisher 2.4.2
Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.10.8
MacBook Pro 16GB, macOS Monterey 12.7.4, Magic Mouse

Link to comment
Share on other sites

  • 4 weeks later...
  • Staff

The issue "PDF 2.0 Passwords That Include Certain ASCII 2-Byte Characters Fail to Display When Placed in Affinity Apps" (REF: AF-1000) has been fixed by the developers in internal build "2.3.0.2150".
This fix should soon be available as a customer beta and 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 @Serif Info Bot to notify us.

Link to comment
Share on other sites

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.