[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: failing CI builds
From: |
Werner LEMBERG |
Subject: |
Re: failing CI builds |
Date: |
Mon, 29 Jun 2020 10:10:25 +0200 (CEST) |
>> Well, while Metafont has SOURCE_DATE_EPOCH support, Metapost hasn't
>> (yet – this will change in a few days so that the next TeXLive
>> version will contain it).
>>
>> Recent versions of FontForge should have support too, BTW.
>
> This still doesn't answer why I'm seeing differences in the
> generated glyphs, see attached diff of emmentaler-11.svg.
Hmm, this looks like a bug in FontForge: It seems to contain code that
outputs SVG data non-deterministically.
Can you reproduce the problem locally by manually calling the
FontForge python script to create the SVG file? If yes, please send
the data to me so that I can submit a FontForge bug report.
Werner
- Re: failing CI builds, (continued)
- Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27
- Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27
- Re: failing CI builds, Werner LEMBERG, 2020/06/27
- Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27
- Re: failing CI builds, Werner LEMBERG, 2020/06/27
- Re: failing CI builds, Werner LEMBERG, 2020/06/28
- Re: failing CI builds, Jonas Hahnfeld, 2020/06/28
- Re: failing CI builds, Werner LEMBERG, 2020/06/29
- Re: failing CI builds, Jonas Hahnfeld, 2020/06/29
- Re: failing CI builds,
Werner LEMBERG <=
- Re: failing CI builds, Jonas Hahnfeld, 2020/06/29