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

This bug is listed as fixed in the latest 2.3.0.2114 Beta, however, the issue remains and is in fact now worse in that placing a Password Protected PDF 2.0 file that includes certain ASCII 2-byte characters generally hangs Publisher. In the previous Beta, this didn't happen.

Quote
  • PDF 2.0 Passwords that include certain ASCII 2-Byte characters fail to display when placed in Affinity apps

The PDF still fails to display when placed in a Publisher Document but now double-clicking the placed PDF in the Layers Panel results in the Spinning Beachball and having to Force Quit Publisher.

Affinity Designer 2.4.0.2301 | Affinity Photo 2.4.0.2301 | Affinity Publisher 2.4.0.2301
Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.10.8
MacBook Pro 16GB, macOS Monterey 12.6.8

Link to comment
Share on other sites

  • Staff

Thanks, My release notes are wrong the fix for this was failed but I had already drafted the release notes. I will correct the release notes

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Link to comment
Share on other sites

3 minutes ago, Patrick Connor said:

Thanks, My release notes are wrong the fix for this was failed but I had already drafted the release notes. I will correct the release notes

No problem thanks for the clarification... :)

Affinity Designer 2.4.0.2301 | Affinity Photo 2.4.0.2301 | Affinity Publisher 2.4.0.2301
Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.10.8
MacBook Pro 16GB, macOS Monterey 12.6.8

Link to comment
Share on other sites

  • 3 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.