LilyPond 1.7.30 available

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

LilyPond 1.7.30 is available!  I expect that this is the last 1.8
prerelease.

The changes relative to .29 are lots of details in the documentation
and a few small fixes. Special thanks to Heikki, who corrected my
shoddy punctuation.

Binaries for RedHat9 are available from the usual location.



2003-08-03  Han-Wen Nienhuys  <[email protected]>

	* VERSION 1.7.30 released
	
	* GNUmakefile.in (EXTRA_DIST_FILES): remove lexer GCC patch.

	* buildscripts/mutopia-index.py (headertext): rewording

2003-08-02  Han-Wen Nienhuys  <[email protected]>

	* scm/new-markup.scm (strut-markup): new markup function.

	* scm/bass-figure.scm (make-bass-figure-markup): insert vertical
	space also when no accidental is there.

2003-08-02  Jan Nieuwenhuizen  <[email protected]>

	* input/les-nereides.ly: Updates.

2003-08-02  Heikki Junes <[email protected]>

	* lilypond-mode.el (LilyPond-insert-tag-current): new function,
	which repeats the tag insertion selected from "Insert tag" menu.

2003-08-02  Han-Wen Nienhuys  <[email protected]>

	* lily/all-font-metrics.cc (find_font): load AFM files first only
	for feta fonts. This fixes problems with TeXlive and other TeX
	distros that include AFM files for the CM fonts. 

	* scm/font.scm (qualifiers-to-font-name): remove.

	* lily/paper-def.cc: remove get_var.

	* input/trip.ly: remove file.
	
	* input/regression/spacing-note-flags.ly (raggedright): remove
	stafflinethickness

	* input/les-nereides.ly: update to new syntax, cleanups.

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

	* Documentation/user/refman.itely: Clarify shortest-note problem
	of autobeamer.

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

	* lilypond-mode.el: Add each word to regexps only once.

	* lilypond-mode.el (LilyPond-insert-tag): add new function, which 
	is based on the syntax definitions in lilypond.words. Remove all 
	LilyPond-insert-tag-* functions. Restructure LilyPond menu. 
	LilyPond->Insert menu is generated by the entries in lilypond.words 
	to which have been given a syntax definition.

	* lilypond.words: give syntax definitions (LilyPond-insert-tag) for 
	\notes, \relative, \score, \simultaneous, \transpose.

	* lilypond-mode.el: allow non-alpha characters only in menu keywords.

	* lilypond.words: add useful `\context Staff =' and `\context Voice ='.
	
	* lilypond-mode.el: add menu keywords separately.

	* lilypond.words: post-syntaxed slur pairs and syntax for \times.

2003-08-01  Mats Bengtsson  <[email protected]>

	* Documentation/topdocs/INSTALL.texi (Top): Documentation of the
	current ugly installation method for PFA fonts.

2003-07-31  Heikki Junes <[email protected]>

        * lilypond-mode.el: Junk LilyPond-quick-notes-insert; instruct 
	to use LilyPond Quick Insert Mode by Nicolas Sceaux, instead.

	* Documentation/user/music-glossary.tely: update legato.

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

	* lexer-gcc-3.0.patch: Remove.

	* lexer-gcc-3.1.sh: Disable FlexLexer.h massaging.

2003-07-30  Han-Wen Nienhuys  <[email protected]>

	* debian/rules (binary-arch): remove NEWS.

2003-07-30  Heikki Junes <[email protected]>

	* buildscripts/{ many }, lily/main.cc, po/{ all }, scripts{ many },
	stepmake/bin{ many }: polish the `--help's of different scripts;
	model taken from the core-utils of Linux.

	* flower/getopt-long.cc, python/lilylib.py: add space, see above.

2003-07-29  Han-Wen Nienhuys  <[email protected]>

	* flower/parse-afm.cc (parseCharMetrics): add warnings.

	* flower/libc-extension.cc: idem.

	* flower/include/libc-extension.hh: protect against isinf macros.

2003-07-29  Heikki Junes <[email protected]>

        * { many }: Use two uppercase letters in LilyPond.

	* lily/main.cc, po/{ many }, scripts/{ many }: add verbs.



-- 

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.