<![CDATA[Error rendering unicode slashthrough characters]]>Hi
I was trying to write some slashthrough characters, but they are rendered as the image below Slashthrough_error.png
Strangely, when I enable dark mode, they render as this (with a kind of offset on the slash):
Slashthrough_error_dark_mode.png

To replicate this, just copy and paste this line on a new file:
a̷b̷c̷d̷e̷f̷g̷h̷i̷j̷k̷l̷m̷n̷o̷p̷q̷r̷s̷t̷u̷v̷w̷x̷y̷z̷0̷1̷2̷3̷4̷5̷6̷7̷8̷9̷A̷B̷C̷D̷E̷D̷G̷H̷I̷J̷K̷L̷M̷N̷O̷P̷Q̷R̷S̷T̷U̷V̷W̷X̷Y̷Z̷

Opening the file with a hex editor, we have this:
119d21d7-702e-4978-9706-453405028af3-image.png

But if I invert the bytes sequence:
0b61a186-41c7-41b7-9c9b-1531d0e2a63a-image.png

I have these results:
0b514a20-90a1-4e9e-a994-3a858ba456f6-image.png
e380bc12-38e5-4d4a-946b-89c8f7c27e5f-image.png

Before someone asks me, I’m up-to-date:
2423f52c-49d3-4541-9dc8-1674004792e0-image.png

]]>https://community.notepad-plus-plus.org/topic/22020/error-rendering-unicode-slashthrough-charactersRSS for NodeSun, 19 Jul 2026 06:14:01 GMTWed, 20 Oct 2021 12:44:54 GMT60<![CDATA[Reply to Error rendering unicode slashthrough characters on Wed, 20 Oct 2021 14:09:49 GMT]]>@Alexandre-Hagihara ,

The slashthrough U+0337 character you showed is a pretty fancy Unicode character, because it is a “combining”/“overlay” glyph, and some fonts have trouble with them. Your selected font may be different for normal mode vs Dark Mode, so maybe the font you have selected in Dark Mode has different Unicode coverage.

But also there is some other behind-the-scenes font-related magic that affects how Unicode is rendered, so even if your font is okay, there might be oddities. Try toggling Settings > Preferences > MISC > Use DirectWrite to see if it draws those characters better (more in the usermanual).

]]>https://community.notepad-plus-plus.org/post/70709https://community.notepad-plus-plus.org/post/70709Wed, 20 Oct 2021 14:09:49 GMT