Insert Unicode characters not working - please help
-
Thank you @PeterJones , you helped me a lot (@guy038 also). It is clear now for me how symbols/glyphs are displayed. I’ve also tested Lucida sans unicode and those symbols do appear in Np++
-
-
@Alan-Kilborn said in Insert Unicode characters not working - please help:
You may also want to try this setting enabled for your situation
Checking for confirmation: When I pasted the text into my v8.1.1 with DirectWrite checked, it showed the fancy integral characters; if I have DirectWrite unchecked (and re-start NPP, of course) then it doesn’t render. And both of those were with the same Deja Vu Sans Mono font, which doesn’t natively have those glyphs. (Same results with a fresh unzip with Courier New selected). So yes, I think there’s a good chance that turning on the DirectWrite option will help the @ZsoltKántor, even if the active font doesn’t have them.
I wonder if there’s ever a good reason for having that option off? Should we lobby Don to change the default state of that option for future versions? (it might head off questions like this in the future)
-
@PeterJones said in Insert Unicode characters not working - please help:
I wonder if there’s ever a good reason for having that option off? Should we lobby Don to change the default state of that option for future versions? (it might head off questions like this in the future)
I think I saw some discussion somewhere that having it on can cause performance issues.
So maybe it is 6-of-one, half-a-dozen of the other: Do we want more my-characters-don’t-display questions, or more my-N++ -is-slow questions? :-)
I always run with DirectWrite on, but I don’t do a lot of things with file types that appear to be cycle-hogs (e.g. XML). But, thinking about it now, even careting through N++'s config file xml stuff is rather slow for me – perhaps it is related to DirectWrite? Hmmm…
-
@PeterJones said in Insert Unicode characters not working - please help:
I wonder if there’s ever a good reason for having that option off?
A quick search of the forum shows:
After those three, I stopped following the links. I can see that whatever the default state of that toggle, we’re going to get questions about why NPP works the way it does (or outright complaints about how awful the most recent change was). No point in changing the default, I guess. :-)
-
@PeterJones said in Insert Unicode characters not working - please help:
No point in changing the default
It’s always a “hard sell” to get a default changed anyway. :-)
-
@Alan-Kilborn said in Insert Unicode characters not working - please help:
You may also want to try this setting enabled for your situation:
Thanks @Alan-Kilborn , this works, the two downsides what I observed is that the characters overall are a little bit thicker, and np++ start up a bit slower.
But good to know about this option :) -
@guy038 said in Insert Unicode characters not working - please help:
Set or create a string, of type (REG_SZ), value called EnableHexNumpad in the registry key HKEY_CURRENT_USER\Control Panel\Input Method\ Assign the value data 1 to this keyI was looking for a long time for solution to this. Thank you!
It’s weird that is not a default thing after so many years.
Cheers -
@ZsoltKántor said in Insert Unicode characters not working - please help:
@Alan-Kilborn said in Insert Unicode characters not working - please help:
You may also want to try this setting enabled for your situation:
Thanks @Alan-Kilborn , this works, the two downsides what I observed is that the characters overall are a little bit thicker, and np++ start up a bit slower.
But good to know about this option :)Solved issue for me as well, thanks a lot! The odd thing is, that this setting was true per default on one machine, but false on others… so hat the issue on some machines, even same NP++ version, same file etc. tried everything but nothing worked, until found this post!
-
@hfrmobile said in Insert Unicode characters not working - please help:
that this setting was true per default on one machine, but false on others
It would depend on what version was first installed on each of these machines.
Recently, DirectWrite was defaulted to On for new installs, whereas on older versions, it was defaulted to Off.
So yes, “true per default on one” and “false on others” is perfectly understandable.
