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

two usage questions on `--user-wordlist`

Aperta
  • Qualcosa non va?
#72 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@m4rc1e ci sta già lavorando.

Dal 4/7/2023.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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!

Lingua principale
Python
Stelle
69
Fork
9
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 googlefonts/diffenator2

Tutte le issue di googlefonts/diffenator2

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.