When using [buildPlans.iosevka-custom.weights.bold] in private-build-plans.toml the build process finishes succesfully but there are no bold variants built

[wimstefan]

• Your font version: git dev commit f18c366
• Your font variant: customized Iosevka
• Your operating system (name and version): Gentoo ~amd64
• Your application using Iosevka: kitty, alacritty, awesomewm

If you have problem when building Iosevka, please provide these information:

• Your Node.js version: v13.12.0
• Your otfcc version: 0.10.3
• Your private-build-plans.toml, if present:

[buildPlans.iosevka-artesanal]
family = "Iosevka Artesanal"
design = [
  "artesanal",
  "sp-term",
  "v-f-tailed",
  "v-g-opendoublestorey",
  "v-i-serifed",
  "v-k-curly",
  "v-l-serifed",
  "v-q-taily",
  "v-m-shortleg",
  "v-r-top-serifed",
  "v-capital-r-curly",
  "v-eszet-traditional",
  "v-u-with-bar",
  "v-v-curly",
  "v-w-curly",
  "v-y-cursive",
  "v-capital-y-curly",
  "v-x-cursive",
  "v-zero-reverse-slashed",
  "v-three-flattop",  "v-seven-serifed",
  "v-tilde-high",
  "v-asterisk-high",
  "v-paragraph-high",
  "v-caret-high"
]
[buildPlans.iosevka-artesanal.weights.bold]
shape = 600
menu  = 600
css   = 600

• Your private.toml, paste if modified:

[artesanal]
slantAngle = 0
[s-italic]
slantAngle = 8
[s-oblique]
slantAngle = 8
[artesanal.multiplies]
sb = 0.90
width = 0.90

I've build my own customized font with the parameters above the issues as described in #473 and there is no bold variant built at all.

[be5invis]

[buildPlans.iosevka-artesanal.weights.bold]
shape = 600
menu  = 600
css   = 600

The menu entry will change the font's name and OS' weight identification, so software will think this font is "Semibold". To change shape only, do this:

[buildPlans.iosevka-artesanal.weights.bold]
shape = 600
menu  = 700
css   = 700

[be5invis]

If you are curious about why the "menu" option exists — this allows you to define new weights like Book and assign a weight like 450 to it.

[wimstefan]

Very interesting! Thanks for the explanation and your patience - I'm just a simple user who enjoys the possibility to customize his fonts ... unfortunately without completely understanding how it works 😔
I've also noticed that if you use a different weight definition than you have to define all weights otherwise just the weight defined is also built. That wasn't obvious to me when I read the Readme ...
Sorry for being so ignorant - I really try to do my best.

[be5invis]

@wimstefan
A weight definition in the configuration file will make the build system create files for one weight, and the parameters will decide in the built font files, how thick will the strokes be (shape field), how is it named (menu field), and what is the corresponded CSS weight if you decide to make the web font CSS (css field).
Yes the weight override needs to define all the weights, so you can build a subset of weights.
PRs are welcome to provide a better description.

[wimstefan]

Hmm perhaps it makes sense to add one more line like this:

  diff --git a/README.md b/README.md
  index 52e7e72..0e3f0e0 100644
  --- a/README.md
  +++ b/README.md
  @@ -84,6 +84,7 @@ Since version 2.0, Iosevka would no longer support building via `makefile`. To i
      # All weights would built and mapped to default shape/CSS
      # IMPORTANT : Currently "menu" property only support 100, 200, 300, 400, 450, 500, 600, 700, 800, 900.
      #              and "shape" properly only supports number between 100 and 900 (inclusive).
  +   #             *If* you decide to use custom weights you have to define all the weights you plan to use otherwise they will not be built.
      [buildPlans.iosevka-custom.weights.regular]
      shape = 400  # Weight for glyph shapes
      menu  = 400  # Weight for menu name