Hi Owen,
Le 30/06/2020 à 23:45, Owen Lamb a écrit :
Apologies--I double-checked the tutorial, and it looks like I just
missed a half-line of code. I put it in, and the beta looks fine now.
So... disregard the beta stuff!
On Tue, Jun 30, 2020 at 2:35 PM Owen Lamb <owendl...@gmail.com
<mailto:owendl...@gmail.com>> wrote:
Hi Jean,
If Fontforge is too old, it never told me so. It generated font
files perfectly well over the last month. Running sudo apt
updatedidn't show any newer versions.
I can't help but notice that CI failed to build some commits on
Friday due to font issues, the same day that my issue first showed
itself. It might be possible that some update made a dependency
conk out on particular setups, including LilyDev. How that would
happen is beyond me, though.
As a side note, when I was first learning MetaFont, I made the
letter-beta glyph described in the tutprial to test everything
out. The .mf file has been sitting in my VM's home directory since
then. This week, when I opened Fontforge to make sure it worked
properly, I absent-mindedly clicked on letter-beta.mf when it
requested to open a file. To my surprise, Fontforge actually
opened it up and showed it as a glyph. However, it looks
wonky--not at all how I remember it looking when I first made the
file. Attached is the source file and a screenshot of
Fontforge's interpretation of the glyph. Not sure if it'll lead
anywhere, but you never know...
I'd like to see if my issue is reproducible on a fresh LilyDev VM
hosted elsewhere. (In particular, my host machine's Windows 10,
but I'm not sure that should matter.) Any volunteers willing to
try that?
Thanks for being patient with me,
Owen
So git clean didn't work? At this point, unfortunately I can't help much--my
previous message was merely a shot in the dark but I understand almost
nothing
about fonts. Also, I'll be going on vacation pretty soon, so I won't
have time
to setup LilyDev, sorry…
That said, if CI itself started to fail recently, there must be
something broken
in the sources, possibly in relation with a specific environement. Could
you try
to compile after a git checkout release/2.18.0-1? If that succeeds, you
want to
go through a git bisect to find the culprit.
Sorry for not being able to provide more than this sort of advice…
Best,
Jean
PS: I guess https://gitlab.com/lilypond/lilypond/-/merge_requests/205 is
going
to help in debugging.
