Copyright ligature (c) should be disabled

[alexeyten]

Version 1.6
https://www.monolisa.dev/playground

When I type (c) it becomes narrower than 3 chars thus changing alignment of the text.
Also this (artificial) example looks weird:

const charCodes = [...str].map((c) => c.charCodeAt(0));
const charCodes = [...str].map((a) => a.charCodeAt(0));

[bebraw]

@MarcusSterz I guess this would be a good fit for a stylistic set? Keeping it enabled by default feels like the wrong choice for programming as the combination can come up in functions as in the example above.

[okonet]

Thanks for reporting this! Yes, it should be put into a stylistic set.

[okonet]

Hmm, I'm trying to reproduce it in my editor, but it works as expected:

Are you sure it's not a text substation of the OS kicking in?

[bebraw]

I have the same in VS Code when ligatures are enabled:

I can also see the problem in the playground.

You may be right in that it's MacOS that's kicking in, though, as the replacement it's doing is fairly aggressive.

Likely the thing to do here would be to check if we've defined a ligature for (c) to begin with or is it something coming from elsewhere.

[alexeyten]

My screenshot is from site’s playground in Firefox on Ubuntu

[MarcusSterz]

Yes, I can disable it and make it a stylistic set, no prob.

[MarcusSterz]

It is a common ligature trick. You normally add ligature-like features like this to make the workflow faster for people who write text.
I can delete it easily. Making it a stylistic set is not a good option since a stylistic set replaces a glyph with another. Here you have 3 glyphs being replaced by 1 symbol.

[okonet]

Since we have a dedicated symbol for it I don't feel the need for it especially for developers.

Interesting question is why it's not reproducible for me on v1.600 on Mac neither in IDE nor on the website playground.

[okonet]

We decided to drop the ligature but keep the symbol in the font.