[BETA] Some non-ascii characters are not rendered in columns of the declension menu
See original GitHub issuePolyglot version: Windows BETA from 19th November 2021 (latest as of writing this)
Unrendered characters: ě í ů ý č ď ň ř š ť ť
(and probably more I didn’t test)
They are rendered properly when displayed as row and tab names. Seems to be unaffected by changing fonts.
Bug: Declension: (the “2” declension contains only regular characters and is there in order to be possible to force the broken declension names into columns)
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Starting with vscode 1.43 non-ascii characters with braces and ...
This is a problem that is caused by the way whitespace is rendered (inline with the actual text) and is triggered when using...
Read more >non-ascii character in directory name breaks web ui display
A directory with a name that starts with certain utf-8 character will not be displayed by the web ui. It furthermore destroys the...
Read more >Non-ascii characters on reading a CSV with Python
I have a big CSV file (~45MB) with about 350.000 rows and 6 columns. When I used this code in Python: data =...
Read more >SQL0302N when inserting non-ASCII characters. - IBM
Receive an SQL0302N error when inserting non-ASCII character data into tables if the database is defined with code set UTF-8.
Read more >Error "CHAR string contains invalid ASCII character" Occurs ...
If the Tableau Desktop UI language is set to the multi-byte (non-ASCII) character like Chinese, Japanese, Korean, the issue will occur in the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ahh, didn’t realize you would be retesting that quickly! I hadn’t yet built a new version up to the public beta. Just did so now, so it should be working in the latest available.
It’s really weird that the newer version wasn’t linked correctly, but worked later for you here… I literally did nothing to fix that between the time when you last said it wasn’t working and when it began working for you. Might need to look into that.