The "!=" character sequence (et.al.) is forcibly translated to "≠" and thus not a faithful representation #18550

Closed
opened 2026-01-31 06:17:28 +00:00 by claunia · 2 comments
Owner

Originally created by @ethzero on GitHub (Sep 26, 2022).

Windows Terminal version

1.14.2281.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

  1. Launch any command interpreter
  2. Type or display the following ascii sequence: "!=" (without quotes) anywhere in the terminal window
  3. Window Terminal performs a unwarranted translation to the "≠" character, and thus not a true reproduction of, for example a file's content.

In a nutshell: "!=" != "≠"!

Expected Behavior

For Windows Terminal not to translate any character sequences allowing users to view file contents in particular, faithfully.

Actual Behavior

"≠"

Originally created by @ethzero on GitHub (Sep 26, 2022). ### Windows Terminal version 1.14.2281.0 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce 1) Launch any command interpreter 2) Type or display the following ascii sequence: "!=" (without quotes) anywhere in the terminal window 3) Window Terminal performs a unwarranted translation to the "≠" character, and thus not a true reproduction of, for example a file's content. In a nutshell: "!=" != "≠"! ### Expected Behavior For Windows Terminal not to translate any character sequences allowing users to view file contents in particular, faithfully. ### Actual Behavior "≠"
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 06:17:28 +00:00
Author
Owner

@ethzero commented on GitHub (Sep 26, 2022):

UPDATE: It just struck me, fonts can technically re-render characters sequences to a single character, i.e. Unicode.
The issue above was using CaskaydiaCove Nerd Font Mono (typically used with PoSH).
Simply reverting the font to Cascadia Mono restores the expected behavior.
To my surprise, Cascadia Code also exhibits this "translating" behavior but in a slightly different manner.

Apologies as this is not likely an issue with Windows Terminal but a bafflingly side-effect of using a "fancy" font for the terminal.

@ethzero commented on GitHub (Sep 26, 2022): UPDATE: It just struck me, fonts can technically re-render characters sequences to a single character, i.e. Unicode. The issue above was using _CaskaydiaCove Nerd Font Mono_ (typically used with PoSH). Simply reverting the font to _Cascadia Mono_ restores the expected behavior. To my surprise, _Cascadia Code_ also exhibits this "translating" behavior but in a _slightly_ different manner. Apologies as this is not likely an issue with Windows Terminal but a bafflingly side-effect of using a "fancy" font for the terminal.
Author
Owner

@DHowett commented on GitHub (Sep 26, 2022):

Thanks for the report! Fonts with "coding ligatures" will be rendered using coding ligatures. This part is expected 😄

@DHowett commented on GitHub (Sep 26, 2022): Thanks for the report! Fonts with "coding ligatures" will be rendered using coding ligatures. This part is expected :smile:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18550