Jump to content

Search the Community

Showing results for tags 'afd-3020'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi, today I found, that there exist slightly different files for Open Sans v1.10. On one machine I've been working with a version obtained in April 2014 from Google Fonts (OpenSans-Regular.ttf, v1.10, 217360 bytes) and created an Assets Library that I shared with a colleague. That co-worker installed a recent Version from Google Fonts, and her OpenSans-Regular.ttf is also v1.10, but 217276 bytes, i.e. 84 bytes smaller. Now, AD won't render the assets correctly and substitutes the "missing" Font with Arial. I believe in this and similar cases AD should either automatically fall back on the identically named available font or ask the user for a substitution rule (like when opening PDFs). Regards, Chris
×
×
  • 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.