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

Search the Community

Showing results for tags 'encoding'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 2 results

  1. Hello, I am building my CV/Resume in Publisher and when exported as a PDF, it doesn't seem to matter which format I choose (Print, Digital, for export…) or the compatibility version (1.7, 1.6, 1.4…), once loaded into an applicant tracking software (ATS) scanner, like https://cultivatedculture.com/resume-scanner/ for instance, the text is not properly extracted and so the match between my CV and the job offer is pretty low (of course). The only reason that I found could be that the encoding software used by Affinity is incompatible, somehow, with this ATS technology. Indeed, once I upload my Affinity PDF into PDF Reader Pro Lite and save it as another PDF, the encoding software in the file info (cmd+i) changes from "PDFlib+PDI 9.2.1-j (macOS (x86_64))" for the Affinity file to "macOS version 12.6.1 (Build 21G217) Quartz PDFContext" for the PDF Reader Pro Lite file, which is read by the ATS scanner. The "Version" in the file info also changes from 1.7 to 1.4; but as I said, it doesn't matter as I've also tried to export it as a 1.4 file with Affinity Publisher to no more success. Does anyone know why this happens, if there is a way to fix this in Affinity, and if Serif is aware of this problem? P.S.: I attach the files in case people want to dig this issue. CV_PERRIER_Mickael_AlternanceUX [Affinity].pdf CV_PERRIER_Mickael_AlternanceUX [PDF Reader Pro Lite].pdf
  2. Would you be able to implement text encoding conversion of layer name on PSD import? Some of popular graphics app are still using non-utf so file made by them become gibberish in Affinity. Such as SAI which uses SJIS encoding. http://systemax.jp/en/sai/ Please check the sample on Photoshop so you can see correct result. SJIS AKA Shift_JIS https://en.wikipedia.org/wiki/Shift_JIS sai-psd-sample.psd
×
×
  • 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.