a common case is matched _serif_, _sans-serif_ and _monospaced_ font families.
A **font family** is composed of *font files, that share a single design, and differ ONLY in*:
A *font package*, is an installation (RPM) package, containing OpenType font files. It MAY be produced by a source (SRPM) package, that also produces other (font or non-font) packages. Other kinds of font packages are out of scope for this document.
All major browsers have been https://caniuse.com/#feat=ttf[fixed] long ago to accept OpenType fonts.
allows converting upstream files to UTF-8 and Unix end of lines if necessary. It takes the following optional arguments:
all the files that, after fontconfig fixing,
all the zero-suffix variables are aliased to no-suffix variables of the same name, and vice versa.
All those declarations are used and processed in the rest of the `spec` file by the following macros:
also, the reused fonts families when <<Assembling different-family font packages: partial designs>>.
a multi-line description block for the generated package. Each line should be less than 80 columns in length.
and if the required toolchain is available as free software under Linux
… and more shell glob lists:
and package font families from their actual respective upstreams when they are bundled with other material in a third party project.
Annotated spec template
an optional upstream identifier, when upstream publishes multiple font families, with consistent QA rules. Font families released by the same upstream will usually play well with one another. Marking them as such helps users choose good font package sets.
Application support for variable fonts is sparse right now. They can not replace older OpenType formats yet.
Applying strict WWS rules helps applications identify all the parts of a font family, and makes selectors like bolder possible.
appstream files,