On 27 mars 2013, at 07:54, Werner LEMBERG <w...@gnu.org> wrote: > >> https://code.google.com/p/lilypond/issues/detail?id=2656 >> >> This is really bad. I agree that it is critical. I unfortunately >> have no way to test this, but do people have an ETA for fixing this? >> If not, it will hold 2.18 up for a long time, in which it may be >> worth pushing the translate_axis patch that I've been holding in the >> works. > > As can be seen in comment #26, Behdad is willing to help, but a > LilyPond developer (or power user) using a Windows box must step > forward, using a current version of Pango (and probably Harfbuzz) to > test the issue. The results should then be added to GUB. >
Someone who "knows what they're doing" (tm) needs to head up the effort and send an e-mail to the LilyPond user list recruiting 2-3 power users. A 1-2 hour Skype session should be all that is needed for the data gathering. I'm in wedding mode for the next 3-4 weeks, so that's a no go for me :-( Cheers, MS _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel