mirror of
https://github.com/ryanoasis/nerd-fonts.git
synced 2024-12-07 17:06:25 +02:00
3c4fa008c1
[why] When working on the font-patcher the developer needs to test the changes on a number of fonts. This is usually a manual call of `font-patcher` and afterwards a 'diff' of the newly created font with the 'old' font in the patched-fonts/ directory with fontforge (which has a font-compare option). If you run gotta-patch-em-all normally the newly generated font will replace the existing font and git will ALWAYS show it as different. The reason is that at least the timestamp in the generated font has changed. Far more easy would be if the new gotta-patch-em-all run could keep the previous timestamps, in that way one can immediately see that the old and new fonts are bitwise equal (via git). Furthermore if you expect a change and want to show the differences of old and new font in fontforge you need both fonts in the filesystem. But a normal gotta-patch-em-all run replaces the font. A different destination folder would help here. [how] Introduce two new (independent) options to a) keep the timestamp equal to previous patch run b) generate the fonts in a different directory While b) is straight forward, a) is a bit more complicated, esp because filenames can change and so on. So the script examines just one (1) random font in the specific font directory and uses its timestamp. In most cases this is correct enough if the developer uses gotta-patch-em-all consequently. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
16 lines
292 B
Plaintext
16 lines
292 B
Plaintext
temp-glyph-source-fonts/*
|
|
temp/*
|
|
patched-fonts/Input*
|
|
check-fonts/*
|
|
unpatched-sample-fonts/Input*
|
|
casks/*
|
|
archives/*
|
|
private.cfg
|
|
node_modules
|
|
# Only apps should have lockfiles
|
|
package-lock.json
|
|
# generated *.uuid files
|
|
*.uuid
|
|
bin/scripts/name_parser/__pycache__/*
|
|
bin/scripts/name_parser/log
|