Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Texture healing doesn't work with frozen fonts

Ouverte
  • Quelque chose ne va pas ?
#406 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
22/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
python
Domaine
design

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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!

Langage dominant
Shell
Étoiles
19.7k
Forks
325
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/monaspace

Toutes les issues de githubnext/monaspace

Issues similaires

Plus d'issues Shell/Bash

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.