fix: google fonts rendering with satori #440
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
β Type of change
π Description
Google Fonts unicode-range subsetting caused issues with Satori - non-Latin subsets would get loaded but lack glyphs for Latin text. WOFF2 variable fonts also don't work since Satori doesn't support font variation axes.
This extracts unicode-range from font-face blocks and passes it through to Satori for proper glyph selection (falling back to Latin range if missing). It prefers static WOFF over variable WOFF2 when both are available, and converts WOFF2βTTF using wawoff2 for all subsets. Converted fonts write directly to @nuxt/fonts cache directory for unified publicAssets bundling.