googlefonts / googlefonts/diffenator2

two usage questions on `--user-wordlist`

Open
#72 5 comments 0 reactions 1 assignee Claimed by @m4rc1e View on GitHub
Dominant language
Python
Stars
68
Forks
9
PR merge metrics
No merged PRs in 30d

Description

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

2. 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!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.