Try to normalize family names for embedded fonts#15703
Merged
grokys merged 7 commits intoAvaloniaUI:masterfrom May 24, 2024
Merged
Try to normalize family names for embedded fonts#15703grokys merged 7 commits intoAvaloniaUI:masterfrom
grokys merged 7 commits intoAvaloniaUI:masterfrom
Conversation
…the requested family name
|
You can test this PR using the following package version. |
Collaborator
|
Contributor
Author
|
@cla-avalonia agree |
maxkatz6
approved these changes
May 21, 2024
|
You can test this PR using the following package version. |
foriequal0
added a commit
to foriequal0/MSBuildStructuredLog
that referenced
this pull request
Jan 31, 2026
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 pattern. Prior to the change, this line prevented Avalonia to use correctly resolved font for the generic family name, although underlying library (Skia) resolved the correct font. AvaloniaUI/Avalonia@1121879#diff-047c1353fd5bbb011dbd2dea7c1d1a021f0fcfe583f6b9d4d0ab5888b67302f2L59
foriequal0
added a commit
to foriequal0/MSBuildStructuredLog
that referenced
this pull request
Jan 31, 2026
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 to use correctly resolved font for the generic family name, although the underlying library (Skia) resolved the correct font. AvaloniaUI/Avalonia@1121879#diff-047c1353fd5bbb011dbd2dea7c1d1a021f0fcfe583f6b9d4d0ab5888b67302f2L59
foriequal0
added a commit
to foriequal0/MSBuildStructuredLog
that referenced
this pull request
Jan 31, 2026
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Bold, Black, etc.SKFontManager.GetInstalledFontFamilyNamesfontSource#FamilyNameso known keywords are filtered out before caching them in the font collection.What does the pull request do?
What is the current behavior?
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues