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.

Sign up for GitHub

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

Jump to bottom

Missing Option for RBG #1643

Closed
Sanobot opened this issue May 31, 2023 · 5 comments
Closed

Missing Option for RBG #1643

Sanobot opened this issue May 31, 2023 · 5 comments
Labels
dotnet-framework/svc Pri2 Medium priority product-feedback Indicates issues that are related to product issues, not docs [org][type][category] wpf/subsvc

Comments

@Sanobot
Copy link

Sanobot commented May 31, 2023

Given there are new types of monitors out with different types of subpixel-layout, this thing definitely needs an overhall with loads of more options and soon.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label May 31, 2023
@adegeo
Copy link
Contributor

adegeo commented Jun 2, 2023

Thank you for bringing this to our attention. We're slowly migrating and updating all of the documentation to .NET from .NET Framework. I don't know what still applies to WPF on .NET versus what applies to Windows as a whole, considering there have been like 4 major OS releases wince this content was written.

I'll put this on the backlog, but it's probably not going to happen soon. I will, however, ping the Windows docs team to see if they have any information about it.

@adegeo adegeo added the doc-enhancement Improve the current content [org][type][category] label Jun 2, 2023
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Jun 2, 2023
@adegeo
Copy link
Contributor

adegeo commented Aug 28, 2023

I believe the problem is that WPF itself doesn't support these other font rendering systems which are supported by Windows. I think it only supports ClearType. Still looking into it.

@adegeo adegeo mentioned this issue Aug 28, 2023
Open
9 tasks
@miloush
Copy link
Contributor

miloush commented Aug 30, 2023

This is not a documentation feedback, this is a feature request and not even to WPF (but to DirectWrite). "Loads of more options soon" is vague and unjustified. I would suggest a request is submitted through Feedback Hub instead, including which layouts are missing for which models of monitors.

@adegeo not sure what you are refering to by "other font rendering systems". Apart from ClearType, grayscale antialiasing is supported which is sub-pixel layout agnostic.

@adegeo
Copy link
Contributor

adegeo commented Sep 1, 2023 •
edited
Loading

@miloush I think I meant OpenType. I feel like you're correct in your conclusion that this is more of a feature request. I'll close the doc issue. Thanks for taking a look!

@adegeo adegeo closed this as completed Sep 1, 2023
@adegeo adegeo added product-feedback Indicates issues that are related to product issues, not docs [org][type][category] and removed doc-enhancement Improve the current content [org][type][category] labels Sep 1, 2023
@miloush
Copy link
Contributor

miloush commented Sep 1, 2023 •
edited
Loading

ClearType is an anti-aliasing technology while OpenType is a file format

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dotnet-framework/svc Pri2 Medium priority product-feedback Indicates issues that are related to product issues, not docs [org][type][category] wpf/subsvc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dotnet-bot @miloush @Sanobot @adegeo