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.
One other thing which might help with the difference testing: you can
try changing the compare metric (in harness.sh) to AE, as that is less
forgiving.
I'll take a look at that when I can, but that may not be for another
week or so.
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 ))
--
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel
