mirror of
https://github.com/ryanoasis/nerd-fonts.git
synced 2024-12-13 17:18:37 +02:00
328b8a2d22
[why] When we add a custom glyph (or want to update Seti) the process is rather laborious and we are needed to change the font and the accompanying `i_seti.sh` in sync. [how] We use a data file to map icon (svg) filenames to codepoints and readable names. That file is parsed and the font and info file is created (overwritten in the repo); and could then be easily committed. This can be a CI workflow. Having a dedicated mapping file (`icons.tsv`) enables us to have stable codepoints for the same symbol over time. Changes in codepoint allocation can be checked in git. Having the font autogenerated help guarantee that the icons are all likely scaled. We rescale them all to the same size and mid-position. That is not needed for font-patcher, because it rescales and shifts again based on to-be-patched font metrics. But it certainly is better for a view into the original-source font. Sizes and position are still roughly equivalent to the hand positioned glyphs. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de> |
||
---|---|---|
.. | ||
data | ||
Hack | ||
lib | ||
name_parser | ||
archive-font-patcher.sh | ||
archive-fonts.sh | ||
docker-entrypoint.sh | ||
fpfix.py | ||
generate-casks.sh | ||
generate-css.sh | ||
generate-font-image-previews.sh | ||
generate-fontconfig.sh | ||
generate-glyph-info-from-set.py | ||
generate-original-source.py | ||
get-font-names-from-json.sh | ||
gotta-patch-em-all-font-patcher!.sh | ||
README.md | ||
release.sh | ||
standardize-and-complete-readmes.sh | ||
test-fonts.sh | ||
test-powerlines.sh | ||
tests.sh | ||
update-all-contributors-website.py | ||
version-bump.sh |
Contents
Note: Usually you need to call the scripts in this directory while actually being in this directory (i.e. pwd = .../nerd-fonts/bin/scripts
).
archive-font-patcher.sh
: Archives the font patcher script and subscripts and the required source glyph files [1]archive-fonts.sh
: Creates the release zip file of one or more font(s) from existingpatched-fonts/
content [1]data/
: Contains plain text files used to generate the CSS and cheat sheet filesdata/sankey/
: Contains instructions on how to create the sankey glyph table manually [3]docker-entrypoint.sh
: This script is packaged into the docker container and is usually used to start patching [2]fpfix.py
: Can be used to set isFixedPitch property in a font [x]generate-casks.sh
: Generates cask files for fonts from data inpatched-fonts/
andarchives/
, unused and not recommended by homebrew-fontsgenerate-css.sh
: Generates the Nerd Fonts CCS, which can be used to access the glyphs on a web page [1]generate-fontconfig.sh
: Generates font configuration to enable use of unpatched fonts with Symbols Only Nerd Font [1]generate-font-image-previews.sh
: Generates the preview images fornerdfonts.com
(i.e. gh-pages) [3]generate-glyph-info-from-set.py
: Generate thei_xxx.sh
file from a glyph source (font) file, if the glyphs are named correctly [4]generate-original-source.py
: Generateoriginal-source.otf
from single glyph svgs. [3]get-font-names-from-json.sh
: Helper to setup the CI font matrix fromdata/fonts.json
[1]gotta-patch-em-all-font-patcher!.sh
: Patch one or more fonts 'complete' with and withoutmono
and with and withoutwindows compat
[1]Hack/
: Special additional post patching script for Hack, invoked via Hack'sconfig.cfg
(not used when self-patching)lib/
: See its own READMEname_parser/
: Suite to set up sane Family and SubFamily names, used byfont-patcher
(on demand)release.sh
: Rough process how a release is created, not used (see.github/workflows/release.yml
)standardize-and-complete-readmes.sh
[1]test-fonts.sh
: Print-to-debug all glyphs we patch in [4]test-powerlines.sh
: Print-to-debug powerline examples [4]tests.sh
: Create some font usage gif movie? [x]update-all-contributors-website.py
: Update the contributors page onnerdfonts.com
(i.e. gh-pages) (Hardcoded paths!) [3]version-bump.sh
: Change version number in all scripts on a new release [1]
[1] Used by CI (github release workflow) [2] Used by CI (github docker-release workflow) [3] To be used manually (sigh) [4] To be used manually [x] Probably not used by anything