Skip to content

Any way to disable == and === ligatures when ss06 is turned on? #347

@ian-h-chamberlain

Description

@ian-h-chamberlain

Hi, loving the new update for the most part! It fixes some of the remaining issues I had been dealing with, but there's one I haven't figured out a solution to yet:

The ss06 setting seems to override appearance for == and ===. I have

  • ss01 turned off because I don't want the merged != and == ligatures, but
  • ss06 turned on, because I want the repeated character ligatures like e.g. ### and +++

So far, I have not found a way to get back the separated appearance of == / === without disabling ss06 — maybe there is a cvXX that can be used for this?

Here are what the varios combinations look like:

Image Image Image Image

Suggestions:

  1. If possible, provide a character variant for == and === (or maybe one for each), which disables merging and falls back to either separated characters or ss01 ligatures.

  2. Document the fact that == and === are affected by ss06, if this behavior is intentional. The website doesn't seem to mention = at all for ss06, and even though it's nice to have for long chains like ========= the behavior is surprising for the commonplace ==

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions