Skip to content

fix(windows): honor ordered font fallback families - #1016

Open
houko wants to merge 1 commit into
nsgo-dev:mainfrom
houko:fix/issue-668-windows-font-fallback
Open

houko wants to merge 1 commit into
nsgo-dev:mainfrom
houko:fix/issue-668-windows-font-fallback

Conversation

@houko

@houko houko commented Nov 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • build a DirectWrite fallback mapping from every family in core.Style.FontFamily
  • apply the mapping to text formats while preserving app-registered fonts
  • cover ordered CJK fallback and document the user-visible fix

Closes #668

Verification

  • go tool nsgo check -target windows -jobs 2
  • go tool nsgo test -target windows ./internal/platform/windows could not run because the current host is macOS and the target test requires Windows

@github-actions github-actions Bot added bug Something isn't working documentation Improvements or additions to documentation Windows size/M conflict Conflicts with the base branch; resolve it first labels Nov 20, 2026
@houko
houko force-pushed the fix/issue-668-windows-font-fallback branch from b4327fb to 6fb6fd0 Compare November 20, 2026 16:05
@github-actions github-actions Bot removed the conflict Conflicts with the base branch; resolve it first label Nov 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working documentation Improvements or additions to documentation size/M Windows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows: a FontFamily list falls back only to the first installed family, never for the characters it lacks

1 participant