Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Win 11 SDK causes certain fonts to not display properly #182

Open
JohnnyWestlake opened this issue Oct 17, 2021 · 5 comments
Open

Win 11 SDK causes certain fonts to not display properly #182

JohnnyWestlake opened this issue Oct 17, 2021 · 5 comments
Assignees
Labels

Comments

@JohnnyWestlake
Copy link
Collaborator

e.g. Evil of Frankenstine Shadow, Modern Love Grunge, Really Petshop, Taberna Extras, Whiteley Inline, etc.

Seems to be a regression that occurred between the last two major updates, trying to pin down exactly what has occured.

@JohnnyWestlake JohnnyWestlake self-assigned this Oct 17, 2021
@JohnnyWestlake
Copy link
Collaborator Author

Seems to have been caused by targeting the Windows 11 SDK, targeting 2104 SDK works fine. Not really sure where to report this issue 🤔

@JohnnyWestlake JohnnyWestlake changed the title Certain fonts not displaying properly Win 11 SDK causes certain fonts to not displaying properly Oct 17, 2021
@JohnnyWestlake JohnnyWestlake changed the title Win 11 SDK causes certain fonts to not displaying properly Win 11 SDK causes certain fonts to not display properly Oct 17, 2021
@JohnnyWestlake
Copy link
Collaborator Author

Open as an issue at microsoft/microsoft-ui-xaml#6109 for now, will retarget back to Windows 10 SDK for now.

@JohnnyWestlake
Copy link
Collaborator Author

According to the XAML team this is an intentional change to XAML font family creation and leaves some font's unable to be rendered in XAML now as we can no longer properly specify certain font faces.

So for the time being, we're stuck on Windows 10 SDK! Will probably leave this open until the next Win11 SDK?

@Jay-o-Way
Copy link

Any update on this? :)

@JohnnyWestlake
Copy link
Collaborator Author

None, unfortunately. Microsoft have no intention of fixing it right now, and WinUI 3 itself is massively delayed in open sourcing.

On the plus side, there are essentially no practical advantages to using the Windows 11 SDK either, so being stuck on 10 is fine for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants