Jump to content

Search the Community

Showing results for tags 'umlaut'.

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 & Discussions
  • 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 3 results

  1. I have text on a flyer which contains umlaute. AD displays it correct. After export into a PDF the umlaute are replaced by a functional char (see attachment original and result). Of course I can rasterize all the text, but I don't want it in this case. I attached a printscreen from the export configuration as well. Thanks
  2. friends and neighbours, i just designed a nice little ad in affinity designer only to find out that the german "umlaute" i.e. ä,ü,ö, DO NOT show up in the pdf for print. they do show in affinity designer while i am working. what to do? or where do i have to change something because like this all my work was for naught. thanks for all the assistance you can give me, tomas anzeige_320x110.pdf
  3. When I try to save a new file to a path containing an Umlaut e.g. ~/Test Umläut/Test.affinity Affinity will crash and loose all changes to that file. This is bad. Please fix. Update: It's not the Umlaut that causes that problem. I sometimes get a permission error and once I get that permission error, I can't save or overwrite anywhere, not even in good old $HOME. I closed all my Documents and now it seems to work again. I will report back, once I can reproduce this problem.