-
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
Update Playfair Display (to fix misaligned Latvian cedilla accents) #1188
Comments
laerm0
added
Priority 1 - Quick (Urgent and not Important)
-- Needs Upstream Resolution
Upstream fix required before moving forward
labels
Sep 6, 2017
@samwheat2020 You can download font files from the Playfair Display repo and host them on your own server. I tested those and they didn't have these issues. |
davelab6
modified the milestones:
Bugs in Font Files 01 Requires Upstream Resolution,
Update Families
Oct 5, 2017
davelab6
removed
the
-- Needs Upstream Resolution
Upstream fix required before moving forward
label
Oct 5, 2017
davelab6
changed the title
Playfair Display Latvian cedilla accents misaligned
Update Playfair Display (to fix misaligned Latvian cedilla accents)
Oct 5, 2017
Thanks for reporting this! |
Fixed in the current version, the issue should be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some combined diacritic characters in the Google Fonts version of Playfair Display are misaligned.
I see the issue in Latvian letters "ķ", "ļ", "ņ", and "ŗ".
As you can see, the cedillas are left-aligned and kerning is off around the affected characters.
Same issue has been reported for Romanian letters "ș" and "ț" in comments on #7 and I can confirm it.
To clarify, the misaligned Latvian diacritics are:
for Romanian:
There may be other combined characters with similar issues.
I already reported this issue via fonts.google.com feedback form but decided to investigate.
Apparently, the issue is not present in the https://github.com/clauseggers/Playfair-Display, so I'm reporting it here.
The text was updated successfully, but these errors were encountered: