]> git.donarmstrong.com Git - lilypond.git/blobdiff - ChangeLog
trim outdated info.
[lilypond.git] / ChangeLog
index 85683a1c7368b98bb3e914ce7575a0aaea355e14..8cce756d72353df1af787a7922070812d4b0647c 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,157 @@
+2006-06-10  Han-Wen Nienhuys  <hanwen@lilypond.org>
+
+       * HACKING: trim outdated info.
+
+2006-06-09  Mats Bengtsson  <mabe@drongo.s3.kth.se>
+
+       * scm/define-grobs.scm (all-grob-descriptions): Add
+       line-spanner-interface to all grobs that already have
+       text-spanner-interface or dynamic-text-spanner-interface
+
+       * scm/page.scm: Rename annotate{headers,systems,page}->
+       annotate-*
+
+       * input/regression/page-spacing.ly,
+       input/regression/page-layout-manual-position.ly: idem
+
+
+2006-06-09  Han-Wen Nienhuys  <hanwen@lilypond.org>
+
+       * lily/line-spanner.cc: cleanup property list.
+
+       * scripts/lilypond-book.py (find_toplevel_snippets): don't use
+       generator expressions (2.3 compat). 
+
+2006-06-09  Mats Bengtsson  <mabe@drongo.s3.kth.se>
+
+       * lily/vertical-align-engraver.cc: Make sure that the
+       align{Above,Below}Context properties are included in the automatic
+       documentation.
+
+2006-06-08  Joe Neeman  <joeneeman@gmail.com>
+
+       * scm/paper-system.scm (paper-system-annotate): also annotate the
+       estimated pure-Y-extent
+
+       * scm/define-grobs.scm: add pure-Y-extent and pure-Y-offset functions
+
+       * lily/system.cc (break_into_pieces): set the estimated height
+       of each child system
+
+       * lily/stem.cc (pure_height): new pure-Y-extent callback
+
+       * lily/staff-symbol-referencer.cc (callback): don't destroy
+       the staff-position property
+
+       * lily/hara-kiri-group-spanner.cc (request_suicide): split
+       consider_suicide into two functions
+
+       * lily/constrained-breaking.cc (resize): use the new pure
+       callbacks to estimate the height of a system
+
+       * lily/axis-group-interface.cc (pure_group_height): new
+       side-effect-free VerticalAxisGroup height-callback
+
+       * lily/align-interface.cc (get_extents_aligned_translates):
+       split align_elements_to_extents into two functions
+       (get_pure_child_y_translation): new function
+
+       * lily/grob.cc: new functions for pure-Y-extent and pure-Y-offset
+
+       * lily/item.cc: new functions pure_is_visible and spanned_rank_iv
+
+       * lily/paper-score.cc: cache break_indices and columns
+
+       * lily/side-position-interface.cc: new pure-Y-extent callbacks
+       
+2006-06-08  Han-Wen Nienhuys  <hanwen@lilypond.org>
+
+       * lily/font-config.cc (init_fontconfig): do the init if
+       cache_file, but don't look at cache_file.
+
+       * input/regression/quote-tie.ly: new file.
+
+       * lily/tie-engraver.cc (struct Head_event_tuple): add end_moment_
+       to Head_event_tuple, so we deal gracefully with ties on
+       cue-endings.
+
+       * lily/pango-font.cc (pango_item_string_stencil): type correctness
+       for FcChar8*
+
+2006-06-08  Graham Percival  <gpermus@gmail.com>
+
+       * input/test/ smart-transpose.ly, reverse-music.ly:
+       \applyMusic to music functions update, thanks Michael!
+
+2006-06-07  Graham Percival  <gpermus@gmail.com>
+
+       * input/test/ add-staccato.ly, add-text-script.ly,
+       unfold-all-repeats.ly, music-box.ly: \applyMusic to
+       music functions update, thanks to Michael Meixner.
+
+       * Documentation/user/music-glossary.tely: small fix
+       from Francisco.
+
+       * Documentation/user/ various: minor additions from mailist.
+
+       * Documentation/user/lilypond.tely, basic-notation.itely:
+       small test of @funindex.  (works here)
+
+       * input/test/font-table.ly: reduce size to partially
+       de-ugly version in manual.
+
+       * Documentation/user/page.itely: new file (split former
+       "global issues" into "page settings" and "non-musical
+       output".
+
+       * Documentation/user/ various: fix @ref{}s to match
+       new chapter names (above).
+
+2006-06-07  Jan Nieuwenhuizen  <janneke@gnu.org>
+
+       * SConstruct (LILYPONDPREFIX): Bootstrap fix.
+
+2006-06-06  Graham Percival  <gpermus@gmail.com>
+
+       * Documentation/user/advanced-notation.itely: add example
+       for segno/coda on barline.
+
+       * tex/texinfo.tex: merge from upstream.
+
+2006-06-06  Jan Nieuwenhuizen  <janneke@gnu.org>
+
+       * scripts/lilypond-book.py (process_snippets): Argument fix.
+
+       * SConstruct:
+       * buildscripts/builder.py:
+       * lily/SConscript: 
+       * mf/SConscript: 
+       * Documentation/user/SConscript:  More SCons fixes.
+
+2006-06-03  Jan Nieuwenhuizen  <janneke@gnu.org>
+
+       * lily/font-config.cc (init_fontconfig): Only initialize if
+       global cache_file is found.
+
+2006-06-06  Erik Sandberg  <mandolaerik@gmail.com>
+
+       * ly/music-functions-init.ly: Updated \overrideProperty to use the
+       new \applyOutput.
+
 2006-06-06  Han-Wen Nienhuys  <hanwen@lilypond.org>
 
+       * VERSION (PACKAGE_NAME): release 2.9.8
+
+       * lily/ledger-line-engraver.cc (stop_translation_timestep): new
+       function. Delay ledger modifying ledgered grobs to
+       stop_translation_timestep(), to ensure that we're ledgering
+       according to the new spanner.
+       (acknowledge_staff_symbol): don't check for non-NULL
+       staff_sym->get_bound()
+
+       * lily/staff-symbol-engraver.cc (start_spanner): set left bound on
+       creation.
+
        * Documentation/pictures/GNUmakefile (XPM_FILES): src-wildcard for
        pictures too.
 
 
 2006-06-06  Jürgen Reuter  <reuter@ipd.uka.de>
 
+       * Documentation/user/instrument-notation.itely,
+       input/regression/breathing-sign-ancient.ly,
+       input/test/divisiones.ly: Removed redundant property settings for
+       vaticana contexts.
+
        * ly/gregorian-init.ly: Rewrote \versus and \responsum in order to
        fix lyrics alignment problems.  They are implemented now as scheme
        functions that add the appropriate unicode char to the first lyric
-       event rather than adding a separate lyric event.
+       event rather than adding a separate lyric event.  Minor edit of
+       comments.
 
 2006-06-06  Han-Wen Nienhuys  <hanwen@lilypond.org>