-
Notifications
You must be signed in to change notification settings - Fork 817
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
U+0615 ARABIC SMALL HIGH TAH is too low #543
Comments
These particular use cases appear to be specific to Qur'anic typesetting, and as Cascadia Code is not intended for that purpose, it will not be supported at this time. |
Why does Cascadia Code support U+0615 ARABIC SMALL HIGH TAH? Its only use is for Quranic typesetting. |
DHowett
pushed a commit
that referenced
this issue
Oct 29, 2021
This is a fairly comprehensive (and spooky!) 🐛💀 update resolving many open issues. ### Arabic bugfixes - [x] Closes #532 👻 - Additional positional variants added - [x] Closes #535 🍂 - Corrected hamza form - [x] Closes #540 🎃 - Dot arrangement corrected - [x] Closes #541 🧹 - Was due to the use of anchors on those glyphs. These have been removed so the glyph can render as spacing. - [x] Closes #542 🌕 - This was partly due to a [bug in Harfbuzz]. It has been resolved both on the font side (through a different implementation) and in Harfbuzz. - [x] Closes #549 🦸♀️ - Design corrected - [x] Closes #555 💀 - All letter glyphs removed from Arabic Presentation form unicode slots to avoid situations where the glyphs are not behaving as expected. - [x] Related to #543 - uni0615 removed as Cascadia Arabic not intended to support Quranic ### Other bug fixes - [x] Closes #488 🔪 - Finally made the www ligature have the proper number of `w`s. - [x] Closes #436 🧟♀️ - Extended length of Powerline 'caps' to avoid situations where rounding can prevent overlap. This may cause problems if the caps are used next to one another, but that seems an unlikely scenario given what I've reviewed of Powerline styles. - [x] Closes #521 🤖 - enlarged the size of the grave character to make it more recognizable / legible in code. - [x] Closes #524 ☠️ - Added some more differentiation in stroke, and also created more space using hinting. - [x] Closes #525 🧙♂️ - tweaked the braces to be more twisty and create better differentiation from the parens. - [x] Closes #529 🧛♀️ - Changed year :P - [x] Closes #546 👹 - ij no longer masquerading as a mark. - [x] Closes #563 🧟♂️ - corrected `locl` feature for proper Serbian rendering - [x] Closes #571 🦹♀️ - corrected overshoot - [x] Closes #572 🕷 - ratio symbol added - [x] Closes #577 🍁 - shifted heights of box drawing lines to better align with block glyphs. Will reduce risk of non-joining forms under certain conditions. [bug in harfbuzz]: harfbuzz/harfbuzz#3069 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cascadia family version
2106.17
Cascadia family variant(s)
Cascadia Code (the version with ligatures), Cascadia Mono (the version without ligatures)
Font file format(s)
.ttf (variable), .ttf (static), .otf (static)
Platform
macOS 10.14.6
Other Software
No response
What happened?
The glyph assigned to U+0615 ARABIC SMALL HIGH TAH was not designed for U+0615. It was clearly designed to be a component of glyphs for characters like U+0768 ARABIC LETTER NOON WITH SMALL TAH, but when it is used as its own character, it is positioned too low.
It overlaps other above-base marks. For example, here it is with U+064B ARABIC FATHATAN:
It also overlaps tall letters like kaf and lam.
U+0615 is a Quranic annotation sign, and as such should be placed at a constant high height, even if the base is short. For example, it should be at the same height above alef and beh.
For comparison, here is the same string in Amiri:
For another comparison, here a similar string in Noto Sans Arabic (it shows U+06D6 instead of U+0615 but the idea is the same):
The text was updated successfully, but these errors were encountered: