Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Texture healing doesn't work with frozen fonts

Abierto
#406 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
design

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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!

Lenguaje dominante
Shell
Estrellas
19.7k
Forks
325
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/monaspace

Todos los issues de githubnext/monaspace

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.