[why]
The fonts where we are allowed to keep the font name despite the RFN
clause in the license have nothing mentioning of RFN or the exception in
the readmes. But it is recommended (required?) by SIL to inform users of
that exception in a most transparent way.
[how]
Add that bit of information to the readme files in the patched-fonts
directories and the release archives.
[note]
Also some other information seemed to be missing, by the complete
rebuild of the readme it also got updated (Gohu/ProFont).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
With commit
23a14f184 Update Terminus to 4.49.3
we dropped the subdirectory structure of Terminus, but forgot to remove
that structure in the patched-fonts/ directory. The release will clear
the destination directory but not remove subdirectories, so we end up
with the 3.1.1 and 3.2.0 patched font files in the repo.
Luckily this is catched by the archiver process:
[Nerd Fonts] Limiting archive to pattern 'Terminus'
[Nerd Fonts] Packing Terminus.tar.xz (24 fonts)
[Nerd Fonts] Did not pack expected number of font files! Likely same font names for different paths.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
With commit
72c335de1 Update M PLUS
the fonts CodeLatin and CodeLatinExpanded got renamed to CodeLatin50 and
CodeLatin60. The old build artifacts still linger while the new fonts
were added.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
When we drop the subdirectories we probably need to clean
up the patched-fonts directory first, or the old font will
not be overwritten.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The subdirs will not be cleared/removed automatically, so we restructure
already now.
[how]
Move all files into the font-root dir.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We dropped the subdirectories and that might or might not be handled
gracefully by the release workflow.
[how]
Just flatten out of the in-repo release directory.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
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>
