[why]
It is explicitely explained for updating fonts but not for new fonts.
[how]
Copy appropriate text passage to new fonts paragraph.
Fixes: #1655
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Often PRs introduce the legacy .../Bold/ etc subdirectory structure.
[how]
Make more clear that a flat directory is preferred.
Also fix several small glitches in the text.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
If we ever switch the default branch the links would break. So just say
'default branch' directly, whichever that may be.
[note]
CI workflows not changed, I do not know if there is an alias for the
default branch available.
Fixes: #971 (partially)
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Following issue #225 it seems fontforge has updated how it behaves after installing. For a consistent experience across
various operating systems (Ubuntu, macOS, etc), it seems we get better results by pre-pending `fontforge --script ..`
before running the `font-patcher` script.
