LilyPond 2.1.8 released

Han-Wen Nienhuys <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.announce
Message-ID <[email protected]>
Hi there,

2.1.8 is out.

The new feature biggie is that you can now change the appearance of
staffs and likes with \property.  Thanks to a Jan for a very sharp
observation about the code organization that enabled this.

Another change is in the website. As a result of the discussions on
the lilypond-user list, each page of the documentation links to a
WikiWiki (thanks to Ferenc Wagner for hosting it), where everyone is
welcome to add tips, comments and elucidations to the manual.


Enjoy! 


NEWS: 

   * Contexts may now be changed locally for an isolated music
     expression. For example,

            \new Voice \with {
               \consists "Pitch_squash_engraver"
            } {
              c'4
            }

   * The syntax for changing staffs has changed. The keyword `\change'
     should now be used, e.g.

            \change Staff = up

   * Features of spanner contexts, like `Staff', can now be changed
     using `\property', eg.

            \new Staff {
                 \property Staff.StaffSymbol \set #'line-count = #4
                 c'4
            }

     puts a quarter note C on a staff with 4 lines.




ChangeLog:

2004-01-09  Han-Wen Nienhuys   <[email protected]>

	* stepmake/bin/add-html-footer.py (built): add Wiki links to
	footer.

	* lily/parser.yy (translator_mod): allow \with { \remove .. }

	* lily/bar-check-iterator.cc (process): only warn if
	barCheckLastFail was changed.

	* scm/define-translator-properties.scm (barCheckLastFail): add
	property.

	* lily/main.cc (main_prog): print summary of failed files.

	* lily/axis-group-engraver.cc: move all spanner creation to
	process_music (). Now staffs can be adjusted with \override too.
	(Jan, you are a brilliant programmer!)
	
	* lily/chord-tremolo-engraver.cc (try_music): fix spurious warning. 

2004-01-08  Han-Wen Nienhuys   <[email protected]>

	* lily/translator-def.cc (get_translator_names): accept user
	tweaks too. 

	* mf/feta-bolletjes.mf (overdone_heads): oops, slashes are twice
	as big as normal heads. 

	* input/*ly: run convert-ly
	
	* lily/tuplet-bracket.cc (brew_molecule): call after_line_breaking
	() if dependencies are fluked.

	* scm/document-translation.scm (engraver-doc-string): update on
	latest string/symbol conventions.

	* lily/translator-ctors.cc: use Scheme_hash_table.

	* lily/translator-def.cc (get_translator_names): new function
	(add_context_mod): new function
	(get_accepted): new function

	* lily/parser.yy (context_mod): put all modifications of
	\translator { } in a single production, encode as SCM.

	* lily/translator-def.cc (add_context_mod): rewrite Translator_def
	to use read-only lists, so additions to the definition can be
	prepended easily.  

	* Documentation/user/invoking.itexi (Editor support): add node on
	editor support.

	* Documentation/user/refman.itely (Bar check): add lyrics example
	of bar checks. 

	* input/mutopia/F.Schubert/morgenlied.ly: add bar checks.

	* scripts/convert-ly.py (conv): add conversion rule.

	* lily/parser.yy: use \change iso. \translator for staff switch.

	* lily/my-lily-lexer.cc: add \change.

	* scm/define-translator-properties.scm
	(default-melisma-properties): add definition.

2004-01-07  Han-Wen Nienhuys   <[email protected]>

	* Documentation/user/refman.itely (Bar lines): clarification of
	systemStartDelimiter. 

	* input/test/slur-shape.ly (x): remove file.

	* lily/translator-group.cc (apply_property_operations): new function.

2004-01-06  Han-Wen Nienhuys   <[email protected]>

	* lily/parser.yy (optional_prop_ops): allow \with {
	PROPERTYSETTINGS } following \context or \new.

	* lily/my-lily-lexer.cc: add \with.

	* lily/parser.yy (property_operation): clean up definition of
	property operations.
	(property_op_to_music): new function.
	(context_spec_music): new function



-- 

 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.