Skip to content
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

Ligature <= display incorrectly (also undocumented) while ss02 is disabled. #269

Open
Tnze opened this issue Nov 14, 2024 · 4 comments
Open
Milestone

Comments

@Tnze
Copy link

Tnze commented Nov 14, 2024

The symbol 'less than or equal to' is incorrectly connected and displayed as an arrow. Which is also not documented so I think this is not designed.

5aa153cb9cbe3d6faf2457512059ae8b
15becc00c6f29893ffcbe5770bacc5b8

@heathercran
Copy link
Collaborator

Hi! It looks like the website is incorrectly rendering some of the ligatures at the moment, which I will tag @idan to look into. The <= arrow ligature you're seeing is part of ss09. Which version of these characters do you want to be seeing here instead?

@Tnze
Copy link
Author

Tnze commented Nov 26, 2024

The <= arrow ligature you're seeing is part of ss09.

In my opinion, ss09 should not include this ligature (It even shouldn't be a ligature. Because in most languages <='s semantics is "less or equal to", rather than an arrow). And the ligature also doesn't exist in the website's description of ss09.

@Tnze
Copy link
Author

Tnze commented Nov 26, 2024

So when ss02 is disabled and no matter ss09 in any state. <= should be displayed as is.

Only when ss09 is enabled and <= followed by a > (that is, <=>) it is displayed as an arrow.

@heathercran
Copy link
Collaborator

Ok! This has previously been discussed in #206 and #219 as well, so I think the best solution is to remove <= from ss09 so that ss02 is the only setting that will change its appearance (which would make the pair display as ), but also include the existing arrow ligature version in cv60 instead so that it can still be enabled for anyone that does want to use that ligature. This change will be included in the 1.2 release!

@heathercran heathercran added this to the 1.2 milestone Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants