LilyPond 2.1.35 released

Han-Wen Nienhuys <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.announce
Message-ID <[email protected]>
2.1.35 is out. It contains a great number of bugfixes, and a small
feature addition:

     Setting `raggedlast = ##t' in the `\paper' block causes the last
     line to be set flush-left instead of justified.

This release should be considered as the first LilyPond 2.2 release
candidate!  Please test this release to check if your scores come out
OK.

I would like to request proofreaders to take a look at the chapter
"Changing defaults." Parts of this chapter have been rewritten
recently, and haven't been scrutinized closely yet. 





2004-03-28  Han-Wen Nienhuys   <[email protected]>

	* VERSION: 2.1.35 released
	
	* scripts/convert-ly.py (FatalConversionError.sub_abs): convert
	context argument too.

	* make/ly-rules.make ($(outdir)/%.texi): use variable for outdir.

	* input/mutopia/W.A.Mozart/mozart-hrn-3.ly: Mozart died in 1791

	* python/lilylib.py (command_name): don't return 1st path
	component.

	* scripts/lilypond-book.py (Lilypond_snippet.is_outdated): treat
	.png case separately.

	* python/lilylib.py (system): typo.

2004-03-28  Jan Nieuwenhuizen  <[email protected]>

	* Documentation/user/preface.itely: Run texinfo-all-menus-update.
	Fixes compile.

	* lily/function-documentation.cc: Compile fix: Include <string.h>.
	Add header.

2004-03-27  Heikki Junes  <[email protected]>

	* vim/lilypond-indent.vim: small fixes.

2004-03-26  Mats Bengtsson  <[email protected]>

	* Documentation/user/notation.itely (Entering lyrics): Add example
	with correct english double quotes (at least for LaTeX output,
	maybe not a good idea if we switch to PS as the default output
	format).

2004-03-26  Han-Wen Nienhuys   <[email protected]>

	* lily/staff-performer.cc (create_audio_elements): play instrument
	changes before notes arrive. This fixes instrument of the first
	note in a score.

	* scripts/convert-ly.py (FatalConversionError.conv): add #'() case
	to 1.9.0 conversion.

	* lily/mark-engraver.cc: doc string.

	* make/lilypond.redhat.spec.in (Group): add vim scriptlets.

	* Documentation/user/introduction.itely (Introduction): new node.

2004-03-25  Han-Wen Nienhuys   <[email protected]>

	* lily/duration.cc (LY_DEFINE): dotcount argument is now optional.

	* input/regression/spacing-ragged-last.ly: new file.

	* lily/gourlay-breaking.cc (do_solve): add raggedlast support for
	spacing.

	* scm/font.scm: rewrite using GOOPS.
	
	* lily/context-def.cc (filter_engravers): derefence pointer.

	* lily/lily-guile.cc (type_check_assignment): use
	ly_scheme_function iso. scm_primitive_eval where possible.

	* lily/performance.cc (output): limit channels at 15. This fixes
	percussion inadvertently showing up in large scores.

2004-03-24  Han-Wen Nienhuys   <[email protected]>

	* input/regression/tuplet-gap.ly: new file.

	* lily/tuplet-bracket.cc (make_bracket): take gap interval.
	(print): compute gap length from number size, include italic
	correction.

	* scm/define-grobs.scm (all-grob-descriptions): remove gap from
	tuplet-bracket

	* scm/paper.scm (set-default-paper-size): new function, to be
	called at toplevel.
	(set-paper-size): new function, to be called inside \paper {}
	(set-default-paper-size): new function, to be called at toplevel.

	* lily/paper-def.cc (LY_DEFINE): ly:paper-def?: new function. 

	* lily/beam-performer.cc (process_music): idem.

	* lily/slur-performer.cc (process_music): stop melisma for stop event.
	
	* tex/titledefs.tex: remove scshape for piece.

	* lily/line-spanner.cc (line_stencil): font-encoding = music, not
	font-family

	* lily/time-signature.cc (special_time_signature): font-encoding
	not family.

	* lily/dynamic-engraver.cc (acknowledge_grob): fix typo, attach
	dynamic to head. This fixes p placement in morgenlied.

2004-03-23  Werner Lemberg  <[email protected]>

	* stepmake/stepmake/generic-targets.make (help): Improve text.



-- 

 Han-Wen Nienhuys   |   [email protected]   |   http://www.xs4all.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.