sudarmindamir Posted November 26, 2022 Share Posted November 26, 2022 When I switch the font color I used from the fill to the stroke color, I encounter this problem which looks odd. *notes 1. I'm currently using windows 11 version 22H2 (OS Build 22621.819 ) 2. This problem occurs only for some typfaces like Montserrat and Jakarta Plus Sans and some other fonts are still running normally 3. I encountered this problem when I was still using affinity designer V1 and it happened in V2 as well Quote Link to comment Share on other sites More sharing options...
firstdefence Posted November 26, 2022 Share Posted November 26, 2022 Working fine on Mac with Montseratt: Black with only a slight Tracking issue between the T & Y in the word AFFINITY This is a good way to take a screenshot when dealing with font issues, gives a lot of info and saves a lot of reply questions. Do you have any settings changed in the Character Panel? Can you upload that document as I have Montseratt installed and it works fine for me so would be interesting to see how your file behaves on my system. sudarmindamir 1 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
Brian_J Posted November 26, 2022 Share Posted November 26, 2022 I have the same issue with Montserrat on a Windows 10 computer. I have the most recent, static version of Montserrat from fonts.google.com. No character settings were changed. I haven't had this issue with other Google Fonts I use, like Open Sans and Roboto. Very odd. Maybe a difference in how Mac and Windows handle fonts that are designed however Montserrat is? Here's a screenshot and the AD file. Stroke Montserrat Font.afdesign sudarmindamir 1 Quote Link to comment Share on other sites More sharing options...
sudarmindamir Posted November 26, 2022 Author Share Posted November 26, 2022 59 minutes ago, firstdefence said: Working fine on Mac with Montseratt: Black with only a slight Tracking issue between the T & Y in the word AFFINITY This is a good way to take a screenshot when dealing with font issues, gives a lot of info and saves a lot of reply questions. Do you have any settings changed in the Character Panel? Can you upload that document as I have Montseratt installed and it works fine for me so would be interesting to see how your file behaves on my system. I dont have any settings changed, just a default version on character panel Quote Link to comment Share on other sites More sharing options...
sudarmindamir Posted November 26, 2022 Author Share Posted November 26, 2022 1 hour ago, firstdefence said: Working fine on Mac with Montseratt: Black with only a slight Tracking issue between the T & Y in the word AFFINITY This is a good way to take a screenshot when dealing with font issues, gives a lot of info and saves a lot of reply questions. Do you have any settings changed in the Character Panel? Can you upload that document as I have Montseratt installed and it works fine for me so would be interesting to see how your file behaves on my system. Montserrat_File_Windows Version.afdesign Quote Link to comment Share on other sites More sharing options...
Arakel Posted November 26, 2022 Share Posted November 26, 2022 No, it is not an OS issue. At my Win10 and Designer V1 and V2 the uploaded file is displayed correctly. Unfortunately, I have no idea why it is displayed incorrectly on your computer. Quote Link to comment Share on other sites More sharing options...
Brian_J Posted November 26, 2022 Share Posted November 26, 2022 3 minutes ago, Arakel said: No, it is not an OS issue. At my Win10 and Designer V1 and V2 the uploaded file is displayed correctly. @Arakel What version of Montserrat do you have? Quote Link to comment Share on other sites More sharing options...
firstdefence Posted November 26, 2022 Share Posted November 26, 2022 I cannot get the text to behave as the OP does, whether I expand to curves or just change from fill to stroke, I cannot get the font to go crazy with curves. The Big Text that looks corrupt, if you select the letter and use geometry add, it has the correct look, there are a few more nodes but it looks correct now. sudarmindamir 1 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
Arakel Posted November 26, 2022 Share Posted November 26, 2022 @Brian_J It's V7.200 (see picture) Quote Link to comment Share on other sites More sharing options...
Arakel Posted November 26, 2022 Share Posted November 26, 2022 OK, it seems to be a problem with the ttf font from google (Just tested). I do use otf from GitHub - JulietaUla/Montserrat Quote Link to comment Share on other sites More sharing options...
Brian_J Posted November 26, 2022 Share Posted November 26, 2022 5 minutes ago, Arakel said: OK, it seems to be a problem with the ttf font from google (Just tested). I do use otf from GitHub - JulietaUla/Montserrat Interesting. Thanks, good to know. Quote Link to comment Share on other sites More sharing options...
Brian_J Posted November 26, 2022 Share Posted November 26, 2022 I haven't tested the TTF fonts from https://github.com/JulietaUla/Montserrat. I'll do that another day unless someone beats me to it. I have Montserrat v8.000 (from fonts.google.com), and it looks like the most recent version on GitHub is 7.200. I'm wondering if the issue is TTF vs OTF or the font version. sudarmindamir 1 Quote Link to comment Share on other sites More sharing options...
firstdefence Posted November 26, 2022 Share Posted November 26, 2022 I have the 7.200 in TTF and it behaves fine for me. Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
firstdefence Posted November 26, 2022 Share Posted November 26, 2022 The issue is variable fonts; which Affinity does not support yet, using the static fonts for Montseratt works fine. sudarmindamir and Arakel 2 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
Arakel Posted November 26, 2022 Share Posted November 26, 2022 As written, it is a problem with the ttf from Google: sudarmindamir 1 Quote Link to comment Share on other sites More sharing options...
sudarmindamir Posted November 26, 2022 Author Share Posted November 26, 2022 1 hour ago, Arakel said: OK, it seems to be a problem with the ttf font from google (Just tested). I do use otf from GitHub - JulietaUla/Montserrat Thanks, the problem was solved by reinstalling the fonts with the montserrat V7.222 file from github as you suggested Arakel 1 Quote Link to comment Share on other sites More sharing options...
kenmcd Posted November 26, 2022 Share Posted November 26, 2022 On 11/25/2022 at 11:03 PM, sudarmindamir said: 2. This problem occurs only for some typfaces like Montserrat and Jakarta Plus Sans and some other fonts are still running normally 3. I encountered this problem when I was still using affinity designer V1 and it happened in V2 as well Those are the overlaps and looped corners used when creating fonts from multiple masters sources so the different styles interpolate properly. When Google Fonts uses their tools to build the fonts, they leave these overlaps in. Their position is that applications should handle this properly. To support variable fonts, the application must handle this properly. Almost all browsers now handle this correctly. Other desktop publishing applications handle this correctly. Static fonts in the original font developer repository usually remove the overlaps when they are generating the fonts from their font editor (they just check a box to remove the overlaps on export). This is why the static fonts from the original Montserrat repo have no overlaps. Affinity must fix this to be able to eventually support variable fonts. Variable fonts never remove the overlaps as they are required for correct interpolation. Brian_J, Arakel, firstdefence and 1 other 2 2 Quote Link to comment Share on other sites More sharing options...
firstdefence Posted November 26, 2022 Share Posted November 26, 2022 Thanks for the clarification @kenmcd kenmcd 1 Quote iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions Link to comment Share on other sites More sharing options...
David Gill Posted December 8, 2022 Share Posted December 8, 2022 Glad I found this thread. I love this font but it was driving me nuts! Hahaha, appreciate the help guys! The github font worked perfectly. kenmcd 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.