Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VF naming convention results in "Value is empty."

See original GitHub issue

Observed behaviour

4298 ± : fontbakery check-googlefonts Karla-Italic\[wght\].ttf                                                                                                   [37m] ✖ ✹ ✭
Validation of expected values failed:
fonts: Value is empty. (value: ())
usage: fontbakery check-googlefonts [-h] [-c CHECKID] [-x EXCLUDE_CHECKID]
                                    [-v] [-l LOGLEVEL] [-m LOGLEVEL_MESSAGES]
                                    [-n] [-C] [-S] [-L] [--json JSON_FILE]
                                    [--ghmarkdown MD_FILE] [--html HTML_FILE]
                                    [-g ITERATED_ARG] [-o ORDER]
                                    [fonts [fonts ...]]

Expected behaviour

Expectation is that fontbakery will run as usual.

Resources and exact process needed to replicate

fontbakery 0.7.8 any similarly named font file should work. i.e.

foofont-italic\[wdth\].ttf
typicalsans\[wght\].ttf

Issue Analytics

State:
Created 4 years ago
Comments:22 (20 by maintainers)

Top GitHub Comments

3reactions

m4rc1ecommented, Jun 26, 2019

brackets of death. https://github.com/google/fonts/issues/1817#issuecomment-477999366

I think everyone is well aware of the issue and they’ll find a solution soon.

1reaction

felipesanchescommented, Jul 10, 2019

Now you won’t need any further workarounds because I added a dirty hack to fontbakery source code itself. I dislike it. But that’s the best we can do for now. I hope we’ll soon have a different naming scheme so that I can remove the hack…