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

two usage questions on `--user-wordlist`

Abierto
  • ¿Algo no está bien?
#72 5 comentarios 0 reacciones 1 asignado Ver en GitHub

@m4rc1e ya está trabajando en esto.

Desde el 4/7/2023.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Today is my first time trying out diffenator2. It is AWESOME. Really, it’s so useful. Thank you for making it!

I’m currently a little stuck on how to use custom wordlists. One thing I’d like to do is make a wordlist representing all the OT features in my font, and check those for each new version. So, I’ve started from the example in the readme, and updated that a bit:

a,latn,dflt,ss09
1/4,,,frac
10/23,,,frac
0123456789,,,numr,tnum,onum
DES,,,sups,ordn

This gives me two questions:

  1. Where does the wordlist output go? My expectation (without digging too deep) is that it would generate a file called something like “user-wordlist-proof.html”, or that it might be put into diffbrowsers_proofer.html or diffenator.html. But, I’m not seeing it anywhere. Do the strings only appear if they are specifically different/changed between versions? This is my current guess, but I kind of wish there were also a proof output to confirm that items in the user wordlist are working as expected, as that alone would be helpful.
image
  1. If I have a set of many words to proof for a given OT feature, do I have to repeat that line in the wordlist file for each of them? The answer in https://github.com/googlefonts/diffenator2/issues/69 seems to say so. But, in my example above, with the last line DES,,,sups,ordn, I’m really hoping to proof a set of ordinals. Ideally, I would want to proof a long string of them, ideally with a word spaced list, like the following: A C D E O R T Ú c d e r t ú AS DE DES DS EME ER ERE ERS ES GR IEME LLE ME ND OS RD RE RES ST STE TH as de des ds eme er ere ers es gr ieme lle me nd os rd re res st ste th. But, putting them onto one per line would be a bit inconvenient, especially because I have quite a few other features to also proof. Is there a better way? If not, that is understandable, and I’m partly just including this a user feedback.

Thanks again!

Lenguaje dominante
Python
Estrellas
71
Forks
9
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 googlefonts/diffenator2

Todos los issues de googlefonts/diffenator2

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.