Skip to content

Commit dec74bc

Browse files
committed
Work around bug in font-patcher --custom
[why] The --custom option seems to be broken for fonts with 'invalid' glyph, which most fonts that fontforge generates have. [how] Use sfd instead of ttf, where to invalid glyph is not added. Signed-off-by: Fini Jastrow <[email protected]>
1 parent e17f6dc commit dec74bc

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

do_generate

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ fi
2222
PWD=$( pwd )
2323

2424
rm -f C*.ttf
25-
fontforge -script "${PWD}/font-patcher" --careful "${3}" --custom "${PWD}/SomeExtraSymbols.otf" --no-progressbars "${PWD}/ttf/static/${4}" "${2}" --outputdir "${PWD}" | tee "process${1}.log"
25+
fontforge -script "${PWD}/font-patcher" --careful "${3}" --custom SomeExtraSymbols.sfd --no-progressbars "${PWD}/ttf/static/${4}" "${2}" --outputdir "${PWD}" | tee "process${1}.log"
2626

2727
if [ -z "${OURVERSION}" ]; then
2828
# Github CI sets this variable, but this can be useful for manual calls:

extract-extra-glyphs

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@ Open($2);
22
SelectAll();
33
SelectFewer(0u26A1);
44
Clear();
5-
Generate($1 + "/src/glyphs/SomeExtraSymbols.otf");
5+
Save($1 + "/src/glyphs/SomeExtraSymbols.sfd");

0 commit comments

Comments
 (0)