ufo_sources
- com.daltonmaag/check/ufo_recommended_fields[source][source]
Check that recommended fields are present in the UFO fontinfo.
Rationale:
This includes fields that should be in any production font.
Originally proposed at https://github.com/fonttools/fontbakery/pull/1736
- com.daltonmaag/check/ufo_required_fields[source][source]
Check that required fields are present in the UFO fontinfo.
Rationale:
ufo2ft requires these info fields to compile a font binary: unitsPerEm, ascender, descender, xHeight, capHeight and familyName.
Originally proposed at https://github.com/fonttools/fontbakery/pull/1736
- com.daltonmaag/check/ufolint[source][source]
Run ufolint on UFO source directory.
Originally proposed at https://github.com/fonttools/fontbakery/pull/1736
- com.daltonmaag/check/ufo_unnecessary_fields[source][source]
Check that no unnecessary fields are present in the UFO fontinfo.
Rationale:
ufo2ft will generate these.
openTypeOS2UnicodeRanges and openTypeOS2CodePageRanges are exempted because it is useful to toggle a range when not _all_ the glyphs in that region are present.
year is deprecated since UFO v2.
Originally proposed at https://github.com/fonttools/fontbakery/pull/1736
- com.google.fonts/check/designspace_has_consistent_codepoints[source][source]
Check codepoints consistency in a designspace file.
Rationale:
This check ensures that Unicode assignments are consistent across all sources specified in a designspace file.
Originally proposed at https://github.com/fonttools/fontbakery/pull/3168
- com.google.fonts/check/designspace_has_consistent_glyphset[source][source]
Check consistency of glyphset in a designspace file.
Rationale:
This check ensures that non-default masters don’t have glyphs not present in the default one.
Originally proposed at https://github.com/fonttools/fontbakery/pull/3168
- com.google.fonts/check/designspace_has_default_master[source][source]
Ensure a default master is defined.
Rationale:
We expect that designspace files declare on of the masters as default.
Originally proposed at https://github.com/fonttools/fontbakery/pull/3168
- com.google.fonts/check/designspace_has_sources[source][source]
See if we can actually load the source files.
Rationale:
This check parses a designspace file and tries to load the source files specified.
This is meant to ensure that the file is not malformed, can be properly parsed and does include valid source file references.
Originally proposed at https://github.com/fonttools/fontbakery/pull/3168
- com.thetypefounders/check/features_default_languagesystem[source][source]
Check that languagesystem DFLT dflt is present in the features.fea file.
Rationale:
The feature file specification strongly recommends to use a languagesystem DFLT dflt statement in your feature file. This statement is automatically inserted when no languagesystem statements are present in the feature file, unless there is another languagesystem statement already present. If this is the case, this behaviour could lead to unintended side effects.
This check only WARNs when this happen as there are cases where not having a languagesystem DFLT dflt statement in your feature file is technically correct.
http://adobe-type-tools.github.io/afdko/OpenTypeFeatureFileSpecification.html#4b-language-system
Originally proposed at https://github.com/googlefonts/fontbakery/issues/4011
- FontBakeryCondition fontbakery.profiles.ufo_sources.designSpace[source][source]
Given a filepath for a designspace file, parse it and return a DesignSpaceDocument, which is ‘an object to read, write and edit interpolation systems for typefaces’.