-
Notifications
You must be signed in to change notification settings - Fork 16
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 Ysabeau-Italic[wght].ttf
#49
Comments
Hi @behdad, thanks for your error hunting! I fixed them on my side, but then had trouble pushing them because I hadn't pulled beforehand. Trying to fix that, I maneuvered myself into a ditch and don't know how to get back out. What in the nine hells does «fix them up in the work tree» mean? Cheers, Christian (base) [Andromeda-2: GitHub] $ git push origin master |
I think I fixed it. Can you check? |
No looks like you got into a conflict. If you don't mind redoing the fixing, you can do:
Then do your work again, then |
Git still complained about some things not being compatible. I went to war with it until it accepted the changes. Now my Glyphs source files are corrupt. I am about to throw my laptop out of the window. |
Blame @yanone |
Glyphs is beyond me... |
Can you open Ysabeau.glyphs from the current commit? |
I'm on Linux currently. Don't have Glyphs. |
Could you revert the repo to yanone's last commit (9386c5f), though? I'm too dumb to do it myself. |
I don't have write access to your repo. But try:
see if that helps. Just don't push anything until you figure it out. |
I already did that, but I just got the following: HEAD is now at 9386c5f Merge pull request #42 from yanone/master No files were changed either locally or on the repo. If I follow it up by git pull, I download the current latest commit from the repo again, which isn't what I want. What do I have to do to get those files from 9386c5f onto my machine so I can recommit them as the newest working version? |
Do you want the files before 9386c5f ? |
No, those at 9386c5f. I'm assuming the commit was healthy before my Merge Of Doom. |
Whoa wait, it works, I can open my source file again! Do I not have to download the files again because my local instance remembers what the files were like at that stage...? In any case, if I make changes now and push, it will generate another conflict with the more recent commits, right? How can I force my new version through that resistance? |
If you managed to get to a good state, then you can, gasp, do:
|
Phew! OK, the newer commits are gone. Thanks so much! I'll redo the fixes later tonight. |
I redid the fixes in the source files, but I realized you were taking about the variable fonts in the /googlefonts directory, rather than the ones I made myself with Glyphs (in the /vf directory). I actually don't know how the Google variable fonts are exported, so you'll have to ask @yanone to regenerate them. (Or to teach me how to do it I guess?) Cheers, Christian |
I'll test your new ones as well. I let @yanone figure out how to get them in the Google Fonts directory. Thanks! |
I actually deleted my homebrew variable fonts from the repo since presumably they're less refined than the Google ones... |
I'll look at generating new fonts on Wednesday. |
Hello!
This is an automatically-generated report about possible interpolation problems in
Ysabeau-Italic[wght].ttf
, as found in the Google Fonts catalog.The particular version of the font that was tested was archive:.
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:
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 apologize and ignore & close it.To give feedback about this report, please file an issue or open a discussion at fonttools.
The text was updated successfully, but these errors were encountered: