#true-type-font #font #css #true-type

no-std fontdb

A simple, in-memory font database with CSS-like queries

38 releases (22 breaking)

0.23.0 Oct 9, 2024
0.21.0 Aug 6, 2024
0.20.0 Jul 2, 2024
0.16.2 Feb 19, 2024
0.2.0 Jul 21, 2020

#1 in Data formats

Download history 73330/week @ 2025-01-08 76900/week @ 2025-01-15 74734/week @ 2025-01-22 73842/week @ 2025-01-29 88965/week @ 2025-02-05 77301/week @ 2025-02-12 76923/week @ 2025-02-19 77365/week @ 2025-02-26 77832/week @ 2025-03-05 91057/week @ 2025-03-12 92647/week @ 2025-03-19 85365/week @ 2025-03-26 84827/week @ 2025-04-02 84854/week @ 2025-04-09 83086/week @ 2025-04-16 84491/week @ 2025-04-23

350,061 downloads per month
Used in 564 crates (47 directly)

MIT license

110KB
898 lines

fontdb

Build Status Crates.io Documentation Rust 1.60+

fontdb is a simple, in-memory font database with CSS-like queries.

Features

  • The database can load fonts from files, directories and raw data (Vec<u8>).
  • The database can match a font using CSS-like queries. See Database::query.
  • The database can try to load system fonts. Currently, this is implemented by scanning predefined directories. The library does not interact with the system API.
  • Provides a unique ID for each font face.

Non-goals

  • Advanced font properties querying.
    The database provides only storage and matching capabilities. For font properties querying you can use ttf-parser.

  • A font fallback mechanism.
    This library can be used to implement a font fallback mechanism, but it doesn't implement one.

  • Application's global database.
    The database doesn't use static, therefore it's up to the caller where it should be stored.

  • Font types support other than TrueType.

Font vs Face

A font is a collection of font faces. Therefore, a font face is a subset of a font. A simple font (*.ttf/*.otf) usually contains a single font face, but a font collection (*.ttc) can contain multiple font faces.

fontdb stores and matches font faces, not fonts. Therefore, after loading a font collection with 5 faces (for example), the database will be populated with 5 FaceInfo objects, all of which will be pointing to the same file or binary data.

Performance

The database performance is largely limited by the storage itself. We are using ttf-parser, so the parsing should not be a bottleneck.

For example, on Mac Book Pro 14 with M1 Pro, it takes just ~24ms to load 1361 font faces.

Safety

The library relies on memory-mapped files, which is inherently unsafe. But since we do not keep the files open it should be perfectly safe.

If you would like to use a persistent memory mapping of the font files, then you can use the unsafe Database::make_shared_face_data function.

License

MIT

Dependencies

~2MB
~50K SLoC