Unexpected text display change for >=
-
I have lived largely in Notepad++ and relied on it for many years, because it is a straightforward text editor and does not do weird things to my text.
So just created a new UTF-8 text file, was typing in text, and typed >= which changed to display what looks like the Unicode character for greater than or equal (≥ (U+2265)). The same behavior occurred even if I typed >, a space, and then =, then removed the space.
When I copied that apparent single character out of my file and pasted it in a Unicode character finder on the web to identify the character, it came back as the vanilla >= that I wanted in the first place.
Looked at Preferences and at the documentation and have no explanation for this, what now appears to be a display issue, my text not appearing as what it is. In computing you more often want >= to appear as such.
Thank you for any solutions or thoughts about this,
Martin L Buchanan
Laramie, WY, USA -
@Martin-L-Buchanan said in Unexpected text display change for >=:
it came back as the vanilla >= that I wanted in the first place.
My immediate thoughts would be to look at your Style Configurator settings. perhaps paste a copy of that here.
Maybe a combination of Language, Style, which theme and font used might have contributed to this display.
Terry
-
You probably have a font selected that has support for ligatures.
And you may have Direct Write turned on in the Preferences (not sure about this, though; I’m AFK).Note: Your data hasn’t changed, just what it looks like has changed. This is confirmed by when you copy and paste that data to another source, and you get 2 characters instead of 1.
In computing you more often want >= to appear as such
Disagree.
Try typing!and then=right next to it … and now you are living in a better world. -
@Alan-Kilborn I want to turn this off too. It also displays
!=as≠. Does anyone know? -
@BrBill said in Unexpected text display change for >=:
@Alan-Kilborn I want to turn this off too. It also displays
!=as≠. Does anyone know?You didn’t need to post a second time with the same question 15 minutes after your first post here.
Besides, one answer in the post you were replying to – turning off DirectWrite, which is now setting it to
GDI (most compatible)as of a few versions ago – would have worked for you if you’d tried it.Or, as I explain here, pick a font that doesn’t have the ligature feature.
Either works.
