-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assistant font switches 'if' for 'fi' on iOS (Chrome and Safari) #391
Comments
Thanks @joeforce :) I filed an issue on the upstream repo :) |
@joeforce I had the same problem then found this issue 😄 If you look at the Merriweather issue again, @davelab6 posted some workaround CSS that worked for me. |
+1 |
This is just source sans pro, please use that until this is fixed |
Is there any eta on this? @davelab6 what do you mean by just use sans pro? (apologies - I'm a font noob) |
The latin part of the family is (mean to be lol) an exact copy of Source Sans Pro. https://fonts.google.com/specimen/Source+Sans+Pro |
Having issues on iOS but not desktop. Posted it on Twitter here: |
@laerm0 can be hotfixed like playfair was, swapping the components |
Okay, I'll take care of it today. |
@laerm0 I'll take a look at this |
The family contains Hebrew so this may an issue with some browsers and how they handle RTL scripts (just an assumption, not fact). |
@joeforce I'll close this as none of us can reproduce, but please reopen if you can still see this happening |
I'm having an issue using Assistant. It works perfectly on Desktop, even responsively in the browser. But when I browse my page is Safari or Chrome (iOS 10) it switches if to fi. For example, "different" becomes "dfiferent" and "diffuse" becomes "dfifuse". I saw a similar issue with Merriweather sans:
#184
Is there any workaround? Changing the typeface this late in the game is going to be a lot of work.
Here's a sample of the spelling issue:
Also, if you search the page for "dfi" it doesn't find it. The font is rendering wrong and the word is actually spelled correctly.
Thanks!
Joe
The text was updated successfully, but these errors were encountered: