info-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

LilyPond 2.1.37 released


From: Jan Nieuwenhuizen
Subject: LilyPond 2.1.37 released
Date: Wed, 31 Mar 2004 18:53:22 +0200
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)

.37 is released.  Attractions are build fixes for SUSE and Cygwin,
bugfixes for the part combiner and chord tremolos.  The documentation
has some more polish, notably all info links should work, relative
octaves, indentation and linewidths of all examples should be OK.

CVS has already has some small fixes, but I hope this will be the
final release candidate; expect only regression bugs to be fixed
before 2.2.  Enjoy!


ChangeLog:

2004-03-31  Jan Nieuwenhuizen  <address@hidden>

        * VERSION: release 2.1.37.

2004-03-31  Han-Wen Nienhuys   <address@hidden>

        * configure.in: check for C language.

        * lily/source-file.cc: include strstream without h.

        * scm/documentation-generate.scm (string-append): use name without
        .texi.

        * autogen.sh (srcdir): SUSE fix.

        * Documentation/user/notation.itely (Ancient clefs): idem.

        * Documentation/user/lilypond-book.itely (Integrating HTML and music): 
idem.

        * Documentation/user/cheatsheet.itely (Cheat sheet): octave fixes.

        * lily/change-iterator.cc (process): use find_existing_context().

        * input/test/polymetric-differing-notes.ly: use ly:music-compress.

        * input/regression/repeat-unfold-tremolo.ly: new file.

        * scm/music-functions.scm (unfold-repeats): undo music compression
        too.

        * lily/music.cc (LY_DEFINE): rename to music-mutable-properties
        (LY_DEFINE): ly:music-compress new function.

        * scm/part-combiner.scm (determine-split-list): split for voice
        crossings

        * input/regression/part-combine-cross.ly: new file.

        * scm/part-combiner.scm (make-part-combine-music): don't do
        relative inside partcombine arguments.

        * scm/music-functions.scm (make-non-relative-music): new function.

        * Documentation/user/notation.itely (Automatic part combining):
        add note about \relative.

        * lily/part-combine-iterator.cc (construct_children): add
        start_moment_ member.

        * lily/chord-tremolo-engraver.cc (acknowledge_grob): trigger
        stem-tremolo by stem object. This fixes no stem for tremolo bug.

        * lily/stem-tremolo.cc (print): don't crash for no-stem.

        * Documentation/user/changing-defaults.itely (Which properties to
        change): fixes.

2004-03-31  Han-Wen Nienhuys   <address@hidden>

        * po/fr.po: update.

2004-03-31  Jan Nieuwenhuizen  <address@hidden>

        * input/wilhelmus.ly: More original lyrics.  Add to examples.

        * stepmake/stepmake/generic-targets.make ($(outdir)/dummy.dep):
        Reinstate old code that issues warning.  Fixes --srcdir build.

2004-03-30  Jan Nieuwenhuizen  <address@hidden>

        * input/wilhelmus.ly: New file.

        * Documentation/user/notation.itely: 
        * Documentation/user/introduction.itely:
        * Documentation/user/tutorial.itely: Use quote ly-option instead
        of explicit @quotation.  This fixes too long lilypond linewidths
        resulting in overful hboxes.

        * scripts/lilypond-book.py: Add ly-option: `quote'.

2004-03-30  Mats Bengtsson  <address@hidden>

        * tex/titledefs.tex: Avoid that the first score line is extra
        indented if instrument is defined but not piece.

2004-03-30  Werner Lemberg  <address@hidden>

        * Documentation/user/macros.itexi (@internalsref) [info]: Prepend
        `lilypond/' to info file name.
        (@usermanref) [info]: New variant.

        * scm/documentation-generate.scm: Fix definition of @usermanref
        and @glossaryref (in the `ifinfo' branch) by prepending `lilypond/'
        to info file name.


-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org





reply via email to

[Prev in Thread] Current Thread [Next in Thread]