From 8ae06a9242edb87d1ccff852b993254c6fb3c235 Mon Sep 17 00:00:00 2001 From: fred Date: Sun, 24 Mar 2002 20:04:18 +0000 Subject: [PATCH] lilypond-0.1.36 --- Documentation/faq.pod | 61 ++++++++++++++++++++++++++--------------- Documentation/links.pod | 4 --- NEWS | 12 ++++++++ 3 files changed, 51 insertions(+), 26 deletions(-) diff --git a/Documentation/faq.pod b/Documentation/faq.pod index e9eb1d4a73..15487142b0 100644 --- a/Documentation/faq.pod +++ b/Documentation/faq.pod @@ -182,6 +182,45 @@ Q: How do I change the TeX layout? A: See F, it has some comments. + + +=head2 Development + +Q: Could you implement feature XXXX? It is really easy, just extend +the syntax to allow YYYY! + +A: If it is reasonable, I'll add XXXX to the TODO list. In general +finding a cute syntax (such as YYYY) isn't very hard. The complicated +issue how to adapt the internals to do XXXX. The parser is really a +simple front end to the complicated internals. + +Q: Can I join in on LilyPond development? How do I do this? + +A: LilyPond development is open for anyone who wants to join. We try +to use a Bazaar style development model for LilyPond, see +http://locke.ccil.org/~esr/writing/cathedral.html. This means: +frequent releases, everyone can send in a patch or do suggestions and +all development discussions are public. + +To be precise, discussions take place on the gnu-music-discuss mailing +list, which is open for subscription to everyone. + + +Q: I want to implement XXXX! Should I do this? + +A: There might be better ways of doing XXXX, so it's a good thing to +ask about this before you start hacking. If you want to keep in touch +with current developments, you should subscribe to the mailing list +(see the "links" section of the documentation). + + +Q: I want to implement XXXX! How should I do this? + +A: Your best bet of getting me to include code, is to present it as a +"fait accompli", ie., to send me a patch. + + + Q: How do I learn the C++ code? A: The entry point is in C. Good luck. :-) @@ -210,28 +249,6 @@ Q: Why GPL? A: Yes. -Q: Could you implement feature XXXX? It is really easy, just extend -the syntax to allow YYYY! - -A: If it is reasonable, I'll add XXXX to the TODO list. In general -finding a cute syntax (such as YYYY) isn't very hard. The complicated -issue how to adapt the internals to do XXXX. The parser is really a -simple front end to the complicated internals. - - -Q: I want to implement XXXX! Should I do this? - -A: There might be better ways of doing XXXX, so it's a good thing to -ask about this before you start hacking. If you want to keep in touch -with current developments, you should subscribe to the mailing list -(see the "links" section of the documentation). - - -Q: I want to implement XXXX! How should I do this? - -A: Your best bet of getting me to include code, is to present it as a -"fait accompli", ie., to send me a patch. - Q: Why do I need g++ >= 2.7? diff --git a/Documentation/links.pod b/Documentation/links.pod index 7a77721c8f..dc1d9d8004 100644 --- a/Documentation/links.pod +++ b/Documentation/links.pod @@ -25,10 +25,6 @@ LilyPond sources. An enormous collection of music related URLs -=item http://art.ucsc.edu/faculty/cope/home - -See New Scientist, aug 9 1997. - =back =head2 Ftp diff --git a/NEWS b/NEWS index 1c5b06fafb..8bd448b3c4 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,16 @@ +pl 36 + - bf: notehead collisions + - bf: dot y-position + - use Item::break_priority_i_ for horizontal alignment of breakables. + (it still sucks) + - junk some derivation checks, junk Normal_*_bar + - FlowerLib fixes. + - twinkle fixes. + - feta: flag/clefspacing + +******* +dec 5 pl 35 - naming: lily-init iso symbol.ly - mf braces -- 2.39.5