Skip to content
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

Strange placement of the "tonos" above lowercase Greek eta in the Serif variant #551

Closed
sykde opened this issue Dec 27, 2023 · 2 comments
Closed

Comments

@sykde
Copy link

sykde commented Dec 27, 2023

In IBM Plex Serif, various diacritical marks above the lowercase Greek eta are placed unnaturally far to the left. Specifically, this problem seems to affect:

  • Greek lowercase letter eta with tonos (U+03AE, ή)
  • Greek lowercase letter and eta (U+03B7, η) with combining diacritical marks (e.g. U+0300, U+0301, U+0303)

This might have been intentional, as the tonos is also slightly offset to the left in the letter alpha tonos (U+03AC, ά), but unlike alpha tonos, in the case of eta tonos this feature is not persistent across other IBM Plex typefaces. Personal bias: It also looks strange...
image

In IBM Plex Sans, the tonos in eta tonos appears in the "normal" spot, near the middle of the letter's width.
image

The fonts affected seem to be all the variants of IBM Plex Serif. For the tests, only TTF files were used: IBMPlexSerif-*.ttf (Version 3.0.0, sfnt Revision 3, Release v6.3.0).
All tests were done in Windows 10/11, in Microsoft Word (Verson 2311, Build 17029.20068) and in FontForge (20230101).

@BoldMonday
Copy link
Collaborator

BoldMonday commented Jan 8, 2024

The placement of tonos to the left on eta in Plex Serif is intentional, and was advised by Irene Vlachou who consulted on the Greek design. Granted, Plex Sans has a slightly different approach. We might fix that in a future update.

Occassions where eta will be combined with Latin diacritics such as U+0303 are unknown to us, and therefore were not considered.

@sykde
Copy link
Author

sykde commented Jan 8, 2024

Since this was confirmed to be an intentional feature, I will be closing the issue. Thanks for the clarification!

@sykde sykde closed this as completed Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants