We flattened the {un,}patched-fonts directory structure.
But purging the destination directory with the new gotta-patch-em
option did not clean all up, so do it manually now.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This is just a correction of the commit message of commit
ca537ca01c SpaceMono: Remove fi/fl ligs
The paragraph regarding the 2 cell wide ligs is wrong. Just ignore it.
The ligature is 1 cell wide, but it takes two letters to create it, so
any vertical alignment will break. The issue mentioned in the
paragraph (which is not existing here) originates from ShareTechMono.
[note]
Change config.cfg slightly just to have a handle to find this commit via
`git log`, `git blame` or the likes.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
With commit
d501410 Update SpaceMono to 1.003
we have this statement
Ligatures moved into discretionary, so we do not need to remove them
anymore.
but it is wrong. The fi/fl ligatures moved into discretionary ONLY for
the Regular/Bold, but they are still ordinary ligatures in *Italic.
Which is a bug in the original/upstream font.
Furthermore when we crate the hard-monospaced Nerd Font Mono variant the
ligs will be shrunk to 1 cell wide, while the content of the `fi` lig is
of course two cells, ending up in strange overwriting issues.
[how]
Remove the `fl` and `fi` ligatures completely.
[note]
The arrow-calt rules did not resurface in neither Regular nor Italic.
Fixes: #2062
Reported-by: @kStor2poche
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
With #2054 we flattened the directory structure, see that PR.
But purging the destination directory with the new gotta-patch-em
option did not clean all up, so do it manually now.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
After #2054 the workflow has not been updated and tried to get the fonts
from the old locations.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
It went unnoticed now at least 2 times that a release is budgered
because the patch start and end have not been adjusted after expansions.
[how]
Add an --experimental feature that checks the actually patched-in number
of glyphs versus the number of glyphs claimed in the i_*.sh files.
If the new flag is given:
Output the findings. Abort run when mismatch.
Fixes: #2056
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
While the Devicon set has been expanded the codepoint for start and end
have not been adapted. So we have release v3.5.0 without the new
Devicons.
[how]
Take the correct number from i_cod.sh. Take offset into account.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
The previous change was not quite sufficient... a lot stuff has been
forgotten.
commit 6c5f2ad4 casks: Switch to tar.xz archives
Fixes#2041Fixes#1918
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This is so seldom used, what I want always changes.
Now we have a two step thing, that lists all stuff first
and after installing the fonts we can generate.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
generate-css.sh also creates glyphnames.json, and a current one of that
is needed for the font-patcher, i.e. gotta-patch-em
The font-patcher-zip release has been missing.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
I always struggle to get the artifacts downloaded when releasing,
because I usually need them before the release has been published. Then
the links are different and some authorization is needed.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
When the fonts or the subdirectory structure of a font is changed that
will leave some 'old' files and/or directories in the patched-fonts/
directory. The archiver will try to pack them all and bails out.
In fact on a RELEASE we can safely purge always, because the complete
structure will be regenerated anyhow. The problem with purging exists
only when working locally and patching only some font files.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
