Hi all, i've just got enlightened about this very old thread:
On Tue, Sep 20, 2011 at 10:17 PM, Janek Warchoł <janek.lilyp...@gmail.com> wrote: > I want to fix an issue where a note is misplaced by about 0.07 > staffspace. I'll add a regtest for this, but how will we make sure > that it won't be overlooked in the future? When we watch a regtest > comparison, it shows us the output in a quite low-resolution > rasterized form; it will be impossible to spot the difference. > > [...] > > My idea of solving this problem: add information about the resolution > at which a regtest should be compiled (and displayed to the user in > the comparison) to the ly file. For example add a header field: > resolution = #1000 There's a much easier way: set staff-size to something really big. I suggest that we adopt this as an official policy: fixes for easy-to-overlook things should be documented by regtests using big/enormous font-size (e.g. between 30 and 100, depending on issue). So, everyone checking regtests should pay extra attention to details when he sees a big-font regtest, while small differences between normal-sized tests can usually be ignored. Do you agree? Shall i mention this in CG 9.2, "What to look for"? cheers, Janek _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
