-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
greater than and less than should use ≤ ≥ #263
Comments
Actually this is a cultural difference. I spent half of my life in russia, there we used ⩾ all the time :D But here it's uncommon. A fork would probably be a solution, anybody with a mac? |
Here in Brazil I'm not sure I've ever seen ≤ ≥ until I stumbled upon these in the IT world. |
I agree that ≤ and ≥ are easier to distinguish, but I feel ⩽ and ⩾ are easier to look at and follow the style of the rest of the ligatures in the font pack. |
Let’s use random numbers generator to decide https://twitter.com/firacode/status/777129225774043136 :) |
How about a culturally-neutral approach with ligatures for >= and <= that simply streamline the original two characters by vertically aligning them and reducing the space between them, like the current ligature for ":=" does? That would have the added benefit, in my mind, of having the ligatures more closely resembles the original two characters. With both ⩾ and ≥ it seems like there's enough difference between what I typed and what actually ends up on the screen that clarity ends up impaired rather than increased. |
Any plans to do anything with this? Would love to have ligatures in my code, but not if I'm more likely to make silly errors. These are honestly harder to distinguish. |
Currently greater than and less than use ⩽ and ⩾
This is actually uncommon. HTML's "commonly used" symbols are ≤ (&leq vs &leqslant) Latex uses /leq. The germans even have a DIN standard where they set ≤ ≥ as standard.
But the most important point is: it is visually more distinguishable from < and > signs.
So I suggest using ≤ instead of ⩽
The text was updated successfully, but these errors were encountered: