Skip to content

Update Avalonia to 11.3.11 to fix Monospace font on Linux#924

Merged
KirillOsenkov merged 1 commit intoKirillOsenkov:mainfrom
foriequal0:fix/avalonia
Jan 31, 2026
Merged

Update Avalonia to 11.3.11 to fix Monospace font on Linux#924
KirillOsenkov merged 1 commit intoKirillOsenkov:mainfrom
foriequal0:fix/avalonia

Conversation

@foriequal0
Copy link
Copy Markdown
Contributor

Prior to Avalonia 11.2.0, it wasn't able to use "Monospace" on Linux. The change AvaloniaUI/Avalonia#15703 shipped in 11.2.0 fixes that.

On Linux, fonts are resolved using fontconfig library. It can be configured by defining match patterns in fonts.conf. So, generic family names such as "Monospace" are usually defined as match patterns.

Prior to the change, this line prevented Avalonia from using the correctly resolved font for the generic family name, although the underlying library (Skia) resolved the correct font.

AvaloniaUI/Avalonia@1121879#diff-047c1353fd5bbb011dbd2dea7c1d1a021f0fcfe583f6b9d4d0ab5888b67302f2L59

Prior to Avalonia 11.2.0, it wasn't able to use "Monospace" on Linux.
The change AvaloniaUI/Avalonia#15703
shipped in 11.2.0 fixes that.

On Linux, fonts are resolved using fontconfig library.
It can be configured by defining match patterns in fonts.conf.
So, generic family names such as "Monospace" are usually
defined as match patterns.

Prior to the change, this line prevented Avalonia from using
the correctly resolved font for the generic family name,
although the underlying library (Skia) resolved the correct font.

AvaloniaUI/Avalonia@1121879#diff-047c1353fd5bbb011dbd2dea7c1d1a021f0fcfe583f6b9d4d0ab5888b67302f2L59
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.

2 participants