This is a simulation of the release workflow.
$ ./gotta-patch-em-all-font-patcher\!.sh -j /IntelOneMono
$ ./archive-fonts.sh IntelOneMono
$ git add ../../patched-fonts/IntelOneMono/
$ git commit -s -m 'Add IntelOne patched (i.e. just readme)' -e
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
In the previous commit we changed the way one line metric is choosen
when they do contradict.
This is the only font affected.
[how]
Just run gotta-patch-em. The font now uses TYPO (1000) and not WIN (1697)
anymore.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
After updating the template the concrete README.md's have not been
updated (forgotten).
[how]
Just call standardize-and-complete-readmes.sh
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
For some unknown reason some files have the execute right bit set in
git. That is neither needed nor recommended.
The *.cfg files are pulled in with `source`, so they do not need to be
executable.
[note]
Example command to check
find . -perm /111 -type f
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We have the same file in the repo, once with the ending 'TXT' and once
with the ending 'txt'.
This raises an issue on case-insensitive file systems.
[how]
The original in src/unpatched-fonts has the lower case ending.
So drop the capital letters one.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The JetBrains Mono family names are still broken.
The commit
b98c2a19 Fix JetBrains Mono Family names
did not do much, because it was not activated with gotta-patch-em.
The previous commit fixed that.
Put the fonts in the repo are still wrong. Repatching those gives a
chance to test them properly before v3.0.0.
[how]
Run gotta-patch-em with version set to v3.3.3-p6 because thats the git
status right now.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The previous commit
f240e073f (HEAD -> master, origin/master, origin/HEAD) font-patcher: Fix windows Mono family names with --makegroups
fixed a bug in teh font naming; instead of "NFM" the fonts were named
"NF Mono", which is wrong.
Affected are the fonts patched with --makegroups --mono --windows.
That means 1/4 of the fonts of
* Iosevka
* JetBrains Mono
* mononoki
* Cascadia Code
[how]
Run gotta-patch-em-all with FF 20230101 locally.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We never patched that fonts.
These are bitmap only fonts and we never touched them. We can keep them
for completeness in the src/unpatched-fonts/ProFont/profont-x11
directory, but the empty patched dir is somehow confusing.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[how]
./gotta-patch-em-all-font-patcher\!.sh /NerdFontsSymbolsOnly
Just add `Mono` variants to commit.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We do not want to rebuild all fonts, just the affected ones.
Without a proper release timestamp this is impossible (i.e. harder) to
do via CI, so do it manually 😬
[how]
./gotta-patch-em-all-font-patcher\!.sh /JetBrainsMono/Ligatures/ExtraLight
./gotta-patch-em-all-font-patcher\!.sh /JetBrainsMono/Ligatures/Light
Hmm, the patched fonts got slightly smaller. These font file sizes are a
mystery for me.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We have only a rather old 3270font: v1.2.23
This new font can be processed with current FontForge without problems.
And we have the benefit of an update.
[how]
Because the paths change (Medium->Regular etc) we need to purge the
patched-fonts/ directories manually. The automatic purging does work
only if at least the paths are kept.
[note]
https://github.com/rbanffy/3270fontFixes: #947
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This is a simulated CI run, because only Caskaydia Cove is affected all
the latest changes - and a complete run takes a ridiculous amount of
time.
Done via:
./gotta-patch-em-all-font-patcher\!.sh /CascadiaCode
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
