-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Text font looks little bold in comparison to conhost #3388
Comments
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
Yeah. I also think its because of the use of different renderers. The difference is not that significant though. Just that the text in conhost looked much lighter and therefore better if you ask me. Attached is the screenshot from my system (I don't know if you can see the differences in this picture). |
Looking at that screenshot, it does look like the difference you're referring to does have to do with the way we're anti-aliasing the text. @miniksa can correct me if I'm wrong here. I know we had a lot of discussion about how we anti-alias fonts prior to announcement. I think once we add #1298, you should be able to configure the terminal to at least be closer. Thanks! /dup #1298 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Yes, this is just the visual difference between GDI text and DirectWrite text. We're planning on adding more knobs to configure it as @zadjii-msft said. |
From @srv-code in #3386:
@srv-code Could you maybe see some screenshots of the difference you're seeing? I'm sure there are going to be slight differences between GDI (the conhost renderer) and DX (the Terminal renderer), but they shouldn't be that significant.
Maybe this has to do with how we're antialiasing? #1298 has some discussion there.
The text was updated successfully, but these errors were encountered: