FiraCode/features/cv11.fea

# zero without anything inside

sub zero by zero.cv11;
sub zero.tosf by zero.tosf.cv11;
Fixed building on the latest fontmake 2022-03-15 20:11:40 +03:00			`# zero without anything inside`
feat: allow hardcoding of features via arguments to build script All features that were not already in their own files were pulled out of FiraCode.glyphs into individual files. There is no way I will write a parser for the glyphs file to do that at runtime. The build script will then read the code in these feature files and appends it to the `calt` property inside the glyphs file. Features to be baked in can be given to build.sh as a comma separated list with the `-f / --features` flag. To more easily generate multiple font versions with different features baked in, there are flags `-n / --family-name` for build.sh that will allow users to set a custom family name for the font. The special value "features" will append the feature list to the font name. The family name is exported and used by the other build scripts as a directory to separate different font versions. The filenames were not changed, the directory name is enough separation. The flag `-g / --generate-glyphs-only` will cause the script to exit after the custom glyphs file has been created without actually building the font. The custom .glyphs file will be saved as `${family_name}.glyphs`. Via another flag, `-w / --weights`, a comma separated list of font weights to be generated can be given to build.sh. The README received a hint to the new capabilities. Fixed a mixup of cv25 and cv32. The .gitignore was adjusted to better deal with the new directories and files. 2022-03-08 14:33:10 +03:00
			`sub zero by zero.cv11;`
			`sub zero.tosf by zero.tosf.cv11;`