-
Notifications
You must be signed in to change notification settings - Fork 592
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
Build process gets stuck when building iosevka-extended #551
Comments
I can confirm this with git commit eea51f6 the install process is stopped at |
The modification “weight = 600” is NOT tested, and may frequently create broken shape/hangs. |
This will remove extended subfamilies and leave "normal" subfamilies only. |
Hmm I haven't changed anything in my config and it was working until the last commit ... [buildPlans.iosevka-artesanal-curly]
family = "Iosevka Artesanal Curly"
design = [
"artesanal",
"slab",
"v-f-tailed",
"v-g-opendoublestorey",
"v-i-italic",
"v-k-curly",
"v-l-italic",
"v-m-shortleg",
"v-r-top-serifed",
"v-eszet-traditional",
"v-v-curly",
"v-w-curly",
"v-y-curly",
"v-capital-y-curly",
"v-x-curly",
"v-zero-reverse-slashed",
"v-three-flattop",
"v-seven-serifed",
"v-nine-turned-six",
"v-tilde-high",
"v-asterisk-high",
"v-paragraph-high",
"v-caret-high"
]
[buildPlans.iosevka-artesanal-curly.weights.regular]
shape = 400
menu = 400
css = 400
[buildPlans.iosevka-artesanal-curly.weights.book]
shape = 450
menu = 450
css = 450
[buildPlans.iosevka-artesanal-curly.weights.medium]
shape = 500
menu = 500
css = 500
[buildPlans.iosevka-artesanal-curly.weights.semibold]
shape = 600
menu = 600
css = 600
[buildPlans.iosevka-artesanal-curly.weights.bold]
shape = 670
menu = 700
css = 700
[buildPlans.iosevka-artesanal-curly.weights.extrabold]
shape = 800
menu = 800
css = 800
[buildPlans.iosevka-artesanal-curly.weights.heavy]
shape = 900
menu = 900
css = 900 |
@wimstefan I cannnot repro this with unmodified |
@be5invis there's definitely no change in the parameters.toml [artesanal]
slantAngle = 2
[artesanal.multiplies]
sb = 0.88
width = 0.88 And yes I'm building my fonts also after every commit without a problem ... |
@wimstefan What build are you testing? @deathaxe's build or yours? |
I've submitted a patch so it should fix this break. Closed. |
I'm testing my own configuration as shown above ... since you've committed a couple of things to the dev branch I've reached commit 0213055 in the meantime. But it still hangs on the same spot despite adding your tip above to my build configuration: [buildPlans.<your build name>.normal]
shape = 5
menu = 5
css = "normal" I've jumped on this issue since I was presuming it is the same sort of issue I'm experiencing as well. I'm sorry if I disturbed the original issue report ... |
@wimstefan Are you adding slope even for regular? This is definently out of our support scope...You can consider remove the heavy weight if you do not need it. |
It's a very slight slant only and I'm using it already more than 2 months in this I need the different weights btw since I'm using Iosevka nowadays for all my application, wm and GUI fonts as well ;-) |
OK now it's getting interesting ... I've checked out the latest commit, removed the What else can I do to get more information what's going wrong? |
@wimstefan You also shrink the characters width which may also cause problem. |
@wimstefan Actually, it is hanging when building the Pound Sterling ( |
wow thanks for finding the reason for this issue! That was certainly not an easy one. Hats off Sir! I can confirm that removing the I try to follow your suggestion but am not sure how to achieve that? I'm not sure which value I should use which is corresponding to the |
@wimstefan Just change the shape weight in your build plan. [buildPlans.iosevka-artesanal-curly.weights.regular]
shape = 400 # May Reduce this
menu = 400
css = 400
[buildPlans.iosevka-artesanal-curly.weights.book]
shape = 450 # May Reduce this
menu = 450
css = 450
[buildPlans.iosevka-artesanal-curly.weights.medium]
shape = 500 # May Reduce this
menu = 500
css = 500
[buildPlans.iosevka-artesanal-curly.weights.semibold]
shape = 600 # May Reduce this
menu = 600
css = 600
[buildPlans.iosevka-artesanal-curly.weights.bold]
shape = 670 # May Reduce this
menu = 700
css = 700
[buildPlans.iosevka-artesanal-curly.weights.extrabold]
shape = 800 # May Reduce this
menu = 800
css = 800
[buildPlans.iosevka-artesanal-curly.weights.heavy]
shape = 900 # May Reduce this
menu = 900
css = 900 |
That's good to know. Unfortunately I'm not clever enough to understand the logic behind the building of this marvelous font :-/ Thank you so much for helping me!!! |
I modified I use the customized (width = 600) Don't find it too wide. Haven't learned too much about font editing so don't have any idea how to build my own build plan or which values needed to configure to do certain customizaiton. Was happy about being able to make the font a little wider at all. |
@deathaxe Anyway...
|
Thanks, very much. Tried to adjust it to match the width of Source Code Pro, which is quite wide as well. Having some safe options to increase the width would be appreciated. Not sure if an "Ultra Extended" needs to be built by default or just supported for private build plans. Maybe there are just too many aspects of taste to decide it atm. The Just not sure what a good multiplier would look like, maybe 1.2 (0.6em), 1.25 (0.625em) or even 1.3 (0.65em)? Looks like I definitely need to dig a bit deeper into all that stuff to get the best out of the font using private-build-plans. ;-) |
If you have problem when building Iosevka, please provide these information:
parameters.toml
, paste if modified:build-plans.toml
, paste if modified:private-build-plans.toml
, if present:When running
npm run build -- ttf::iosevka-ss09
the build process stucks at 66% (74 tasks pending) with all 4 CPU cores run at 100% for hours.Looks like an endless loop being caused by the
width = 600
parameter - the only one changed.I've built several versions with a width of 600 before. The last was 3.0.0-rc.8. It also took some time but finally got through it.
The text was updated successfully, but these errors were encountered: