Skip to content

Migrate to googlefonts/oxidize font tech stack - #77

Open
7sDream wants to merge 14 commits into
masterfrom
use-skrifa
Open

Migrate to googlefonts/oxidize font tech stack#77
7sDream wants to merge 14 commits into
masterfrom
use-skrifa

Conversation

@7sDream

@7sDream 7sDream commented Jul 9, 2026

Copy link
Copy Markdown
Owner

Due to #76, I would like to migrate to a technology stack that is still actively maintained.

Currently, googlefonts/fontations seems like a reasonable choice. Chromium appears to be gradually adopting some of its components, and the linebender project is also using it, while providing options such as fontique and parley for font enumaeration and layout.

Current progress:

  • Code implementation
    • fontdb -> fontique
    • ttf-parser -> read-fonts
    • ab_glyph -> skrifa + ab_glyph_rasterizer
      • or skrifa + tiny-skia?
    • Linux system font loading while keep build without c library dep
      • Do we use dlopen?
      • Or do we parse fontconfig configure files like fontdb? leave for next PR.
  • Compilation successful
  • CI passed
  • Verification of correctness
  • Performance
    • Linux: fontconfig with dlopen, speed ok.
    • Windows: DirectWrite API is slow, but it is more reliable than manual parsing, particularly because some font files in system font folder are lack extensions
    • macOS: Not yet tested.

@7sDream 7sDream changed the title Change to googlefonts/oxidize font tech stack Migrate to googlefonts/oxidize font tech stack Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant