Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Texture healing doesn't work with frozen fonts

Aperta
  • Qualcosa non va?
#406 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
design

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!

Lingua principale
Shell
Stelle
19.7k
Fork
325
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/monaspace

Tutte le issue di githubnext/monaspace

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.