* don't duplicate entries from news-front.itexi
@end ignore
+@newsItem
+@subheading LilyPond 2.19.53 released @emph{December 17, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.53. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@newsItem
+@subheading LilyPond 2.19.52 released @emph{December 4, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.52. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.51 released @emph{November 20, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.51. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.50 released @emph{November 6, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.50. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.49 released @emph{October 16, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.49. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.48 released @emph{September 13, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.48. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.47 released @emph{August 31, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.47. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.46 released @emph{July 26, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.46. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.45 released @emph{July 09, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.45. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.44 released @emph{June 21, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.44. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.43 released @emph{June 8, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.43. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.42 released @emph{May 15, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.42. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.41 released @emph{May 1, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.41. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.40 released @emph{April 17, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.40. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.39 released @emph{March 27, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.39. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.38 released @emph{March 13, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.38. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.19.37 released @emph{February 28, 2016}
+
+We are happy to announce the release of LilyPond
+2.19.37. This release includes a number of enhancements, and contains some
+work in progress. You will have access to the very latest features, but
+some may be incomplete, and you may encounter bugs and crashes. If you
+require a stable version of LilyPond, we recommend using the 2.18
+version.
+
+@newsEnd
+
@newsItem
@subheading LilyPond 2.19.36 released @emph{January 31, 2016}
2.19.36. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.35. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.34. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.33. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.32. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.31. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.30. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.29. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.28. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.27. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.26. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.25. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.24. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.23. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.22. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.21. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.20. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.19. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.18. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.17. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
2.19.16. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
We would like to acknowledge and thank Masamichi Hosoda for making this
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
-require a stable version of Lilypond, we recommend using the 2.18
+require a stable version of LilyPond, we recommend using the 2.18
version.
@newsEnd
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.18 version.
+a stable version of LilyPond, we recommend using the 2.18 version.
@newsEnd
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.18 version.
+a stable version of LilyPond, we recommend using the 2.18 version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond production named BEST EDITION 2014 @emph{March 11, 2014}
+
+We are thrilled that the edition of the songs of Oskar
+Fried (1871-1941), published recently by our fellow contributors Urs Liska
+and Janek Warchoł [1], received the "Musikeditionspreis BEST EDITION
+2014" of the German Music Publishers' Association [2]. The ceremony
+took place at the Frankfurt Musikmesse.
+
+We congratulate Janek and Urs for gaining such public recognition of
+typographical and editorial excellence of their work. We are also delighted
+to inform you that they intend to make their work available under a Free
+license as soon as the publisher expenses are covered. Please support this
+initiative by buying the printed volume through the publisher [3].
+
+[1] @uref{http://lilypondblog.org/category/fried-songs}@*
+[2] @uref{http://www.best-edition.de}@*
+[3] @uref{http://www.sound-rel.de}@*
@newsEnd
+
@newsItem
@subheading LilyPond 2.19.3 released @emph{March 2, 2014}
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.18 version.
+a stable version of LilyPond, we recommend using the 2.18 version.
@newsEnd
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.18 version.
+a stable version of LilyPond, we recommend using the 2.18 version.
@newsEnd
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.18 version.
+a stable version of LilyPond, we recommend using the 2.18 version.
@newsEnd
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.18 version.
+a stable version of LilyPond, we recommend using the 2.18 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
This update cures the issue with the Windows version crashing with a problem
with positioning text.
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond blog. @emph{June 2, 2013}
+
+Janek Warchoł has created a LilyPond blog. You can find it at
+@uref{http://lilypondblog.org/, lilypondblog.org}!
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
where they should be) and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
+
+@newsEnd
+
+@newsItem
+@subheading LilyPond 2.16.2 released! @emph{January 4, 2013}
+
+We are happy to announce the release of LilyPond 2.16.2. This release is mainly
+to correct a problem with lilypond-book running on Windows. We recommend that
+only people requiring this functionality upgrade to this version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
+@newsItem
+@subheading The LilyPond Report #28. @emph{November 12, 2012}
+
+The @uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?The-LilyPond-Report-28, October
+issue of the @emph{LilyPond Report}} focuses on the
+@uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?LilyPond-meeting-in-Waltrop,
+meeting of LilyPond developers and users} in Waltrop, Germany last
+August. Of course, there are also some musings on LilyPond
+triggered by the release of 2.16.0 and 2.17.0 occuring from that
+venue.
+
+There are also two monthly financial reports from David Kastrup
+whose work on LilyPond is
+@uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?The-LilyPond-Report-24#an_urgent_request_for_funding,
+solely paid for} by financial contributions from other developer
+and users (thank you!), and a report about experiences from
+@uref{http://scorio.com, a web-based music typesetting service}
+using LilyPond internally.
+
+Come @uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?The-LilyPond-Report-28, read
+LilyPond Report 28} now; comments and contributions are warmly
+encouraged!
+@newsEnd
+
@newsItem
@subheading LilyPond 2.16.1 released! @emph{November 9, 2012}
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
-a stable version of Lilypond, we recommend using the 2.16 version.
+a stable version of LilyPond, we recommend using the 2.16 version.
@newsEnd
@newsEnd
@newsItem
-@subheading Lilypond 2.16.0 released! @emph{August 24, 2012}
+@subheading LilyPond 2.16.0 released! @emph{August 24, 2012}
We are proud to announce the release of GNU LilyPond 2.16.0.
LilyPond is a music engraving program, devoted to producing the
traditionally engraved music to computer printouts.
Many improvements have been made in the past year since the previous
-main stable version. A few major improvements are:
+main stable version. A few major improvements are:
@itemize
@item
@item
User and programming interfaces have greatly improved
@item
-Music functions have become quite more versatile
+Music functions have become quite more versatile
@end itemize
A full list of new features is given in:
Translation contributors:
-Jean-Charles Malahieude, Till Paala, Yoshiki Sawada
+Jean-Charles Malahieude, Till Paala, Yoshiki Sawada
@newsEnd
@newsItem
-@subheading Lilypond 2.15.95 released! @emph{August 11, 2012}
+@subheading LilyPond 2.15.95 released! @emph{August 11, 2012}
We are excited to announce the release of LilyPond 2.15.95.
With this release, development on version 2.15 is frozen for the
@uref{http://www.linux-magazine.com,Linux Magazine} publishes an
article in the May 2011 issue titled
-@uref{http://www.linux-magazine.com/w3/issue/126/088-090_projects.pdf,
+@uref{http://www.linux-magazine.com/content/download/61706/482546/version/1/file/088-090_projects.pdf,
Projects on the Move}. It is an introduction to MuseScore,
LilyPond and Chordii. Author Carla Schroder states @qq{LilyPond is
driven from the command line, but don’t let the lack of a GUI scare
@subheading The LilyPond Report #13. @emph{June 23, 2008}
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-13,this link} to read the full issue...
+Follow @uref{http://web.archive.org/web/20120220123759/http://news.lilynet.net/?The-LilyPond-Report-13,this link} to read the full issue...
@newsEnd
@subheading The LilyPond Report #12. @emph{June 16, 2008}
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-12,this link} to read the full issue...
+Follow @uref{http://web.archive.org/web/20120220123754/http://news.lilynet.net/?The-LilyPond-Report-12,this link} to read the full issue...
@newsEnd
@subheading The LilyPond Report #11. @emph{June 9, 2008}
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-11,this link} to read the full issue...
+Follow @uref{http://web.archive.org/web/20120220123750/http://news.lilynet.net/?The-LilyPond-Report-11,this link} to read the full issue...
@newsEnd
@subheading The LilyPond Report #10. @emph{June 2, 2008}
Welcome to this special tenth issue of the @emph{LilyPond Report}, entirely dedicated to Algorithmic Composition systems.@*
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-10,this link} to read the full issue...
+Follow @uref{http://web.archive.org/web/20120220123743/http://news.lilynet.net/?The-LilyPond-Report-10,this link} to read the full issue...
@newsEnd
Welcome to this ninth issue of the @emph{LilyPond Report}!@*
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-9,this link} to read the full issue...
+Follow @uref{http://web.archive.org/web/20120220123946/http://news.lilynet.net/?The-LilyPond-Report-9,this link} to read the full issue...
@newsEnd
Release 2.11.28 is now available as a binary installer for
FreeBSD x86_64. Download
-@uref{http://lilypond.org/download/binaries/freebsd-64/lilypond-2.11.28-1.freebsd-64.sh,the installer} and
+@uref{http://lilypond.org/downloads/binaries/freebsd-64/,the installer} and
do @emph{sh lilypond-2.11.28-1.freebsd-64.sh} in a command window.
@newsEnd
Starting with 2.7.26, the development team has been working on the
installers. We're proud to announce another version of these: they are
now available for
-@uref{http://lilypond.org/download/binaries/linux-x86/lilypond-2.7.27-1.linux.sh,
+@uref{http://lilypond.org/downloads/binaries/linux-x86/,
Linux/x86},
-@uref{http://lilypond.org/download/binaries/MacOS/lilypond-2.7.27-2.zip,
+@uref{http://lilypond.org/downloads/binaries/darwin-ppc/,
MacOS X} and
-@uref{http://lilypond.org/download/binaries/mingw/lilypond-2.7.27-2.exe,
+@uref{http://lilypond.org/downloads/binaries/mingw/,
Windows}.
@newsEnd
@newsItem
@subheading February 28, 2005
-LilyPond 2.5.13 is available for Fedora Core 3. You need to install @uref{http://lilypond.org/download/binaries/Fedora-3/ghostscript-8.15rc3-0.i386.rpm,ESP
-Ghostscript 8.15rc3}. Unfortunately, this version of Ghostscript
+LilyPond 2.5.13 is available for Fedora Core 3. You need to install
+Ghostscript 8.15rc3. Unfortunately, this version of Ghostscript
lacks the IJS dynamic library, which means that it will conflict with
the gimp-print package. You may install it with --nodeps. Use at your
own risk.
release has many internal code cleanups. In addition,
accuracy of error reporting has been improved.
See the
-@uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3065&content-type=text/vnd.viewcvs-markup,
+@uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,
change log
} and @ref{Old downloads}!
@newsEnd
font code by Werner.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3048&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
SVG and GNOME backends are broken, most probably.
@ref{Old downloads}
and check out the
-changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3013&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
while we stabilize the Pango/FontConfig integration.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev= 1.3000&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
handling for the GNOME backend and SVG backend.
@ref{Old downloads}
and check out the
-changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2974&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
expression.
@ref{Old downloads}
and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2908&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+check out the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
changed to accomodate the solfa-notation.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2898&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
various bugfixes.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2881&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
applied to the PS and TeX output as well.
@ref{Old downloads}
and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2837&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
fixes that were made to 2.4.0 last week.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2780.2&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
some problems with the conversion scripts.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2773&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
important fix for raggedbottom page-layout.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2765&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
backend, and a bunch of other small fixes.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2752&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
candidate for LilyPond 2.4.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2742&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
\paper@{@}.
@ref{Old downloads}
and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2709&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+check out the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
code.
@ref{Old downloads}
and check
-out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2692&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+out the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
in the documentation.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2674&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
@newsItem
@subheading September 29, 2004
-The LilyPond development team will be present at the @uref{http://www.nluug.nl/events/sane2004/bazaar/index.html,Free
+The LilyPond development team will be present at the @uref{https://web.archive.org/web/20040811160307/http://www.nluug.nl/events/sane2004/bazaar/index.html,Free
Software Bazaar} of the NLUUG SANE 2004 conference today. If you
are in the neighborhood, drop by for live contact with the Team or
just a friendly chat. Registration is not required to attend.
LilyPond 2.3.19 is out. It's mainly a bugfix release.
@ref{Old downloads}
and check out the changes
-in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2652&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
similarly.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2614&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
will hold users back in switching.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2562&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
only notes and rests end up in quotes.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2553&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
other.
@ref{Old downloads}
and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2534&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
again.
@ref{Old downloads}
and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2520&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+check out the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
disappearing metronome mark.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.33&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
`doubleSlurs' property.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2489&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
annoying bugs fixed.
@ref{Old downloads}
and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2449&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
@ref{Old downloads}
and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2435&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
projected date for this to happen is in about a month.
@ref{Old downloads}
and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2416&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
separate. This also required a cleanup of the Ambitus
implementation.
@ref{Old downloads}
-and check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2395&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+and check out the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
beat within the measure.
@ref{Old downloads}
and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2383&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
2.3.x.
@ref{Old downloads}
and check
-out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.28&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+out the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
formatting, and was also present in the 2.2 series.
@ref{Old downloads}
and check out the changes
-in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2306&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
release.
@ref{Old downloads}
and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.23&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+check out the changes in the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}.
@newsEnd
scm/output-gnome.scm and try to run
buildscripts/guile-gnome.sh to see what the fuss is all about.
Carl Sorensen also provided us with more patches to the
-fret-diagram output. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2293&content-type=text/vnd.viewcvs-markup,ChangeLog}
+fret-diagram output. Check out the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}
and
@ref{Old downloads}.
@newsEnd
@newsItem
@subheading June 20, 2004
LilyPond 2.2.3 has a turkish translation and fixes a few minor
-bugs that were reported over the past month. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.16&content-type=text/vnd.viewcvs-markup,ChangeLog} for a full description and
+bugs that were reported over the past month. Check out the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog} for a full description and
@ref{Old downloads}.
@newsEnd
@subheading June 13, 2004
LilyPond 2.3.4 further improves the output backends. As a
result, manual page-breaks, multiple output formats and putting
-@code{\score} into markups now works. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2242&content-type=text/vnd.viewcvs-markup,ChangeLog}
+@code{\score} into markups now works. Check out the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}
and
@ref{Old downloads}.
@newsEnd
@subheading May 31, 2004
LilyPond 2.3.3 has many internal changes relating to the output
backend (PostScript) and page-layout. In addition, it contains a few
-bugfixes for recently reported problems. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2207&content-type=text/vnd.viewcvs-markup,ChangeLog}
+bugfixes for recently reported problems. Check out the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}
and
@ref{Old downloads}.
@newsEnd
@newsItem
@subheading May 31, 2004
LilyPond 2.2.2 is out. It has a number of small bugfixes, so upgrade
-if any of these errors concern you. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.9,ChangeLog}
+if any of these errors concern you. Check out the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd3c36946e4c341b0abb0f1c6bbdbc12883c1,ChangeLog}
or head straight to the
@ref{Old downloads}.
@newsEnd
@subheading January 18, 2004
LilyPond 2.1.11 is now also
available for Windows! For downloading, go
-@uref{http://www.inf.bme.hu/~berti/lilypond/,here}.
+@uref{https://web.archive.org/web/20040204191423/http://www.inf.bme.hu/~berti/lilypond/,here}.
@newsEnd
@subheading October 11, 2003
LilyPond 2.0.1 binaries for Mandrake 9.1
available from
-@uref{http://rpm.nyvalls.se/sound9.1.html,here}
+@uref{https://web.archive.org/web/20031006165051/http://rpm.nyvalls.se/sound9.1.html,here}
thanks to Heikki Junes.
@newsEnd
@newsItem
@subheading September 27, 2003
PlanetCCRMA has been updated to include LilyPond 2.0. Go
-@uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,
+@uref{http://ccrma.stanford.edu/planetccrma/software/soundapps.html#SECTION000621700000000000000,
here} to download. Thanks to Fernando Pablo
Lopez-Lezcano!
@newsEnd
@newsItem
@subheading August 25, 2003
Mandrake 9.1 RPMS available, get them
-@uref{http://rpm.nyvalls.se/sound9.1.html,here}.
+@uref{https://web.archive.org/web/20031006165051/http://rpm.nyvalls.se/sound9.1.html,here}.
@newsEnd
@subheading August 18, 2003
PlanetCCRMA (eg. RedHat 8 and 9)
has been updated to 1.8.
-Download @uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,here.}
+Download @uref{http://ccrma.stanford.edu/planetccrma/software/soundapps.html#SECTION000621700000000000000,here.}
@newsEnd