You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm using fontc, I'm aware it's an incomplete and imperfect font compiler, and I'm willing to make sacrifices in my source (or hacks on fontc's source itself) to try and get all the way to a TTF.
One problem I'm running into with this is that fontc only reports a few errors at a time (as far as I can tell), instead of all* errors at once. This means that I can't solve classes of errors in one go, I have to do a fix for 3-4 glyphs, then run fontc again, get the same error for a different 3-4 glyphs, fix those, rinse & repeat ad nauseam.
I understand in the long run failing fast is probably best and a sensible default, however much like Cargo's proposed --keep-going, I think something similar could help fontc's early adopters work through the teething pains and get a TTF built.
(*Obviously there may be some point at which no further work can be done due to the accumulated errors, but that's still distinct from stopping everything when the first error is discovered)
The text was updated successfully, but these errors were encountered:
Thanks for opening this, it's definitely an issue we should discuss. In general we should be able (and this could be configurable) to complete all work up to a point where there is a dependency on something that has failed, and return these errors at the end. In general this is a matter of storing a vector of intermediate errors, and returning them at the end. There is some of this in place already, but we also do seem to exit early in some situations.
More generally, I think there's a lot of room for us to improve compiler diagnostics and error reporting, and maybe this could be part of a larger project to that end.
Hi there!
When I'm using fontc, I'm aware it's an incomplete and imperfect font compiler, and I'm willing to make sacrifices in my source (or hacks on fontc's source itself) to try and get all the way to a TTF.
One problem I'm running into with this is that fontc only reports a few errors at a time (as far as I can tell), instead of all* errors at once. This means that I can't solve classes of errors in one go, I have to do a fix for 3-4 glyphs, then run fontc again, get the same error for a different 3-4 glyphs, fix those, rinse & repeat ad nauseam.
I understand in the long run failing fast is probably best and a sensible default, however much like Cargo's proposed
--keep-going
, I think something similar could help fontc's early adopters work through the teething pains and get a TTF built.(*Obviously there may be some point at which no further work can be done due to the accumulated errors, but that's still distinct from stopping everything when the first error is discovered)
The text was updated successfully, but these errors were encountered: