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

Interpolation problems in YsabeauInfant-Italic[wght].ttf #56

Open
behdad opened this issue Jan 4, 2024 · 5 comments
Open

Interpolation problems in YsabeauInfant-Italic[wght].ttf #56

behdad opened this issue Jan 4, 2024 · 5 comments

Comments

@behdad
Copy link

behdad commented Jan 4, 2024

Hello!

This is an automatically-generated report about possible interpolation problems in YsabeauInfant-Italic[wght].ttf, as found in the Google Fonts catalog.

To download a PDF version of this report with helpful visuals of the problems, click here; Or to view it on the GitHub website, click here.

The report follows:

Glyph uni030A0301 was not compatible:
  Masters: '', 'wght=1000.0':
    Contour 2 interpolation is underweight: '', 'wght=1000.0'

This report was generated using the fonttools varLib.interpolatable tool. We understand that sometimes the tool generates false-positives. Particularly for more complicated font designs. If you did not find this report useful, please accept our apologies and ignore / close it.

To give feedback about this report, please file an issue or open a discussion at fonttools.

Please note that I am doing this as a community service and do not represent Google Fonts.

@CatharsisFonts
Copy link
Owner

CatharsisFonts commented Jan 4, 2024

Huh, looks like there's an old version of the acute stuck in the lighter masters of ringabovecomb_acutecomb in Ysabeau Italics. I fixed it locally, but then remembered I should have git pulled first.
I'm now back at this stage where I screwed things up last time:
(base) [Andromeda: GitHub] $ git pull
error: cannot pull with rebase: You have unstaged changes.
error: please commit or stash them.
(base) [Andromeda: GitHub] $
@behdad, what should I do to resolve this without screwing up the repo again? Stash, probably?

@behdad
Copy link
Author

behdad commented Jan 4, 2024

You can try stash but that might still get you in a merge conflict...

Note that I'm testing the version of the font in the Google Fonts repo only. So if you fixed this recently it might not have reached there.

@CatharsisFonts
Copy link
Owner

sigh So how do I avoid a merge conflict? Can I discard all changes since the last commit and then pull?
xkcd summed it up perfectly:
https://explainxkcd.com/wiki/images/4/4d/git.png

@behdad
Copy link
Author

behdad commented Jan 4, 2024

If you want to discard all your local changes do a git reset --hard. But make sure that's what you really intend.

@CatharsisFonts
Copy link
Owner

CatharsisFonts commented Jan 4, 2024

Oh wait, it looks like I'm not even out of date with my local instance. I just assumed it was the case because you seemed to be working on it, and when I git pulled and got an error message. I guess I can afford to commit and push, then. Sorry for the hassle. I'm just not cut out for working with git.
EDIT: Yep, all good.

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

No branches or pull requests

2 participants