lilypond 1.5.73

Han-Wen Nienhuys <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.announce
Message-ID <[email protected]>
.73 is out.

It contains The Final Fix for beamed stem-lengths, and stdin input for
ly2dvi and tablature hammer & pull. Also, there are a bunch of
documentation fixes.


Share and Enjoy.


Go forth and Multiply.


2002-08-14 <[email protected]>

	* scm/output-lib.scm: Support of hammers and pulls in tablature
	-- Hammers and pulls are inserted exactly like slurs, and a "H" or
	a "P" is added over the slur as needed.  

	* ./input/test/tablature-hammer.ly: example of hammer, pull and
	legato in a tablature.

	* ly/engraver-init.ly: Stem.up-to-staff is now disabled by
	default, since it appears that most of the published tablatures
	are not like that.

2002-08-13  Han-Wen Nienhuys  <[email protected]>

	* lily/beam.cc (brew_molecule): use
	Staff_symbol_referencer::staff_space for thickness.

2002-08-14  Jan Nieuwenhuizen  <[email protected]>

	* Documentation/user/lilypond.tely: Add dir entries for
	executables.

	* Documentation/user/converters.itely: 
	* Documentation/user/invoking.itexi: Fix `invocation' node names,
	in line with standard dir entries.

	* Documentation/user/convert-ly.itexi
	* Documentation/user/ly2dvi.itexi: Remove.
	
	* scripts/ly2dvi.py: Add pseudo-filter (and stdout output)
	support.

	* lily/main.c: 
	* lily/paper-score.cc : 
	* lily/gourlay-breaking.cc: Write info to stderr.

	* buildscripts/help2man.pl: Update to latest version from Debian.
	Fixes generation of man pages with perl 5.6.1.

	* GNUmakefile.in: Add python link to build-datadir.  Fixes
	generation of midi2ly man page.

2002-08-14  Mats Bengtsson  <[email protected]>

	* Documentation/user/{tutorial.itely, introduction.itely}: 
	Small fixes.

2002-08-13  Jan Nieuwenhuizen  <[email protected]>

	* lily/beam.cc (least_squares): Add comment.

	* input/regression/beam-center-slope.ly: Update.

	* lily/beam-quanting.cc (score_stem_lengths): Revert oops.

	* input/template/melody-chords.ly: New file.

	* lily/stem.cc (calc_stem_info): Move, document, clean up and fix
	up-to-stem feature.

	* ly/grace-init.ly (startGraceMusic):
	* scm/grob-description.scm (beamed-lengths): Subtract half a beam
	thickness, to fix most ugly beams.  See input/test/stem.ly and
	baerenreiter-sarabande.ly.

	* input/test/stem.ly:
	* input/mutopia/J.S.Bach/baerenreiter-sarabande.ly: Play with
	beamed-lengths.

	* input/test/spacing.ly: Give enough room to test spacing.

	* cygwin/post-lilypond.sh: Fix and update.

	* cygwin/zlily-profile.sh: Remove.

2002-08-12  Jan Nieuwenhuizen  <[email protected]>

	* GNUmakefile.in (EXTRA_DIST_FILES): Add server.el.patch.

	* scm/grob-property-description.scm
	(beamed-extreme-minimum-free-lengths): New property, now correctly
	named.

	* ly/grace-init.ly: New beam property updates.

	* input/les-nereides.ly: Updates.

	* cygwin/README.in: New file.

	* input/sondag-morgen/GNUmakefile: 
	* input/mutopia/R.Schumann/GNUmakefile: New file.

	* scm/grob-property-description.scm (beamed-minimum-free-lengths):
	(beamed-extreme-free-lengths): New property.

	* lily/beam.cc (forced_stem_count): Count boundary cases too.
	(set_stem_shorten): Integer divide bug fix.

	* input/mutopia/J.S.Bach/baerenreiter-sarabande.ly: Really expect
	six systems, change warning into error.

	* scm/grob-description.scm (beamed-stem-shorten): Shorten 8th
	beams same as normal stem (one staffspace), high order beams less
	(arbitrary guess).
	(beamed-lengths): Standard length for all beams.
	(beamed-minimum-free-lengths):
	(beamed-extreme-minimum-free-lengths): New property.

	* input/regression/beam-default-lengths.ly: 
	* input/regression/beam-shortened-lengths.ly: New file.

	* lily/stem.cc (get_stem_info): New function.
	(calc_stem_info): Partial rewrite.

	* scm/grob-description.scm (Beam): same beamed-stem-shorten for
	all beam counts.


-- 

Han-Wen Nienhuys   |   [email protected]    | http://www.cs.uu.nl/~hanwen/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.