Xavier Scheuer wrote > Hi dear bug squad members, > > I do not want to criticize but I think some bug reports remained > untracked, as I see no reply to the original poster. > This is the case for Daniel Rosen's "Avoiding collisions involving > full-bar rests" e-mail, Eluze's "add "real" string number extenders", > Arle Lommel's "Changing document fonts with non-standard global font > size causes scaling problems" or pls' "automatic scaling to landscape > paper size leads to collisions". > All of them reported on December 14, 2012. > > I do not know how you guys handle this, I just would like to make sure > they do not become lost/forgotten.
thank you, Xavier, for pointing to these seemingly unanswered bug reports! I cannot tell if something special happened on this 14th of December with any possibly involved systems like google, nabble or others. I've done some research: - for DR's question see http://lilypond.1069038.n5.nabble.com/Full-bar-rests-in-single-staff-polyphony-tt137626.html#a137722 - for my own question about "add "real" string number extenders" I can't answer - "Changing document fonts with non-standard global font size causes scaling problems" see http://lilypond.1069038.n5.nabble.com/Changing-fonts-with-global-staff-size-other-than-20-leads-to-scaling-problems-td137688.html#a137798 - "automatic scaling to landscape paper size leads to collisions" see http://lilypond.1069038.n5.nabble.com/automatic-scaling-to-landscape-paper-size-leads-to-collisions-tp137634p137673.html in certain cases when posting to several lists answers only go to one list and this might not be the intended on. the answers may not always be satisfying but at least they are answers! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Bug-reports-from-December-14-2012-forgotten-tp138040p138049.html Sent from the Bugs mailing list archive at Nabble.com. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
