From: fred Date: Sun, 24 Mar 2002 19:39:19 +0000 (+0000) Subject: lilypond-0.0.51 X-Git-Tag: release/1.5.59~4956 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=cb4f71a68a20302b9f07e7d804a9bfc9352b9e62;p=lilypond.git lilypond-0.0.51 --- diff --git a/Documentation/CodingStyle.pod b/Documentation/CodingStyle.pod index c1a9c7aed0..468c63a260 100644 --- a/Documentation/CodingStyle.pod +++ b/Documentation/CodingStyle.pod @@ -1,10 +1,10 @@ =head1 NAME -CodingStyle - standards while programming for LilyPond +CodingStyle - standards while programming for GNU LilyPond =head1 DESCRIPTION -Please use these standards while doing programming for LilyPond +Please use these standards while doing programming for GNU LilyPond Functions and methods do not return errorcodes, but use assert for checking status. @@ -115,8 +115,8 @@ Unfortunately most of the code isn't really documented that good. =head2 CLASSNAMES (2) -A lot of classes in LilyPond start with 'P', this is to distinguish -certain parts of LilyPond: the P stands for Printer, and the P-classes +A lot of classes in GNU LilyPond start with 'P', this is to distinguish +certain parts of GNU LilyPond: the P stands for Printer, and the P-classes are supposed to be more lowlevel than the others. Example: Staff uses PStaff, PScore and PCol to do the typesetting of diff --git a/Documentation/INSTALL.pod b/Documentation/INSTALL.pod index 4a0701b8b0..0d6c96e6eb 100644 --- a/Documentation/INSTALL.pod +++ b/Documentation/INSTALL.pod @@ -1,10 +1,10 @@ =head1 NAME -INSTALL - installing LilyPond +INSTALL - installing GNU LilyPond =head1 DESCRIPTION -This page documents installation and compilation of LilyPond +This page documents installation and compilation of GNU LilyPond =head1 IMPORTANT @@ -22,7 +22,7 @@ For compilation you need. =over 5 =item * -Unix. LilyPond is known to run on Linux, AIX, Digital Unix and +Unix. GNU LilyPond is known to run on Linux, AIX, Digital Unix and Solaris If you have the Cygnus WIN32 port of the GNU utils, it will @@ -66,7 +66,7 @@ Documentation. =head1 CONFIGURING and COMPILING -to install LilyPond, simply type: +to install GNU LilyPond, simply type: configure make install @@ -96,7 +96,7 @@ B<--help>. If you are not root, you will probably have to make it with configure --prefix=/home/me_myself_and_I/ -Since LilyPond currently is beta, You are advised to also use +Since GNU LilyPond currently is beta, You are advised to also use --enable-debug --enable-checking @@ -120,7 +120,7 @@ F. =head1 RUNNING -LilyPond does use a lot of resources. For operation you need the following: +GNU LilyPond does use a lot of resources. For operation you need the following: =over 5 @@ -154,14 +154,14 @@ Windows NT: you need the cygnus win32 gnu port development stuff; have a look at http://www.cygnus.com/gnu-win32. -to make LilyPond under, brr, aargh, well, simply type: +to make GNU LilyPond under, brr, aargh, well, simply type: bash configure make win32 =head1 PLATFORMS -LilyPond (pl 0.0.39) is known to compile on the following platforms: +GNU LilyPond (pl 0.0.39) is known to compile on the following platforms: * linux 2.0.28, g++ 2.7.2[.1] * aix 4.1, g++ 2.7.2 diff --git a/Documentation/faq.pod b/Documentation/faq.pod index 930ad89345..70162a6095 100644 --- a/Documentation/faq.pod +++ b/Documentation/faq.pod @@ -1,12 +1,32 @@ =head1 NAME -FAQ - LilyPond FAQs +FAQ - GNU LilyPond FAQs =head1 DESCRIPTION Some questions that have been answered before. -=head2 language +=head2 Language: mudela + +Q: Why can't you type C<#c> in stead of C ? + +A: We think that C<#c> looks as if you are entering the symbols to +print (which you are not; remember, you're entering the musical +content in Mudela) + +We're not sure on leaving out this feature. If you think this is a +good idea, please let us know. + +Be warned we will I allow you to leave out the C<#> if the note +already has an accidental. We won't allow + + c# c % no way! + +in stead of: + + cis cis + #c #c + Q: I can type @@ -73,9 +93,9 @@ simple front end to the complicated internals. Q: Why do I need g++ >= 2.7? -A: By using g++ LilyPond is portable to all platforms which support +A: By using g++, GNU LilyPond is portable to all platforms which support g++ (there are quite a few). Not having to support other compilers -saves us a I of trouble. LilyPond and FlowerLib use: +saves us a I of trouble. GNU LilyPond and FlowerLib use: =over 4 @@ -117,10 +137,10 @@ Q: I want a DOS/NT/W95 port. A.0: Reconsider. Try Linux. It's fun! -A.1: Currently (patchlevel 27), LilyPond (and flowerLib) compiles, links +A.1: Currently (patchlevel 27), GNU LilyPond (and flowerLib) compiles, links and runs on windhoos-nt, using the cygnus gnu port (release b17.1). I (JCN) only had to make a minor workaround for missing library calls. -Have a look at http://www.cygnus.com/gnu-win32. To make LilyPond type +Have a look at http://www.cygnus.com/gnu-win32. To make GNU LilyPond type C. (I am not promising to maintain this platform, it is just that when having to use doze, i-m sometimes too lazy to reboot.) diff --git a/NEWS b/NEWS index 237aac8d2f..cbcbe2102b 100644 --- a/NEWS +++ b/NEWS @@ -1,9 +1,18 @@ +pl 51 + - transposition bugfix + doco + - LilyPond -> GNU LilyPond + - bugfixes for Staff_side and Note_column* + - wohltemperirt: 12 more bars + +****** +april 11 pl 50 - merge rest / notehead. - Staff_side as a base class for most "staff-side" symbols. - version check - Note_column_register, Note_column - multiple scripts + ******** april 8 pl 49.jcn1 diff --git a/TODO b/TODO index 1ba47b577a..20b8e9aea5 100644 --- a/TODO +++ b/TODO @@ -5,10 +5,8 @@ before 0.1 * decent TeX page layout * per-pstaff item-widths - - * remove unnecessary or confusing constructs from .ly - * key undo + * script priority This is an assorted collection of stuff that will be done, might be done, or is an idea that I want to think about @@ -16,12 +14,12 @@ done, or is an idea that I want to think about PARSER * Duration-> Musical_duration, typedef Rational Duration? -MAKE-STUFF - - * do platform stuff: configure, header(s), targets, build (out?) - BUGS + * hairpin width + + * problems with empty staff. + * help-lines * help-lines for rests @@ -32,8 +30,12 @@ BUGS * lilypond - -> crash + * \stem -1 < chord > rest + SEVERELY LACKING: + * SPEED! + * grace notes FURTHER FOR ORCHESTRAL SCORE: @@ -69,6 +71,8 @@ SMALLISH PROJECTS * half-sharps, half-flats + * key undo + * unix style paths for LILYINCLUDE EN * rpm package buildroot @@ -117,7 +121,6 @@ SMALLISH PROJECTS * C meter iso 4/4 * textspanner: center position - * script-spacing * Brackets @@ -133,7 +136,8 @@ SMALLISH PROJECTS * add (good guess of) width to lyric items - * midi output: eat-up dynamic, key/meter/tempo changes, and write them neatly + * midi output: eat-up dynamic, key/meter/tempo changes, and +write them neatly * LilyPond .deb @@ -165,6 +169,9 @@ FUTURE * Junk Staff_column, and find the requests while walking the Voices.? + * MIDI repeat: make lily understand repeats + + * better beamslope calculation: QLP for beams? * implement better breaking algorithm @@ -181,6 +188,7 @@ FUTURE * piano staff + * vertical spanner IDEAS * integrate Register/Midi stuff @@ -224,3 +232,5 @@ IDEAS * #c <-> cis * breath marks + + * used fixedpoint arithmetic for min. energy.