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

Update && for ss03 #831

Closed
tonsky opened this issue Sep 10, 2019 · 9 comments
Closed

Update && for ss03 #831

tonsky opened this issue Sep 10, 2019 · 9 comments
Milestone

Comments

@tonsky
Copy link
Owner

tonsky commented Sep 10, 2019

@tonsky you missed the <$, <$> and $> ligatures for the ss04 and shouldn't maybe the && with ss03 look more like grafik than like grafik?

Originally posted by @Vampire in #617 (comment)

@tonsky tonsky added this to the 3 milestone Sep 10, 2019
@Coder-256
Copy link

IMHO I'm not a huge fan of a ligature for && with ss03, but on the other hand &= might be worth considering (bitwise AND and assignment, in many languages). I am interested to hear what other people think.

@tonsky
Copy link
Owner Author

tonsky commented Apr 5, 2020

I tried couple of times but can’t figure out how to make that connection look good. Sorry

@tonsky tonsky closed this as completed Apr 5, 2020
@Vampire
Copy link
Contributor

Vampire commented Apr 5, 2020

You don't like my suggestion? :-(

@tonsky
Copy link
Owner Author

tonsky commented Apr 6, 2020

They are quite apart to be joined like that. And extending the tails didn’t do the job

@Vampire
Copy link
Contributor

Vampire commented Apr 6, 2020

Hm, I don't understand what you mean.
Many ligatures are much narrower than their single chars.
The ligature of <= is half the size of the single characters.
So where do you see the problem in joining them like I depicted?
I also don't think extending the tails would be looking decent.

@Vampire
Copy link
Contributor

Vampire commented Apr 6, 2020

I'm just wondering.
I have it like that in my manipulated FiraCode since years and it is looking quite good imho.

@tonsky
Copy link
Owner Author

tonsky commented Apr 6, 2020

The strokes have direction and logic. In your version it looks like one glyph was just moved behind the other. Which is one way to do it, I just don’t like it.

Re: distance, these are pretty complex characters, so I feel that moving them close together will make them harder to read and will create more of a mess.

@tonsky
Copy link
Owner Author

tonsky commented Apr 6, 2020

I looked at what other fonts with an ampersand like that do. Some just remove one of the tails inside. Would that work?
Screenshot 2020-04-06 at 09 44 08

@tonsky tonsky reopened this Apr 6, 2020
@Vampire
Copy link
Contributor

Vampire commented Apr 6, 2020

I don't know.
That looks strange, but it might just be so because of it being so big to look at.
I can only say that I work with the joined version I suggested for years and like it.
If you think it is not good and too hard to read, then not, that's ok.
I was just curious what your reason was, you are the font expert here. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants