Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Vertical Bar #2

Closed
Mark2Mark opened this issue Jul 20, 2020 · 1 comment
Closed

Vertical Bar #2

Mark2Mark opened this issue Jul 20, 2020 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@Mark2Mark
Copy link
Owner

From a user:

"I was wondering why modern fonts, even those intended for code, do not render the vertical bar | as broken in the middle, as in the Unicode character ¦. This is an obvious solution for differentiating the bar from 1 and I and l, and it has a history behind it in old computer fonts (particularly bitmap ones). I reckon it is not done anymore because Unicode went and made ¦ a separate character – a pretty useless one semantically, I might add. So, I would like to ask the designer of a major recent font design project for code:
Did you consider rendering the bar as broken at some point in the design process?
Was Unicode’s separation of these characters a main motivation for your decision not to?
Do you reckon that the function of differentiating the vertical bar is better served without doing this?
Do you have any more comments about this? …"

@Mark2Mark Mark2Mark self-assigned this Feb 26, 2021
@Mark2Mark Mark2Mark added the question Further information is requested label Feb 26, 2021
@Mark2Mark
Copy link
Owner Author

Anyone with opinions on that?

I usually draw the broken bar way taller than the letter height, which is my eyes distinction enough from the letter l. I find the possible confusion with the 1, as that is with its nose clearly different as well.

Personally, all applications I use the broken bar in (e.g twig modifiers, shell or yaml pipe, or operator, SQL string concatenation, …) I would find it rather confusing to see the broken version of it.

  • Does anyone pledge for the bar to be broken?
  • In which cases would that be preferred?
  • Should it be an option for the user to pick? (If so, are there IDE’s that don’t allow OpenType Features to be set?)

Repository owner locked and limited conversation to collaborators May 8, 2023
@Mark2Mark Mark2Mark converted this issue into discussion #12 May 8, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant