[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]
It can be hard to find out which license a particular font is using.
Therefore we add a new field to the fonts.json with an SPDX license
identifier (if possible).
[how]
For fonts with a license that has no SPDX identifier we use a free
`LicenseRef-*` identifier, but that reference is not solved in the
fonts.json file.
[note]
Also correct some licensing info given in the license audit.
Related: #1578
Suggested-by: Jan Christian Gruenhage <jan.christian@gruenhage.xyz>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This squashes also these commits:
* ds-store
* ZedMono: Clean up files
Remove files that should not be in the PR, because they are autocreated
or belong somewhere else.
* Also divide Extended and non-Extended versions.
* ZedMono: Fix metadata
* ZedMono: Fix some metadata
* ZedMono: Drop some more exotic weights and restructure dirs
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
'for Code' variants.
Rename RecMonoSemicausal to RecMonoSemi to avoid too long font names
after we add 'Nerd Font Mono' )or even (NFM) to it.
Fixes: #845
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Sqashed these commits:
* Remove Thin, Extra-Light, Semi-Bold and Heavy variants of IosevkaTermSlab
* Remove Thin, Extra-Light, Semi-Bold and Heavy files after unpacking
* No more subfolders per weight
* Revert commiting patched fonts
* Rewrite update scripts
* Update readme.md
[why]
The outlines in Terminus 4.49.2 are rather weird. Autoconverted but not
too nice.
[how]
Update to 4.49.3 as tis has much better outlines.
Fixes: #1329
Suggested-by: Wiesław Herr @herself
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
For new fonts we do not create one subdirectory for each font file anymore.
The (historic) reason were the many variants that each font file had been
patched with. Nowadays we just have 3 variants for each font file.
And anyhow this font is release archive released only.
[how]
Simplify update script and move font files.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Forgotten after update.
[note]
Also remove old old configure file that has been used for fast test
runs. It has the wrong format now anyhow.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
For testing we might want to execute one command (e.g. font-patcher run)
once for each source font. We need to decide which of the font files is
a good choice.
[how]
Best would maybe to use the font that is used for the image previews.
We add that information for each font into the 'database'. Then we can
for example do stuff like:
while IFS= read -d $'\n' -r f; do
ls -l ../../src/unpatched-fonts/"${f}"
done < <(jq -r '.fonts | .[] | ."imagePreviewFontSource"' lib/fonts.json)
This is already utilized for the helper tools that are hid in the
generate-font-image-previews.sh script.
Note that DaddyTimeMono and NerdFontSymbolsOnly has "--ext ttf" set in the
config, so the information provided for that fonts is wrong.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
History of the cask name:
It started as font-aurulentsansmono-nerd-font.rb, named by us (Nerd Font)
ecdf756a62
Then it has been dash-i-fied font-aurulent-sans-mono-nerd-font.rb
e8c2732486
Then just one year ago the Nerd Font release CI got an overhaul and I
(personally) put in font-aurulent-nerd-font.rb, despite the fact that I
did look up all cask names and put them into a 'database' in our CI:
c8cb5c7 casks: Hardcode cask names in fonts.json
[how]
Drop the wrong cask name (font-aurulent-nerd-font.rb) and use the more
correct and older one (casks: Hardcode cask names in fonts.json)
[note]
See also
https://github.com/Homebrew/homebrew-cask-fonts/pull/8704
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
After the working draft name Monispace the final patched font name will
be Monaspice.
* It keeps the characteristic `Mona` in the beginning
* It changes just one character
* The replacement is still a real word
* The replacements sounds very similar
Also other very good names have been suggested, thank you all for the
input!
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Monaspace has an RFN that individually protects 'Monaspace' and all the
face names of noble gases 'Xenon' etc. Both must not be used on patched
fonts.
[how]
Just add the rule(s). The concrete naming is not decided yet.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
SemiWide and ExtraWide might be nice in some contexts, but that is not
really the audience of Nerd Fonts I guess.
Lets start with few and we can always add more if there is really a
demand.
Simplify the paths; the old style stems from the time when we patched
all variants per source font. Nowerdays the fonts are few (3 per source)
and will almost always be installed together anyhow.
Shorten the naming a bit for, for example
ERROR: ====-< Family (ID 1) too long (37 > 31): MonaspaceXenon Nerd Font Propo Medium
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
We struggle with the pack-committing of patched fonts to the repository
on release. This makes our repo grow extremely big. It would be better
to just use release artifacts for the releases and not commit any
patched font back.
There were different approaches discussed, but the problem remains that
I personally have no rights to implement anything of that - neither can
I force push to the default branch, nor can I create new repos in the
organization.
[how]
To make it still possible to add new fonts without a repo size
explosion we do not release NEW fonts back to the repository as commits,
but old fonts are handled as before.
NEW fonts:
* have a new property set in the fonts.yaml 'database'
* are released as release artifact via release workflow (but not
committed back)
* get a readme in the patched_fonts/ directory that points to the
release artifact page
The solution is not ideal, but for sure better than not adding any fonts
anymore or having the repo grow in size faster and faster.
At some point in time I would like to phase out all in-repo releases,
also for OLD fonts.
This scheme has been (manually) used / introduced for Intel One.
With this change the .gitignore file is automatically adapted to any new
font that is added with the repoRelease flag set to false (which should
be the default for any added font from now on).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
