Jump to content

Search the Community

Showing results for tags 'afb-2696'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. The problem is pretty obvious when I go to print. I have a custom keyboard layout and I documented it using designer. Both Thai and European diacritical marks appear on the screen correctly. I'm trying to enter them in this message, but apparently the forum software is cringing at letting me enter them. I am referring to all of these: https://www.compart.com/en/unicode/bidiclass/NSM. Here's a screen cap of the European: https://i.imgur.com/bHHJQP1.png By comparison, here is Thai: https://i.imgur.com/UHV12gR.png Those are all correct on screen. But when I go to print those things, the European diacritics print properly, the Thai do not. Here is the printing of the previous European example: https://i.imgur.com/oqYYUEp.png and here is the Thai https://i.imgur.com/MNuhSrJ.png Actual file attached. keyboard layouts.afdesign
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.