+2006-06-13 Han-Wen Nienhuys <hanwen@lilypond.org>
+
+ * buildscripts/output-distance.py (test_compare_signatures):
+ timing routines.
+ (read_signature_file): use new signature format.
+
+ * scm/stencil.scm (write-system-signature): simpler signature
+ format.
+
+ * lily/stem.cc (calc_stem_end_position): calc quantized-positions
+ for beamed case. Backportme.
+
+ * lily/note-spacing.cc (stem_dir_correction): don't inspect
+ stem_end_position, but estimate instead. Backportme.
+
+ * lily/tuplet-bracket.cc (calc_positions): look at
+ stem-end-position for tuplet bracket slope. Fixes sloped tuplet
+ brackets narrower than beams. Backportme.
+
+ * lily/lexer.ll: set version-seen? even if version is
+ INVALID. Backportme.
+
+ * lily/rest.cc (y_offset_callback): bugfix: decide position
+ override based on scm_is_number(). Fixes \rest on center staff
+ line. Backportme.
+
+ * lily/beaming-pattern.cc (best_splitpoint_index): fix beaming
+ patterns for 16th triplets.
+
+2006-06-10 Graham Percival <gpermus@gmail.com>
+
+ * Documentation/user/ page.itely, global.itely: editing
+ and reorg.
+
+ * Documentation/user/ various: findex -> funindex.
+
+2006-06-10 Erik Sandberg <mandolaerik@gmail.com>
+
+ * lily/time-scaled-music-iterator.cc: Use tupletSpannerDuration to
+ insert extra tuplet events.
+
+2006-06-10 Graham Percival <gpermus@gmail.com>
+
+ * Documentation/user/programming-interfaces.itely: add
+ info from NEWS.
+
+ * python/convertrules.py: add annotatefoo -> annotate-foo
+ rules.
+
+ * Documentation/user/global.itely: start editing.
+
+ * Documentation/user/page.itely: major editing, new spacing
+ docs.
+
+2006-06-10 Han-Wen Nienhuys <hanwen@lilypond.org>
+
+ * scm/define-markup-commands.scm (wordwrap-markups): use
+ output-def 'line-width if undefined.
+
+ * 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