lily 1.7.12

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


Lily 1.7.11 is out. New features:

 * Lots of work for ligatures by Juergen. Please ask Jurgen for more
   information; it's all Latin to me.

 * Updates for the chordname code. You can now enter exceptions in a
   friendly syntax:

	epartial = \chordnames {
	    c:2^3 = \markup { \normal-size-super "2" }
	    c:3-  = \markup { "m" }
	}

   This defines chord name notation for the <<c d g>> and <<c es g>>
   and derivative chords as

	  2
	 C 


   and

         Cm

   More examples are in input/test/chord-names-dpnj.ly





2003-01-12  Han-Wen Nienhuys  <[email protected]>

	* lily/vaticana-ligature-engraver.cc (finish_primitive): compile fixes.

	* lily/gregorian-ligature.cc: new file

	* lily/*: the Great 2003 search & replace.

	* Documentation/user/refman.itely (Manual repeat commands): add
	note about font selection.

2003-01-12  Heikki Junes  <[email protected]>

	* lilypond-mode.el: propose recompiling midi while invoking playing,
	not while stopping playing.

2003-01-11  Heikki Junes  <[email protected]>

	* lilypond.words: add one.

	* lilypond-font-lock.el: add colour groups for horizontal, vertical 
	and expressional note grouping. Fontify chord modes.

2003-01-09  Heikki Junes  <[email protected]>

	* Documentation/user/music-glossary.tely (Top): translate melisma.

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

	* Documentation/user/music-glossary.tely (Top): add melisma.

2002-01-08  Juergen Reuter  <[email protected]>

	* lily/gregorian-ligature-engraver.cc: bugfix: added missing
	interfaces for (abstract) grob GregorianLigature

	* lily/vaticana-ligature-engraver.cc, lily/vaticana-ligature.cc:
	renamed head* -> glyph_name*, x-shift* -> x-offset*

	* scm/grob-property-description.scm: bugfix: added missing descriptions

2003-01-07  Jan Nieuwenhuizen  <[email protected]>

	* input/test/chord-names-dpnj.ly: New file.

	* scm/double-plus-new-chord-name.scm: Implement full and partial
	exceptions.

	* lily/lexer.ll: <markup>: Allow dash and hyphen in markup command.

	* scm/double-plus-new-chord-name.scm
	(double-plus-new-chord->markup): Fix sub->markup.


2003-01-07  Juergen Reuter  <[email protected]>

	* lily/custos-engraver.cc: added TODO; editorial changes

	* lily/ligature-bracket-engraver.cc: added typeset_ligature () for
	consistency with other ligature engravers; removed access on (now)
	private variable _ligature of Ligature_engraver

	* lily/include/ligature-engraver.hh, lily/ligature-engraver.cc:
	renamed last_bound -> last_bound_; issue programming_error on
	abstract method calls; moved primitives code from
	Mensural_bracket_engraver to here (because almost ligature
	engravers will need it); renamed try_stop_ligature () ->
	typeset_ligature (); bugfix: store primitives of finished ligature
	in separate variable finished_primitives_ to avoid clash on input
	like "\] \["; added current_ligature () to enable access on
	private variable _ligature

	* lily/mensural-ligature-engraver.cc: removed primitives_ code
	(now in super class); renamed try_stop_ligature () ->
	typeset_ligature ()

	* lily/mensural-ligature.cc: issue programming_error on abstract
	method calls

	* lily/note-heads-engraver.cc: added TODO comment upon bool
	in_ligature

	* mf/parmesan-heads.mf: fixed some of set_char_box()

	* scm/grob-description.scm: added VaticanaLigature

	* scm/grob-property-description.scm: added neume prefix properties

	* ly/gregorian-init.ly, lily/gregorian-ligature-engraver.cc,
	lily/include/gregorian-ligature-engraver.hh,
	lily/include/gregorian-ligature.hh: new files; framework for
	gregorian ligature engravers such as vaticana

	* lily/vaticana-ligature.cc, lily/vaticana-ligature-engraver.cc,
	lily/include/vaticana-ligature.hh, input/test/vaticana.ly:
	vaticana style ligature implementation (still somewhat uncomplete)


-- 

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.