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

Open octothorpe #621

Closed
paolobolzoni opened this issue Jun 24, 2020 · 5 comments
Closed

Open octothorpe #621

paolobolzoni opened this issue Jun 24, 2020 · 5 comments

Comments

@paolobolzoni
Copy link
Contributor

The octothorpe of IBM Plex looks somewhat weird, but it is well readable even when displayed very small. Since Iosevka is used for code and it is very tight I think it would be a valuable addition to have a bit more breeze in the text.

IBM Plex mono octothorpe
(IBM Plex mono octothorpe)

@be5invis
Copy link
Owner

image

@paolobolzoni
Copy link
Contributor Author

Even after downloading the latest dev code this simple build plan leave the number sign closed and upright... Am I missing something?

I open the resulting regular font with DTL OTMaster and checked the octothorp with Glyph Index (gid) 6.

 $ cat private-build-plans.toml
# parameters.toml

[buildPlans.iosevka-paopao]
family = "Iosevka Paopao test"

design = [ "sp-fixed", "VXBI" ]
hintParams = ["-a", "sss"]

[buildPlans.iosevka-paopao.weights.light]
shape = 300
menu  = 300
css   = 300

[buildPlans.iosevka-paopao.weights.regular]
shape = 500
menu  = 400
css   = 400

[buildPlans.iosevka-paopao.weights.bold]
shape = 700
menu  = 700
css   = 700

[buildPlans.iosevka-paopao.slants]
upright = "normal"
italic = "italic"

@be5invis
Copy link
Owner

@paolobolzoni What's your command used to build fonts. I used npm run build -- contents::iosevka-paopao and the result match expectation.
image

@paolobolzoni
Copy link
Contributor Author

paolobolzoni commented Jun 30, 2020

The command was the same. Then I tried to fully reset the building environment. But after compiling otfccit fails at one test:

[...] [==========] 1990 tests from 183 test suites ran. (5981 ms total)
[  PASSED  ] 1989 tests.
[  FAILED  ] 1 tests, listed below:
[  FAILED  ] premake_http.http_redirect
HTTP response code said error
The requested URL returned error: 404 Not Found

Of course, previously this did not happen. I will try to understand more.

@paolobolzoni
Copy link
Contributor Author

I know it is not great, but merely skipping the otfcc tests after the compilation and then resetting the whole building environment gave the expected result.

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

No branches or pull requests

2 participants