-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Add Support for U+20C0 (SOM SIGN) #747
Comments
See also https://www.unicode.org/charts/PDF/U20A0.pdf |
It's not actually just underline, here is the proposal document with more details https://www.unicode.org/L2/L2020/20261-kyrgyz-som.pdf. But I'm also think that it's could be easy. |
@ravid-dubsteper yap, "c" is in fact a letter here, as its described in "... “C” of the Cyrillic alphabet with underlining ...". But its definitely should not sticking to cap height, the proposal from National Bank of Kyrgyz Republic is clearly illustrate it. |
Yup. The spec is very clear on the design. Case closed |
Would like to request the addition of U+20C0 (SOM SIGN) to the Inter font. This character is important for certain applications that require the representation of the SOM SIGN symbol (Kyrgyzstan country currency). Adding this character would enhance the usability of the Inter font across different contexts where this symbol is used.
Detailed information about unicode char here: https://www.unicodecharacter.org/U+20C0 and here: https://www.unicode.org/L2/L2020/20261-kyrgyz-som.pdf
Why this is important:
Currently, the Inter font does not support U+20C0, which makes it difficult for users who need to display this symbol in their projects. Incorporating it into the font will improve its versatility and ensure better support for a wider range of use cases.
Proposed solution:
Please, consider adding U+20C0 (SOM SIGN) to the font's character set in an upcoming release.
Additional context
The addition of this symbol would make Inter more suitable for applications and regions that require this character for proper display and usage.
The text was updated successfully, but these errors were encountered: