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

Add cp437 characters #13

Closed
davelab6 opened this issue Jul 12, 2017 · 19 comments · Fixed by #39
Closed

Add cp437 characters #13

davelab6 opened this issue Jul 12, 2017 · 19 comments · Fixed by #39

Comments

@davelab6
Copy link
Member

@tracker1 posted in google/fonts#1047:

It would be really nice to have the missing translated characters for CP437 to unicode[1] added (namely shaded blocks, box,, and other "drawing" characters), which would aid in making this a more useful font for web-based terminal emulators.

I did not go through to identify all the missing characters, but did notice quite a few that were missing.

0xb0	0x2591	#LIGHT SHADE
0xb1	0x2592	#MEDIUM SHADE
0xb2	0x2593	#DARK SHADE
...
0xdb	0x2588	#FULL BLOCK
0xdc	0x2584	#LOWER HALF BLOCK
0xdd	0x258c	#LEFT HALF BLOCK
0xde	0x2590	#RIGHT HALF BLOCK
0xdf	0x2580	#UPPER HALF BLOCK

[1] ftp://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/PC/CP437.TXT

@davelab6
Copy link
Member Author

@tracker1 https://github.com/adobe-type-tools/box-drawing might help with this

@tracker1
Copy link

tracker1 commented Jul 17, 2017

@davelab6 I know absolutely nothing of font editing... only know that I'd love to use this as a terminal/web font, but the missing drawing/block and other cp-437 characters make it a non-starter for me. 😢

@davelab6
Copy link
Member Author

@tracker1 cool - thanks for the suggestion :)

@alexeiva
Copy link
Collaborator

Here you go @tracker1 : c7430fc
screen shot 2017-07-18 at 1 41 09 pm
screen shot 2017-07-18 at 1 41 04 pm

Meanwhile, I made box-drawing work for Glyphs v.2.
adobe-type-tools/box-drawing@407f204

@tracker1
Copy link

@alexeiva Nice, thank you so much!

@tracker1
Copy link

It looks like some of the characters aren't lining up, and that the charaters with lower hanging parts (p, q, y, etc) will overlap the box characters, and that the size of some of the characters aren't the same as the text. Will try to give this a closer look over the weekend, for html rendering some ansi/ascii files, to see how it works in that case.

@alexeiva
Copy link
Collaborator

alexeiva commented Jul 24, 2017 via email

@alexeiva
Copy link
Collaborator

alexeiva commented Mar 8, 2018

New bug detected: width of cp437 chars is 600 but should be 500

@alexeiva alexeiva reopened this Mar 8, 2018
@davelab6
Copy link
Member Author

@appsforartists would you be interested in resolving this? :D

@pdevine
Copy link

pdevine commented Dec 17, 2018

What version of Inconsolata is going to have these? Just tried 2.000 and they're missing.

@smasher164
Copy link

Here is a test case that comes across when using Inconsolata in my work. For this text:

┌───────┬───────────────┬──────────────────────┐
│  sign │  combination  │ trailing significand │
├───────┼───────┬───────┼──────────────────────┤
│   1   │   5   │   6   │          20          │
└───────┴───────┴───────┴──────────────────────┘

I get the desired behavior from Menlo:
wantBox
But not from Inconsolata:
gotBox

@tracker1
Copy link

#31 is tracking the scale/spacing issues.

@raphlinus
Copy link
Collaborator

Yup, looking forward to fixing these. Probably next week.

@pdevine
Copy link

pdevine commented Dec 12, 2019

@raphlinus does your change fix all of these issues?
Screen Shot 2019-12-12 at 9 20 24 AM

This was using Inconsolata 2.00 using Regular 10pt. If you have Docker on your machine, you can test this out with the command docker run -it --rm pdevine/textinvaders.

@raphlinus
Copy link
Collaborator

@pdevine I wouldn't expect it to reduce the line spacing; this might be a consequence of the terminal using usWin metrics rather than typo metrics (see #35). I will create a "terminal" version of Inconsolata that reduces the usWin metrics as a workaround, but the longer term answer is to fix the software. I do expect the new release to address the block misalignment, but that also depends on whether the font has coverage for all characters used by the space invaders game.

I don't have Docker handy, and in general prefer people to test their use cases with the candidate fonts - just now merged to master, btw.

@pdevine
Copy link

pdevine commented Dec 12, 2019

@raphlinus no worries. That was taken using Apple's "Terminal" which does seem to suffer from the problem. iTerm2 does seem to be better in that regard.

@smasher164
Copy link

First of all, thank you so much for adding these characters!
I am however seeing some of the lines exhibit uneven thickness when connected. This makes for a pattern-like effect instead of a straight line. Is it possible to address this?
image
image

@raphlinus
Copy link
Collaborator

I don't think it would be straightforward, it's probably a function of your font renderer. One thing you can do is experiment with other fonts and see if they handle this better, then I could take a look and see what they do.

@smasher164
Copy link

On further evaluation, it looks to be renderer-dependent like you said. Chrome is giving me different behavior than sublime for the same fonts/sizes.

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

Successfully merging a pull request may close this issue.

6 participants