On Saturday, 01 April 2017 at 03:24:21 pm -0400, Br. Samuel Springuel wrote: > On 2017-04-01 1:01 PM, Henry So Jr. wrote: > > If it's unlikely to be in the C code (which seems to be the case), and > > it already exists in the TeX Live 2016 version, then maybe we should > > consider releasing anyway, with this as a known issue. We can release > > fixes to the TeX and Lua code after TeX Live 2017 is built. > > I agree that this is a reasonable solution if the problem is in the TeX > or Lua code. I would like the diagnosis to be nailed down (via a proper > bisect) just to be sure that the problem is where I think it is, but > don't know when I'll be able to get to it.
This makes sense, but Élie has mentioned that the deadline is next Tuesday (I'm not sure if that means the 4th or the 11th), and seeing as this bug is already in the TeX Live 2016 version, perhaps we should go ahead and release anyway? > Hmm... Perhaps it might do to add an option which runs the stricter test > (maybe with a warning about needing a new baseline before hand). > Something like > > if $strict && ! compare -metric AE "$name" "$expected" null: 2>/def/null > elseif (( 10#$metric < 999 )) There's certainly a more elegant way to do it than that, and I'll put it in, but probably not before the TeX Live deadline. Henry _______________________________________________ Gregorio-devel mailing list [email protected] https://mail.gna.org/listinfo/gregorio-devel
