Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Texture healing doesn't work with frozen fonts

Offen
  • Stimmt etwas nicht?
#406 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
design

Rechercherichtung

The report compares texture healing (the calt feature) in a font frozen with FontFreeze against the shipped Monaspace fonts, so start by checking whether calt survives the freeze, using fonttools to inspect the GSUB lookups in both builds. The payload names no source files, so the freeze and build scripts in the repository are the places to look. Done means identifying why the frozen build loses the lookup and either fixing the freeze step or documenting a reliable workaround.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

I built frozen versions of the fonts with FontFreeze, since I wanted slashed zeros (a non-negotiable for me, dotted zeros suck 😉) locked in for the editors/apps that don't support font configuration/customization (which is most of them, unfortunately). I made sure to set calt to 1 when I did, along with the other features I wanted. Everything seems to work except for texture healing, which doesn't seem to work when I use the frozen fonts.

This is in Zed, using Neon Var:

Image

This is in Sublime Text, using Neon Var Frozen:

Image

Notice how the i and the m in minimus are different between the two screenshots.

I could try the frozen versions provided in the repo, but, as I said, slashed zeros are absolutely mandatory for me, so I wouldn't be able to use those.

So my question is, should I use a different freezing method (maybe whichever one you guys used when you created your frozen versions)? If so, which one?

FWIW: FontFreeze uses fonttools and, according to its README,

The way FontFreeze deactivates a feature is by removing all lookups inside it, and it activates a feature by moving all lookups in it into calt, which is usually activated by default in most environments. If this doesn't work for a particular environment, you may also try changing the "Target feature for activation" setting to rvrn (which is more forced than calt by the OpenType specification; note that in this case, you might also need to activate calt as well for some other features to function).

I did set "Target feature for activation" to rvrn, and calt was already activated, since it's what activates texture healing, but I'm wondering if that isn't the reason why texture healing seems to be the only feature that isn't working.

Thanks!

Vorherrschende Sprache
Shell
Sterne
19.7k
Forks
325
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/monaspace

Alle Issues in githubnext/monaspace

Ähnliche Issues

Weitere Issues zu Shell/Bash

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.