fonts/nerd-fonts
1
0
Fork 0
mirror of https://github.com/ryanoasis/nerd-fonts.git synced 2024-12-25 20:18:01 +02:00
Code Issues Releases Activity
9defc59b9d
nerd-fonts/bin/scripts/lib/fonts.json

535 lines
18 KiB
JSON
Raw Normal View History

Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
"fonts": [
{
Drop 'IBM' from 3270's names [why] The font was always called 3270. Having a big company's name in the fontname is scary :grimacing: See https://github.com/rbanffy/3270font/issues/60 [how] Add renaming rule. Fixes: #1012 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-17 16:40:52 +02:00
"unpatchedName": "IBM 3270",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "3270",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "3270",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"imagePreviewFont": "3270 Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "font3270",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "3270",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Derived from the x3270 font, a modern format of a font with high nostalgic value"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
{
"unpatchedName": "Agave",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"patchedName": "Agave",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Agave",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"imagePreviewFont": "Agave Nerd Font",
"linkPreviewFont": "agave",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "agave",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"description": "A small, monospace, outline font that is geometrically regular and simple"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Anonymous Pro",
"RFN": true,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Anonymice",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "AnonymousPro",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Anonymice Nerd Font",
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "anonymice",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Inspired by Anonymous 9 on Macintosh, since 2009, distinct `O`, `0`, `I`, `l`, `1`"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Arimo",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Arimo",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Arimo",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Arimo Nerd Font",
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "arimo",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Metrically similar to Arial, pan-European WGL character set, sans serif"
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Aurulent Sans Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "AurulentSansMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "AurulentSansMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "AurulentSansMono Nerd Font",
"linkPreviewFont": "aurulent",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "aurulent",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Sans serif, designed by Stephen G. Hartke which also created Verily Serif"
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "BigBlue Terminal",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "BigBlueTerminal",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "BigBlueTerminal",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "BigBlue_TerminalPlus Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "bigblue-terminal",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Nostalgic, closely based on IBM's 8x14 EGA/VGA charset"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Bitstream Vera Sans Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "BitstreamVeraSansMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "BitstreamVeraSansMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "BitstreamVeraSansMono Nerd Font",
"linkPreviewFont": "bitstream-vera",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "bitstream-vera-sans-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Dotted zero, compact lowercase characters"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
{
"unpatchedName": "Cascadia Code",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": true,
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"patchedName": "Caskaydia Cove",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "CascadiaCode",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"imagePreviewFont": "Caskaydia Cove Nerd Font",
"linkPreviewFont": "cascadia-code",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "caskaydia-cove",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"description": "A fun, new monospaced font that includes programming ligatures and is designed to enhance the modern look and feel of the Windows Terminal"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"unpatchedName": "IBM Plex Mono",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": true,
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"patchedName": "Blex Mono",
"folderName": "IBMPlexMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "BlexMono Nerd Font",
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "blex-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "It's global, it's versatile and it's distinctly IBM"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Code New Roman",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "CodeNewRoman",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "CodeNewRoman",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "CodeNewRoman Nerd Font",
"linkPreviewFont": "code-new-roman",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "code-new-roman",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Tunable, slashed zeros, compact smaller characters"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Cousine",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Cousine",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Cousine",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Cousine Nerd Font",
"linkPreviewFont": "cousine",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "cousine",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Similar to Courier New with better readablitiy, dotted zeros"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
{
"unpatchedName": "DaddyTimeMono",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"patchedName": "DaddyTimeMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "DaddyTimeMono",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"imagePreviewFont": "DaddyTimeMono Nerd Font",
"linkPreviewFont": "daddytimemono",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "daddy-time-mono",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"description": "A monospaced font for programmers and other terminal groupies"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "DejaVu Sans Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "DejaVuSansMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "DejaVuSansMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "DejaVuSansMono Nerd Font",
"linkPreviewFont": "dejavu",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "dejavu-sans-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Dotted zero, based on the Bitstream Vera Fonts with a wider range of character"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Droid Sans Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "DroidSansMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "DroidSansMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "DroidSansMono Nerd Font",
"linkPreviewFont": "droid-sans",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "droid-sans-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Good for small screens or font sizes"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Fantasque Sans Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "FantasqueSansMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "FantasqueSansMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "FantasqueSansMono Nerd Font",
"linkPreviewFont": "fantasque-sans",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "fantasque-sans-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "\"Wibbly-wobbly handwriting-like fuzziness\", takes some inspiration from Inconsolata and Monaco"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Fira Code",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "FiraCode",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "FiraCode",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "FiraCode Nerd Font",
"linkPreviewFont": "firacode",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "fira-code",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Programming ligatures, extension of Fira Mono font, enlarged operators"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
casks: Add unpatched fontname in cask description [why] People might want to know how the original/unpatched font really is called. This is done for most current casks. [how] Utilize jq and the fonts.json database to retrieve the name (which is stored nowhere else). Put it in the parens in the name field. Update some `unpatchedName`s. [note] Examples from current casks: homebrew-cask-fonts/Casks$ find . -name '*nerd-font*' -exec grep " name" {} \; | sort name "3270 Nerd Font (3270)" name "Agave Nerd Font (Agave)" name "Anonymice Nerd Font (Anonymous Pro)" name "Arimo Nerd Font (Arimo)" name "AurulentSansMono Nerd Font (Aurulent Sans Mono)" name "BigBlue_Terminal Nerd Font families (BigBlue Terminal)" name "BitstreamVeraSansMono Nerd Font (Bitstream Vera Sans Mono)" name "BlexMono Nerd Font (IBM Plex Mono)" name "CaskaydiaCove Nerd Font (Caskaydia code)" name "CodeNewRoman Nerd Font (Code New Roman)" name "Cousine Nerd Font (Cousine)" name "DaddyTimeMono Nerd Font (DaddyTimeMono)" name "DejaVuSansMono Nerd Font (DejaVu Sans Mono)" name "DroidSansMono Nerd Font (Droid Sans Mono)" name "FantasqueSansMono Nerd Font (Fantasque Sans Mono)" name "FiraCode Nerd Font (Fira Code)" name "FiraMono Nerd Font (Fira)" name "GohuFont Nerd Font (Gohu)" name "GoMono Nerd Font (Go)" name "Hack Nerd Font (Hack)" name "Hasklug Nerd Font (Hasklig)" name "HeavyData Nerd Font (Heavy Data)" name "Hurmit Nerd Font (Hermit)" name "iMWriting Nerd Font families (iA Writer)" name "InconsolataGo Nerd Font (Inconsolata Go)" name "InconsolataLGC Nerd Font (Inconsolata LGC)" name "Inconsolata Nerd Font (Inconsolata)" name "Iosevka Nerd Font (Iosevka)" name "JetBrainsMono Nerd Font (JetBrains Mono)" name "Lekton Nerd Font (Lekton)" name "Literation Nerd Font families (Liberation)" name "MesloLG Nerd Font families (Meslo LG)" name "Monofur Nerd Font (Monofur)" name "Monoid Nerd Font (Monoid)" name "Mononoki Nerd Font (Mononoki)" name "mplus Nerd Font (M+)" name "Nerd Font Symbols Template (Symbols Only)" name "Noto Nerd Font families (Noto)" name "OpenDyslexic Nerd Font families (OpenDyslexic)" name "Overpass Nerd Font (Overpass)" name "ProFont Nerd Font families (ProFont)" name "ProggyCleanTT Nerd Font families (ProggyCleanTT)" name "RobotoMono Nerd Font (RobotoMono)" name "SauceCodePro Nerd Font (Source Code Pro)" name "ShureTechMono Nerd Font (Share Tech Mono)" name "SpaceMono Nerd Font (Space Mono)" name "TerminessTTF Nerd Font (Terminus)" name "Tinos Nerd Font (Tinos)" name "UbuntuMono Nerd Font (Ubuntu Mono)" name "Ubuntu Nerd Font (Ubuntu)" name "VictorMono Nerd Font (Victor Mono)" Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-25 17:47:12 +02:00
"unpatchedName": "Fira",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "FiraMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "FiraMono",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "FuraMono Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "fira",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "fira-mono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Mozilla typeface, dotted zero"
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Go Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Go-Mono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Go-Mono",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "GoMono Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "go-mono",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "go-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Created specifically for the Go project, looks particularly clear for use with the Go language"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Gohu",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Gohu",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Gohu",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "GohuFont Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "gohufont",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Bitmap font, tall capitals and ascenders, small serifs"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Hack",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Hack",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Hack",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Hack Nerd Font",
"linkPreviewFont": "hack",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "hack",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Dotted zero, short descenders, expands upon work done for Bitstream Vera &amp; DejaVu, legible at common sizes"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Hasklig",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": true,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Hasklug",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Hasklig",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Hasklug Nerd Font",
"linkPreviewFont": "hasklig",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "hasklug",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Monospaced ligatures, makes composite glyphs (e.g. ->) more reabable, especially in Haskell"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Heavy Data",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "HeavyData",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "HeavyData",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "HeavyData Nerd Font",
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "heavy-data",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Novel and unique design, dotted zero"
},
{
"unpatchedName": "Hermit",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": true,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Hurmit",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Hermit",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Hurmit Nerd Font",
"linkPreviewFont": "hermit",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "hurmit",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Symbols stand out from common text"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
{
"unpatchedName": "iA Writer",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": true,
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"patchedName": "iM Writing",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "iA-Writer",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "iMWritingMonoS Nerd Font",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"linkPreviewFont": "ia-writer-mono",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "im-writing",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"description": "A heavy modification of IBM's Plex font"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
"unpatchedName": "Inconsolata",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Inconsolata",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Inconsolata",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Inconsolata Nerd Font",
"linkPreviewFont": "inconsolata",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "inconsolata",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Slashed zero, takes inspiration from many different fonts and glyphs, subtle curves in lowercase"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "InconsolataGo",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "InconsolataGo",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "InconsolataGo",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "InconsolataGo Nerd Font",
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "inconsolata-go",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Inconsolata with straight quotes"
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Inconsolata LGC",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "InconsolataLGC",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "InconsolataLGC",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "InconsolataLGC Nerd Font",
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "inconsolata-lgc",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Inconsolata with added the Cyrillic alphabet"
},
{
"unpatchedName": "Iosevka",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Iosevka",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Iosevka",
IosevkaTerm: Prepare gh-pages for change Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-04-05 16:02:47 +02:00
"imagePreviewFont": "Iosevka Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "iosevka",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "iosevka",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Narrow and horizontally tight characters, slashed zero"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
IosevkaTerm: Prepare gh-pages for change Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-04-05 16:02:47 +02:00
{
"unpatchedName": "Iosevka Term",
"RFN": false,
"patchedName": "IosevkaTerm",
"folderName": "IosevkaTerm",
"imagePreviewFont": "IosevkaTerm Nerd Font",
"linkPreviewFont": "false",
"caskName": "iosevka-term",
"description": "A narrower variant focusing terminal uses: Arrows and geometric symbols will be narrow to follow typical terminal usages"
},
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "JetBrains Mono",
"RFN": false,
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"patchedName": "JetBrainsMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "JetBrainsMono",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"imagePreviewFont": "JetBrainsMono Nerd Font",
"linkPreviewFont": "jetbrainsmono",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "jetbrains-mono",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"description": "JetBrains officially created font for developers"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
"unpatchedName": "Lekton",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Lekton",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Lekton",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Lekton Nerd Font",
"linkPreviewFont": "lekton",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "lekton",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Very light and thin characters, sharp m's, `0` and `O` very similar"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
casks: Add unpatched fontname in cask description [why] People might want to know how the original/unpatched font really is called. This is done for most current casks. [how] Utilize jq and the fonts.json database to retrieve the name (which is stored nowhere else). Put it in the parens in the name field. Update some `unpatchedName`s. [note] Examples from current casks: homebrew-cask-fonts/Casks$ find . -name '*nerd-font*' -exec grep " name" {} \; | sort name "3270 Nerd Font (3270)" name "Agave Nerd Font (Agave)" name "Anonymice Nerd Font (Anonymous Pro)" name "Arimo Nerd Font (Arimo)" name "AurulentSansMono Nerd Font (Aurulent Sans Mono)" name "BigBlue_Terminal Nerd Font families (BigBlue Terminal)" name "BitstreamVeraSansMono Nerd Font (Bitstream Vera Sans Mono)" name "BlexMono Nerd Font (IBM Plex Mono)" name "CaskaydiaCove Nerd Font (Caskaydia code)" name "CodeNewRoman Nerd Font (Code New Roman)" name "Cousine Nerd Font (Cousine)" name "DaddyTimeMono Nerd Font (DaddyTimeMono)" name "DejaVuSansMono Nerd Font (DejaVu Sans Mono)" name "DroidSansMono Nerd Font (Droid Sans Mono)" name "FantasqueSansMono Nerd Font (Fantasque Sans Mono)" name "FiraCode Nerd Font (Fira Code)" name "FiraMono Nerd Font (Fira)" name "GohuFont Nerd Font (Gohu)" name "GoMono Nerd Font (Go)" name "Hack Nerd Font (Hack)" name "Hasklug Nerd Font (Hasklig)" name "HeavyData Nerd Font (Heavy Data)" name "Hurmit Nerd Font (Hermit)" name "iMWriting Nerd Font families (iA Writer)" name "InconsolataGo Nerd Font (Inconsolata Go)" name "InconsolataLGC Nerd Font (Inconsolata LGC)" name "Inconsolata Nerd Font (Inconsolata)" name "Iosevka Nerd Font (Iosevka)" name "JetBrainsMono Nerd Font (JetBrains Mono)" name "Lekton Nerd Font (Lekton)" name "Literation Nerd Font families (Liberation)" name "MesloLG Nerd Font families (Meslo LG)" name "Monofur Nerd Font (Monofur)" name "Monoid Nerd Font (Monoid)" name "Mononoki Nerd Font (Mononoki)" name "mplus Nerd Font (M+)" name "Nerd Font Symbols Template (Symbols Only)" name "Noto Nerd Font families (Noto)" name "OpenDyslexic Nerd Font families (OpenDyslexic)" name "Overpass Nerd Font (Overpass)" name "ProFont Nerd Font families (ProFont)" name "ProggyCleanTT Nerd Font families (ProggyCleanTT)" name "RobotoMono Nerd Font (RobotoMono)" name "SauceCodePro Nerd Font (Source Code Pro)" name "ShureTechMono Nerd Font (Share Tech Mono)" name "SpaceMono Nerd Font (Space Mono)" name "TerminessTTF Nerd Font (Terminus)" name "Tinos Nerd Font (Tinos)" name "UbuntuMono Nerd Font (Ubuntu Mono)" name "Ubuntu Nerd Font (Ubuntu)" name "VictorMono Nerd Font (Victor Mono)" Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-25 17:47:12 +02:00
"unpatchedName": "Liberation",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": true,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "LiterationMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "LiberationMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "LiterationMono Nerd Font",
"linkPreviewFont": "liberation",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "liberation",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "`0` and `O` very similar, very short tight descenders"
},
CI: Add Lilex to release [why] Lilex is missing from the 2.2.0 RC and is not automagically patched. [how] Add Lilex to the font metadata database :-> [note] Lilex's licence has no RFN given. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-08-20 17:05:25 +02:00
{
"unpatchedName": "Lilex",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
CI: Add Lilex to release [why] Lilex is missing from the 2.2.0 RC and is not automagically patched. [how] Add Lilex to the font metadata database :-> [note] Lilex's licence has no RFN given. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-08-20 17:05:25 +02:00
"patchedName": "Lilex",
"folderName": "Lilex",
"imagePreviewFont": "Lilex Nerd Font",
"linkPreviewFont": "lilex",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "lilex",
CI: Add Lilex to release [why] Lilex is missing from the 2.2.0 RC and is not automagically patched. [how] Add Lilex to the font metadata database :-> [note] Lilex's licence has no RFN given. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-08-20 17:05:25 +02:00
"description": "Modern with ligatures"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
fonts.json: Correct Meslo name [why] It is in fact Meslo LG that we consume and produce. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-29 15:49:55 +02:00
"unpatchedName": "Meslo LG",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
fonts.json: Correct Meslo name [why] It is in fact Meslo LG that we consume and produce. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-29 15:49:55 +02:00
"patchedName": "MesloLG",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Meslo",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "MesloLGM Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "meslo",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "meslo-lg",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Slashed zeros, customized version of Apple's Menlo"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Monofur",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Monofur",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Monofur",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Monofur Nerd Font",
"linkPreviewFont": "monofur",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "monofur",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Dotted zeros, slightly exaggerated curvy characters, compact characters"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Monoid",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Monoid",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Monoid",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Monoid Nerd Font",
"linkPreviewFont": "monoid",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "monoid",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Ligatures, distinguishable glyphs with short ascenders &amp; descenders, large operators &amp; punctuation"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
"unpatchedName": "Mononoki",
Update mononoki to 1.5 Mononoki is now a RFN; but under conditions mentioned in [1] we can use that name for the patched font. [1] https://github.com/ryanoasis/nerd-fonts/issues/575#issuecomment-1385308049 Fixes: #575 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-17 14:28:27 +02:00
"RFN": true,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Mononoki",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Mononoki",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Mononoki Nerd Font",
"linkPreviewFont": "mononoki",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "mononoki",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Keeps in mind differentiation of characters and resolution sizes"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "M+",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "MPlus",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "MPlus",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "M+ 1m",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "mplus",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Multiple styles and weights, many glyph sets (e.g. Kana glyphs)"
},
{
"unpatchedName": "Noto",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Noto",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Noto",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "NotoSansMono Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "noto",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "noto",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "`0` and `O` very similar, characters are either very curvy or straight lined"
},
{
"unpatchedName": "ProFont",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "ProFont",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "ProFont",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "ProFontIIx Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "profont",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "profont",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Looks best with anti-aliasing turned off, squared off character corners, vertically tight small `s`"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
casks: Add unpatched fontname in cask description [why] People might want to know how the original/unpatched font really is called. This is done for most current casks. [how] Utilize jq and the fonts.json database to retrieve the name (which is stored nowhere else). Put it in the parens in the name field. Update some `unpatchedName`s. [note] Examples from current casks: homebrew-cask-fonts/Casks$ find . -name '*nerd-font*' -exec grep " name" {} \; | sort name "3270 Nerd Font (3270)" name "Agave Nerd Font (Agave)" name "Anonymice Nerd Font (Anonymous Pro)" name "Arimo Nerd Font (Arimo)" name "AurulentSansMono Nerd Font (Aurulent Sans Mono)" name "BigBlue_Terminal Nerd Font families (BigBlue Terminal)" name "BitstreamVeraSansMono Nerd Font (Bitstream Vera Sans Mono)" name "BlexMono Nerd Font (IBM Plex Mono)" name "CaskaydiaCove Nerd Font (Caskaydia code)" name "CodeNewRoman Nerd Font (Code New Roman)" name "Cousine Nerd Font (Cousine)" name "DaddyTimeMono Nerd Font (DaddyTimeMono)" name "DejaVuSansMono Nerd Font (DejaVu Sans Mono)" name "DroidSansMono Nerd Font (Droid Sans Mono)" name "FantasqueSansMono Nerd Font (Fantasque Sans Mono)" name "FiraCode Nerd Font (Fira Code)" name "FiraMono Nerd Font (Fira)" name "GohuFont Nerd Font (Gohu)" name "GoMono Nerd Font (Go)" name "Hack Nerd Font (Hack)" name "Hasklug Nerd Font (Hasklig)" name "HeavyData Nerd Font (Heavy Data)" name "Hurmit Nerd Font (Hermit)" name "iMWriting Nerd Font families (iA Writer)" name "InconsolataGo Nerd Font (Inconsolata Go)" name "InconsolataLGC Nerd Font (Inconsolata LGC)" name "Inconsolata Nerd Font (Inconsolata)" name "Iosevka Nerd Font (Iosevka)" name "JetBrainsMono Nerd Font (JetBrains Mono)" name "Lekton Nerd Font (Lekton)" name "Literation Nerd Font families (Liberation)" name "MesloLG Nerd Font families (Meslo LG)" name "Monofur Nerd Font (Monofur)" name "Monoid Nerd Font (Monoid)" name "Mononoki Nerd Font (Mononoki)" name "mplus Nerd Font (M+)" name "Nerd Font Symbols Template (Symbols Only)" name "Noto Nerd Font families (Noto)" name "OpenDyslexic Nerd Font families (OpenDyslexic)" name "Overpass Nerd Font (Overpass)" name "ProFont Nerd Font families (ProFont)" name "ProggyCleanTT Nerd Font families (ProggyCleanTT)" name "RobotoMono Nerd Font (RobotoMono)" name "SauceCodePro Nerd Font (Source Code Pro)" name "ShureTechMono Nerd Font (Share Tech Mono)" name "SpaceMono Nerd Font (Space Mono)" name "TerminessTTF Nerd Font (Terminus)" name "Tinos Nerd Font (Tinos)" name "UbuntuMono Nerd Font (Ubuntu Mono)" name "Ubuntu Nerd Font (Ubuntu)" name "VictorMono Nerd Font (Victor Mono)" Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-25 17:47:12 +02:00
"unpatchedName": "ProggyCleanTT",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "ProggyClean",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "ProggyClean",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "ProggyCleanTT Nerd Font",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"linkPreviewFont": "proggy-clean",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "proggy-clean-tt",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Designed particularly for use at small point sizes"
},
{
"unpatchedName": "OpenDyslexic",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "OpenDyslexic",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "OpenDyslexic",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "OpenDyslexic Nerd Font",
"linkPreviewFont": "opendyslexic",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "open-dyslexic",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Designed specifically to alleviate reading errors caused by dyslexia"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
{
"unpatchedName": "Overpass",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"patchedName": "Overpass",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Overpass",
Fix font previews [why] Some font previews in the gh-pages are obviously wrong (showing some fallback font). [how] Recreate all image previes from current master branch. To make this more easy: - Add commented out code that displays command to install just the needed fonts but all the needed fonts - Add commented out code that displays the family names of the needed fonts - these have to be in sync with the fonts.json database Fixes: #489 Reported-by: CosmosAtlas Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2023-01-30 08:55:58 +02:00
"imagePreviewFont": "OverpassMono Nerd Font",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"linkPreviewFont": "overpass",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "overpass",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"description": "An open source font family inspired by Highway Gothic"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Roboto Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "RobotoMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "RobotoMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "RobotoMono Nerd Font",
"linkPreviewFont": "roboto",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "roboto-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Dashed zero, curved and straight character lines"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Share Tech Mono",
"RFN": true,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "ShureTechMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "ShareTechMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "ShureTechMono Nerd Font",
"linkPreviewFont": "share-tech",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "shure-tech-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Dotted zeros, distinguishable 1 and l, curved and straight character lines"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Source Code Pro",
"RFN": true,
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"patchedName": "SauceCodePro",
"folderName": "SourceCodePro",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"imagePreviewFont": "Sauce Code Pro Nerd Font",
"linkPreviewFont": "source-code-pro",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "sauce-code-pro",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"description": "Monospaced font family for user interface and coding environments"
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Space Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "SpaceMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "SpaceMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "SpaceMono Nerd Font",
"linkPreviewFont": "space",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "space-mono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Squarish character lines, dotted zero, aggressive parethesis"
},
Improves structure and hopefully automated patching of symbol only nerd font variations * relates to issues #479 #668
2021-12-11 23:35:07 +02:00
{
casks: Add unpatched fontname in cask description [why] People might want to know how the original/unpatched font really is called. This is done for most current casks. [how] Utilize jq and the fonts.json database to retrieve the name (which is stored nowhere else). Put it in the parens in the name field. Update some `unpatchedName`s. [note] Examples from current casks: homebrew-cask-fonts/Casks$ find . -name '*nerd-font*' -exec grep " name" {} \; | sort name "3270 Nerd Font (3270)" name "Agave Nerd Font (Agave)" name "Anonymice Nerd Font (Anonymous Pro)" name "Arimo Nerd Font (Arimo)" name "AurulentSansMono Nerd Font (Aurulent Sans Mono)" name "BigBlue_Terminal Nerd Font families (BigBlue Terminal)" name "BitstreamVeraSansMono Nerd Font (Bitstream Vera Sans Mono)" name "BlexMono Nerd Font (IBM Plex Mono)" name "CaskaydiaCove Nerd Font (Caskaydia code)" name "CodeNewRoman Nerd Font (Code New Roman)" name "Cousine Nerd Font (Cousine)" name "DaddyTimeMono Nerd Font (DaddyTimeMono)" name "DejaVuSansMono Nerd Font (DejaVu Sans Mono)" name "DroidSansMono Nerd Font (Droid Sans Mono)" name "FantasqueSansMono Nerd Font (Fantasque Sans Mono)" name "FiraCode Nerd Font (Fira Code)" name "FiraMono Nerd Font (Fira)" name "GohuFont Nerd Font (Gohu)" name "GoMono Nerd Font (Go)" name "Hack Nerd Font (Hack)" name "Hasklug Nerd Font (Hasklig)" name "HeavyData Nerd Font (Heavy Data)" name "Hurmit Nerd Font (Hermit)" name "iMWriting Nerd Font families (iA Writer)" name "InconsolataGo Nerd Font (Inconsolata Go)" name "InconsolataLGC Nerd Font (Inconsolata LGC)" name "Inconsolata Nerd Font (Inconsolata)" name "Iosevka Nerd Font (Iosevka)" name "JetBrainsMono Nerd Font (JetBrains Mono)" name "Lekton Nerd Font (Lekton)" name "Literation Nerd Font families (Liberation)" name "MesloLG Nerd Font families (Meslo LG)" name "Monofur Nerd Font (Monofur)" name "Monoid Nerd Font (Monoid)" name "Mononoki Nerd Font (Mononoki)" name "mplus Nerd Font (M+)" name "Nerd Font Symbols Template (Symbols Only)" name "Noto Nerd Font families (Noto)" name "OpenDyslexic Nerd Font families (OpenDyslexic)" name "Overpass Nerd Font (Overpass)" name "ProFont Nerd Font families (ProFont)" name "ProggyCleanTT Nerd Font families (ProggyCleanTT)" name "RobotoMono Nerd Font (RobotoMono)" name "SauceCodePro Nerd Font (Source Code Pro)" name "ShureTechMono Nerd Font (Share Tech Mono)" name "SpaceMono Nerd Font (Space Mono)" name "TerminessTTF Nerd Font (Terminus)" name "Tinos Nerd Font (Tinos)" name "UbuntuMono Nerd Font (Ubuntu Mono)" name "Ubuntu Nerd Font (Ubuntu)" name "VictorMono Nerd Font (Victor Mono)" Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-25 17:47:12 +02:00
"unpatchedName": "Symbols Only",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
generate-font-image-previews: Generate Symbols Only preview [why] We do not have a preview for the Symbols Only font. The Symbols Only font appears two times (with 1000 and with 2048 EM). [how] Remove one of the occurences of NerdFontSymbolsOnly in the fonts.json. The font matrix (for CI) still works, and we get only one entry in the fonts list on the gh-pages. Change the entry details accordingly. Create special svg template that includes lots of symbols. Change the destination filename to be imagePreviewFont instead of the patchedName + "Nerd Font". The website (gh-pages) expects the former file names. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-12-19 18:10:38 +02:00
"patchedName": "Symbols",
Improves structure and hopefully automated patching of symbol only nerd font variations * relates to issues #479 #668
2021-12-11 23:35:07 +02:00
"folderName": "NerdFontsSymbolsOnly",
generate-font-image-previews: Generate Symbols Only preview [why] We do not have a preview for the Symbols Only font. The Symbols Only font appears two times (with 1000 and with 2048 EM). [how] Remove one of the occurences of NerdFontSymbolsOnly in the fonts.json. The font matrix (for CI) still works, and we get only one entry in the fonts list on the gh-pages. Change the entry details accordingly. Create special svg template that includes lots of symbols. Change the destination filename to be imagePreviewFont instead of the patchedName + "Nerd Font". The website (gh-pages) expects the former file names. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-12-19 18:10:38 +02:00
"imagePreviewFont": "Symbols Nerd Font Mono",
Improves structure and hopefully automated patching of symbol only nerd font variations * relates to issues #479 #668
2021-12-11 23:35:07 +02:00
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "symbols-only",
generate-font-image-previews: Generate Symbols Only preview [why] We do not have a preview for the Symbols Only font. The Symbols Only font appears two times (with 1000 and with 2048 EM). [how] Remove one of the occurences of NerdFontSymbolsOnly in the fonts.json. The font matrix (for CI) still works, and we get only one entry in the fonts list on the gh-pages. Change the entry details accordingly. Create special svg template that includes lots of symbols. Change the destination filename to be imagePreviewFont instead of the patchedName + "Nerd Font". The website (gh-pages) expects the former file names. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-12-19 18:10:38 +02:00
"description": "Just the Nerd Font Icons. I.e Symbol font only"
Improves structure and hopefully automated patching of symbol only nerd font variations * relates to issues #479 #668
2021-12-11 23:35:07 +02:00
},
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
{
"unpatchedName": "Terminus",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": true,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Terminess",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Terminus",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "TerminessTTF Nerd Font",
"linkPreviewFont": "terminus",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "terminess-ttf",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Squarish characters that are slightly askew"
},
{
"unpatchedName": "Tinos",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Tinos",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Tinos",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Tinos Nerd Font",
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "tinos",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"description": "Some similarities to Times New Roman, designed by Steve Matteson, includes pan-European WGL character set"
},
{
"unpatchedName": "Ubuntu",
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "Ubuntu",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "Ubuntu",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "Ubuntu Nerd Font",
Remove wrong "Ubuntu" font preview link [why] Both, Ubuntu and Ubuntu Mono link to the #Ubuntu preview on ProgrammingFonts.org. But that ends up in Ubuntu Mono. You can not preview the proportional version. [note] This commit must be synched to branch gh-pages manually. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 15:52:17 +02:00
"linkPreviewFont": false,
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "ubuntu",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Specially created for Ubuntu"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Ubuntu Mono",
"RFN": false,
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"patchedName": "UbuntuMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "UbuntuMono",
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
"imagePreviewFont": "UbuntuMono Nerd Font",
"linkPreviewFont": "ubuntu",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "ubuntu-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Dotted zeros, used the `n`, `o`, `H` &amp; `O` Latin characters as a base for design"
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
},
{
doc: Fix RFN entries in readme [skip ci] [why] Some fonts in the readme source font tables are marked as 'no RFN' while they infact have a RFN (and we act on that, so that is just a documentation issue). [how] Also add updated fonts.json, that contains RFN information and correct unpatchedFont names, compare gh-pages commit 4f78d656 download: Fix RFN detection The updated fonts.json is also needed for an upcoming Casks creation fix. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 13:50:39 +02:00
"unpatchedName": "Victor Mono",
"RFN": false,
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"patchedName": "VictorMono",
Setup matrix for actions
2021-11-26 16:46:46 +02:00
"folderName": "VictorMono",
Updates image preview names to match the generated ones
2020-04-06 10:01:32 +02:00
"imagePreviewFont": "VictorMono Nerd Font",
"linkPreviewFont": "victor-mono",
casks: Hardcode cask names in fonts.json [why] We want to replace the existing casks. But they do not have a consistent way to name the casks. Sometimes blanks are preserved (as dashes): "unpatchedName": "DejaVu Sans Mono", "patchedName": "DejaVuSansMono", "caskName": "dejavu-sans-mono", The above looks like cask-name == unpatched-name. Here they introduce blanks out of thin air (the original name does not have blanks): "unpatchedName": "DaddyTimeMono", "patchedName": "DaddyTimeMono", "caskName": "daddy-time-mono", Here they add something to the name??!: "unpatchedName": "Gohu", "patchedName": "Gohu", "caskName": "gohufont", Here the cask-name follows the RFN renaming: "unpatchedName": "Hasklig", "patchedName": "Hasklug", "caskName": "hasklug", Here they do not follow the RFN renaming: "unpatchedName": "Liberation", "patchedName": "LiterationMono", "caskName": "liberation", And there are a lot more ... strangenesses. I guess the casks have been created by different people following different ideas. [how] All these inconsistencies makes setting up rules how to determine the cask name from the other names very complicated and brittle. If we want to preserve the existing cask names the simplest and most stable approach is to explicitely specify them in the fonts.json database: Introduce a new data field "caskName", like shown above. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-11-26 19:00:17 +02:00
"caskName": "victor-mono",
Unify descriptive text in fonts.json [why] The description is displayed like this: * Info: <description> Sometimes the description text starts with lowercase, sometimes with caps. This looks weird. [how] Always start the description with uppercase. [note] Also correct missing(?) description for one font. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
2022-10-18 19:12:20 +02:00
"description": "Clean, crisp and narrow, with a large x-height and clear punctuation"
Updates script to use json data file instead of fc-list * adds json file
2019-10-12 20:59:13 +02:00
}
]
}
Reference in New Issue Copy Permalink