Lam and alef presentation forms should not ligate #555
Comments
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?
Arabic presentation forms represent specific glyphs that are immune to contextual shaping. When a lam presentation form precedes an alef presentation form, they should not be ligated. To get a lam–alef ligature using presentation forms, you should use a character like U+FEFB ARABIC LIGATURE LAM WITH ALEF ISOLATED FORM.
Here is <U+FEDF, U+FE8E, U+FEDF, U+FE84, U+FEDF, U+FE88, U+FEDF, U+FE82, U+FEDF, U+FB51, U+FEDF, U+FD3C, U+FEE0, U+FE8E, U+FEE0, U+FE84, U+FEE0, U+FE88, U+FEE0, U+FE82, U+FEE0, U+FB51, U+FEE0, U+FD3C>:
It should look like this:
The text was updated successfully, but these errors were encountered: