fontbakery: VF naming convention results in "Value is empty."

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

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Comments: 22 (6 by maintainers)

Commits related to this issue

Most upvoted comments

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.

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…

I’ll see what I can do about it for now, though…