question: how much interest is there in coding ligatures a la Hasklig for SCP?

adobe-fonts / source-code-pro

Monospaced font family for user interface and coding environments

https://adobe-fonts.github.io/source-code-pro/

SIL Open Font License 1.1

19.75k stars 1.62k forks source link

question: how much interest is there in coding ligatures a la Hasklig for SCP? #96

Open pauldhunt opened 9 years ago

pauldhunt commented 9 years ago

I guess this is an invitation for +1’s, even though I generally dislike them. GitHub should have a polling feature, hmmmmm...

Hasklig

Also, if you have any insights about what works and what doesn’t in terms of coding ligatures, please post here.

magroski commented 6 years ago

Any progress?

vikky49 commented 6 years ago

@magroski @jianghaizhu I used [https://github.com/rojiani/Ligaturizer] to patch the Source code pro. It basically patches the all the FiraCode Ligatures onto any reasonable font. Its a great utility if u like both source code pro and the Fira code style ligatures. Feel free to try it out

rofrol commented 5 years ago

Fixed https://github.com/ToxicFrog/Ligaturizer/issues/25

ferenczy commented 5 years ago

So how does it look, have any work been done on ligatures in Source Code Pro actually, please? It's more than two years since the discussion took place on this.

Source Code Pro already looks great! I would only use ligatures if they are still recognizable, that is, close to the original character sequence. So I am mainly looking for fine-tuned kerning, better positioning and subtle beauty. :)

The kerning doesn't make any sense in the context of a monospaced font.

tapir commented 5 years ago

Just tested LigaSrc Pro in VS Code. It's quite good -> https://github.com/ToxicFrog/Ligaturizer/releases

dgasmith commented 5 years ago

@tapir Great find! I saw Ligaturizer, but did not notice they run through several common fonts.

snaggen commented 5 years ago

I'd love to see ligatures in source code pro. I'm using Ligaturizer versions now, and it is ok, but some ligatures doesn't feel like they match the font. Like && , so I'm still hoping to se native ligatures.

alinnert commented 4 years ago

I'm also totally in for ligatures. (Definitely as an option because there are still reasons not to use them and some people don't like them).

I also want to throw in: If you implement ligatures for HTML comments (, which I'd appreciate), please also support CFML comments (, since I'm also working such projects). Otherwise these comments look kinda strange because HTML comments are a part of these comments.

tspiteri commented 4 years ago

Care needs to be given when the same pair of characters can mean something different. For example <= can mean less-than or equal to ≤, or it can mean leftwards double arrow ⇐, depending on the language or context; for example in VHDL it can mean either of the two, depending on context.

killua99 commented 4 years ago

4 years and nothing happened.

yvvt0379 commented 4 years ago

@pauldhunt It's been 6 years since this issue was created. So any progress? I came up with a solution in #240 . I hope it can help.

astrolemonade commented 4 years ago

@magroski @jianghaizhu I used [https://github.com/rojiani/Ligaturizer] to patch the Source code pro. It basically patches the all the FiraCode Ligatures onto any reasonable font. Its a great utility if u like both source code pro and the Fira code style ligatures. Feel free to try it out

What is the name of the IDE/editor and also the color scheme ? Looks great

yvvt0379 commented 4 years ago

It seems like an intellij-based ide

Guema commented 3 years ago

My humble opinion is that "as it is optional and must be opted-in, there is no logical reason to not do it" Recently released code fonts support ligatures (Jetbrains recently). The only question is about your ressources and the time you can to put for it. Personally, i use this feature. It took time to get used to, but now i feel that code is more easily readable, especially for heavy math or comparison functions.

Btw Source Code is for me the best for fast readability because of an (imo) perfect width/height proportions and its simple and clean round shapes. Haskilg is unfortunately incomplete in ligatures, and is based on old versions of source code.

pouyakary commented 2 years ago

I really love Source Code Pro, yet I really can't stand seeing an ugly -> to make an arrow, and I don't have to, thanks to the wonderful work of @i-tu on Hasklig. But I just think that the font is designed by you people and it deserves to be called Source Code Pro and not Hasklig, and I really think after the amazing job @i-tu has done, it could be nice to merge back those ligatures to the Source Code Pro. It feels like the TypeScript language that you think oh what a wonderful amazing language it is, while you forget it is an extension to the JavaScript, and to me when I think of a great typeface for programming only Hasklig comes to my mind and I forget 99% of the time that this is actually an extension to Source Code Pro. I think Source Code Pro deserves to be the main name and brand and @i-tu should really be a big part of the team. After 6-7 years of this issues, really why not doing a move?

pkazmier commented 2 years ago

I, too, enjoy SCP very much. I love the clean, uncluttered shapes, which make for an easy to read font. It’s simplicity is its elegance in my opinion. With that said, I would also like the option of ligatures as well—not hasklig’s though as it’s meant for Haskell and /= is their not equal ligature.

yvvt0379 commented 2 years ago

It could be nice to merge back those ligatures to Source Code Pro.

Merge back? I don't think it a good idea. There's no denying that Hasklig is a good font, but it's specifically designed for Haskell. However, what we need is ligatures compatible with most languages.