search

microsoft / cascadia-code

This is a fun, new monospaced font that includes programming ligatures and is designed to enhance the modern look and feel of the Windows Terminal.
Other
25.16k stars 797 forks source link

Lam and alef presentation forms should not ligate #555

Closed dscorbett closed 2 years ago

dscorbett commented 2 years ago

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: ﻟﺎﻟﺄﻟﺈﻟﺂﻟﭑﻟﴼﻠﺎﻠﺄﻠﺈﻠﺂﻠﭑﻠﴼ