-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Box drawing characters are not antialiased #6161
Comments
I think this is will probably be covered by issue #5897. |
Linking, but not closing this. Thanks. |
I add that utf8 file to the repo last year some time: https://github.com/microsoft/terminal/blob/master/doc/reference/UTF8-torture-test.txt |
The diagonals are terrible though (U+2571, U+2572, and U+2573). These are "box drawing" characters - they're meant to connect together. |
@oising Definitely doesn't look like that for me. This is Fira Code at 10pt: |
From #8614
|
@Grable are you sure you have the builtin glyph setting enabled? |
No i dont, they are incorrect in both sizing, looks and alignment plus no rounded corners. I prefer the stock box drawing that comes with most fonts as very few actually change them. EDIT: If this issue is for only builtin glyph drawing I might have put this in the wrong place :/ |
The builtin glyphs are our solution to the problem you're having. But you're right that the rounded corners are difficult to see at 100% display scale. I'll make them larger and roughly match the way that Cascadia Mono looks like. Hopefully that should be an alright compromise for you. |
That was unfortunately intentional. A lot of users asked us for such box glyphs that don't have aliasing ("blur") and so when I only have 1px to work with I've decided that I'd simply make it look somewhat asymmetric. Adding options to control this would be extremely easy to do though: All of the drawing is already parametric. 🙂 If you'd like us to add support for that, please feel free to file an issue for it (the description can be short). |
I think i will😃 Thank you again! |
Environment
Steps to reproduce
$ curl https://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt
Expected behavior
The box drawings are properly rasterized with antialiasing in similar fashion to the rest of the text. Here is an example from Fluent Terminal using the Inconsolata font:
![image](https://user-images.githubusercontent.com/4991927/82727405-ff738180-9cf2-11ea-8000-c0f82e8d2669.png)
(Note: I'm not necessarily saying this is perfect either, but it's at least closer to what would be an acceptable and more consistent result.)
Actual behavior
The box drawing glyphs are severely aliased, unlike any other text, with visible pixel gaps in diagonal elements, and generally just look really bad. Rendered in the latest stable Windows Terminal version using the Inconsolata font (size 10pt):
![image](https://user-images.githubusercontent.com/4991927/82727447-58dbb080-9cf3-11ea-9f5b-65debc2ce913.png)
This behavior is not just limited to Inconsolata, but happens with every font, and every size. Here is for an example Cascadia Mono in different sizes:
![image](https://user-images.githubusercontent.com/4991927/82727590-19fa2a80-9cf4-11ea-80ff-9a0b472cb62f.png)
8pt
10pt
![image](https://user-images.githubusercontent.com/4991927/82727598-21213880-9cf4-11ea-91c5-7f53135433f2.png)
12pt
![image](https://user-images.githubusercontent.com/4991927/82727599-25e5ec80-9cf4-11ea-9bb0-cbb876431626.png)
This behavior was introduced recently in the RC versions, and I assume
0.11.1333.0
in specific since it included #5743 which altered the way box drawing glyphs were handled. Prior versions had alignment issues with these glyphs that the PR aimed to fix, but at least the glyphs were still rendered nicely individually, with a similar, comparable output to what Fluent Terminal produces.The text was updated successfully, but these errors were encountered: