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

Search the Community

Showing results for tags 'afb-3288'.

  • 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 (Serif 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.4 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 1 result

  1. Hi there, as a follow-up of my investigation into unencoded glyphs, here are some additional observations. There is an IDML (XML) context that isn’t still interpreted correctly. This is the original Indesign text frame containing some glyphs from Cambria Math and the IDML export (CS 5.5): M-phi-phi-salt.idml As you can see, I am using the standard phi (Unicode 03C6) from the Greek and Coptic block and phi salt (the common stylistic alternate). The IDML (XML) context for the latter one is: Publisher doesn’t interpret this context correctly, but displays the standard phi, not the stylistic alternate: Indesign reimports the file correctly. Please have a look! Alex
×
×
  • 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.