[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ligatures
From: |
Eli Zaretskii |
Subject: |
Re: Ligatures |
Date: |
Tue, 19 May 2020 19:41:50 +0300 |
> From: Pip Cet <address@hidden>
> Date: Tue, 19 May 2020 16:16:53 +0000
> Cc: address@hidden, address@hidden
>
> I think we need to fix the design first, moving a lot of C code out
> to Lisp
No, we don't need to fix the design of the display engine. We need to
design a new and different display engine, based on ideas more
flexible and powerful than the current rectangular array of glyphs.
You (or someone else) is more than welcome to work on such a new
design, present it here, discuss ideas, etc. If I can help, I will.
I will reserve my judgment on the "move to Lisp" part until I see the
overall design of this new engine, and at least some of the
implementation ideas, including how not to lose existing display
features.
By contrast, "fixing the design" of the current display engine, let
alone moving parts of it to Lisp, is IMNSHO a waste of effort. It
simply cannot be fixed, it's already stretched beyond limit. We can
(and do) make small adjustments, but that's all.
- Re: Ligatures, (continued)
- Re: Ligatures, Werner LEMBERG, 2020/05/19
- Re: Ligatures, tomas, 2020/05/19
- Re: Ligatures, Eli Zaretskii, 2020/05/19
- Re: Ligatures, Eli Zaretskii, 2020/05/19
- Re: Ligatures, Pip Cet, 2020/05/19
- Re: Ligatures, Eli Zaretskii, 2020/05/19
- Re: Ligatures, Pip Cet, 2020/05/19
- Re: Ligatures,
Eli Zaretskii <=
- Re: Ligatures, Eli Zaretskii, 2020/05/19
- Re: Unify the Platforms: Cairo+FreeType+Harfbuzz Everywhere (except TTY), Julius Pfrommer, 2020/05/17
- Re: Unify the Platforms: Cairo+FreeType+Harfbuzz Everywhere (except TTY), Eli Zaretskii, 2020/05/17
- Re: Unify the Platforms: Cairo+FreeType+Harfbuzz Everywhere (except TTY), chad, 2020/05/17
- Re: Unify the Platforms: Cairo+FreeType+Harfbuzz Everywhere (except TTY), Alan Third, 2020/05/18