On Jan 19, 2011, at 10:53 PM, Graham Percival wrote: > On Wed, Jan 19, 2011 at 10:28:38PM +0100, Jan Warchoł wrote: >> 2011/1/19 Mike Solomon <mike...@ufl.edu>: >>> It may be worth it to add this to the issue tracker and get this fixed in >>> one of the first 2.14 bug fixes (if not 2.14 itself) - thoughts? >> >> In my opinion this issue is important and potentially widespread, and >> as such it should be considered a high priority one. > > In my opinion, I don't care about your opinion, but I *do* care > about evidence of bugs. Please submit a bug report and let's get > it in the tracker. Doubly so if it's a regression.
That's part of the problem. Is it a bug if something changed? Technically, no, as far as I understand the term "bug". Is it convoluted and difficult to use? Would graham's mother have difficulty understanding the documentation on getting a simple arrangement for her church choir to work the same way in 2.13 as it did in 2.12? Probably. If I opened a bug report that was essentially, "Lyrics are now more difficult to use. Type - Regression, Priority - Critical", someone would probably close is as invalid very quickly. Exactly this reasoning was the reason for my question, "what advantages does the new lyric spacing offer?" I think if we understand this, we can understand how to explain it, and make it easy for people to understand what needs to change and how. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
