Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/microsoft/cascadia-code/issues/555 below:

Lam and alef presentation forms should not ligate · Issue #555 · microsoft/cascadia-code · GitHub

2106.17

Cascadia Code (the version with ligatures), Cascadia Mono (the version without ligatures)

.ttf (variable), .ttf (static), .otf (static)

macOS 10.14.6

No response

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:

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4