Hangman Posted June 8, 2023 Posted June 8, 2023 Hi @grabuge, So the issue with the roll up.pdf is the same as mentioned above in that for some unknown reason pixelart printing include a zero width no-break space at the start of most of the metadata fields, denoted by the Hex reference FEFF... The zoning.pdf has no Subject but again it does have a zero width no-break space which is causing the error when exporting the file... The workaround for both files is as @Patrick Connor and @Dan C mention above, to go to Window > References > Fields in Publisher (assuming you have Publisher), then mouse click in the Subject field, hit Delete followed by Enter, then both files will export to pdf... In case you don't have Publisher I've re-exported both pdf files and have attached them here, so hopefully these will work for you but if not just let us know... roll up export.pdf zoning export.pdf Patrick Connor 1 Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
Dan C Posted June 8, 2023 Posted June 8, 2023 Just to confirm, I've been able to replicate the information provided here and I've updated the development log regarding this - it also confirms that Publisher is able to create a PDF file which then fails on import, if the Subject Field is using one of these types of characters. Many thanks for your extra due diligence here @Hangman, it's certainly appreciated Quote
Hangman Posted June 8, 2023 Posted June 8, 2023 Hi @Dan C, That's no problem at all, hopefully, it will help with regard to fixing the issue now we know what's causing it in the first place... Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
Staff Affinity Info Bot Posted June 12, 2023 Staff Posted June 12, 2023 The issue "Fields Panel- clicking into each field and changing the contents without pressing enter causes the fields to clear when enter is next pressed in a field" (REF: AFB-7746) has been fixed by the developers in build "2.1.1.1847". 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 Quote
Staff Affinity Info Bot Posted June 12, 2023 Staff Posted June 12, 2023 The issue "User File - PDF imports with unsupported characters (þÿ) for the 'Subject' field, then fails to export out to PDF" (REF: AFB-7775) has been fixed by the developers in internal build "2.1.1.1847". 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. Quote
Staff Affinity Info Bot Posted June 14, 2023 Staff Posted June 14, 2023 Build 2.1.1 (build 1847) is now available as a Customer Beta We would appreciate you trying the beta build for yourself to check that the fix listed by Serif Info Bot above has been fixed for you. If it has NOT been fixed please post into the announcement post rather than here. Quote
Staff Affinity Info Bot Posted July 21, 2023 Staff Posted July 21, 2023 The issue "User File - PDF imports with unsupported characters (þÿ) for the 'Subject' field, then fails to export out to PDF" (REF: AFB-7775) has been fixed by the developers in internal build "2.2.0.1915". 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. Quote
Recommended Posts
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.