* don't duplicate entries from news-front.itexi
@end ignore
+@newsItem
+@subsubheading LilyPond 2.13.41 released! @emph{Dec 4, 2010}
+
+We are happy to announce the release of LilyPond 2.13.41. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+Please note that this is @strong{not} the second beta test. Due
+to a number of untested changes to our build process, we cannot be
+at all confident about the quality of this release.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.40 released! @emph{Nov 21, 2010}
+
+We are happy to announce the release of LilyPond 2.13.40. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+Please note that this is @strong{not} the second beta test. Due
+to a number of untested changes to our build process, we cannot be
+at all confident about the quality of this release.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading Beta test one of 2.14 -- LilyPond 2.13.39 released! @emph{Nov 15, 2010}
+
+LilyPond 2.13.39 is out; this is the first beta test of the
+upcoming 2.14 stable release. Users are invited to experiment
+with this version. New features since 2.12.3 are listed in the
+@qq{Changes} manual on the website section about
+@ref{Development}.
+
+There are still some Critical problems with this release: the
+vertical spacing is suspicious in two cases, and lilypond can
+crash with some odd input. If you decide to test 2.13.39, do not
+be surprised to discover problems; just send us polite
+@ref{Bug reports}.
+
+@newsEnd
+
+
+
+
+@newsItem
+@subsubheading The LilyPond Report #22. @emph{Nov 3, 2010}
+
+The @emph{LilyPond Report} is back, with some surprises and exciting
+news for the whole LilyPond community! To be found in this issue is
+an up-to-date, complete list of all LilyPond mailing lists and forums
+around the world. Also, for the very first time our special guest
+today is LilyPond’s co-founder and core developer
+@strong{Jan Nieuwenhuizen}, who has been busy these past months --
+read on to find out what for!
+
+Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-22, read
+LilyPond Report 22} now; comments and contributions are
+warmly encouraged!
+
+@newsEnd
+
+
+@newsItem
+@subsubheading Alpha test four of 2.14 -- LilyPond 2.13.38 released! @emph{Oct 31, 2010}
+
+LilyPond 2.13.38 is out; this is the fourth alpha test of the
+upcoming 2.14 stable release. Users are invited to experiment
+with this version. New features since 2.12.3 are listed in the
+@qq{Changes} manual on the website section about
+@ref{Development}.
+
+There are still some Critical problems with this release: the
+vertical spacing is suspicious in two cases, and lilypond can
+crash with some odd input. If you decide to test 2.13.38, do not
+be surprised to discover problems; just send us polite
+@ref{Bug reports}.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading Alpha test three of 2.14 -- LilyPond 2.13.37 released! @emph{Oct 25, 2010}
+
+LilyPond 2.13.37 is out; this is the third alpha test of the
+upcoming 2.14 stable release. Users are invited to experiment
+with this version. New features since 2.12.3 are listed in the
+@qq{Changes} manual on the website section about
+@ref{Development}.
+
+There are still some Critical problems with this release: the
+vertical spacing is suspicious in two cases, and lilypond can
+crash with some odd input. If you decide to test 2.13.37, do not
+be surprised to discover problems; just send us polite
+@ref{Bug reports}.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.36 released! @emph{Oct 19, 2010}
+
+We are happy to announce the release of LilyPond 2.13.36. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+Please note that this is @strong{not} the third alpha test. Due
+to a number of untested changes to our build process, we cannot be
+at all confident about the quality of this release.
+
+@newsEnd
+
+@newsItem
+@subsubheading The LilyPond Report #21. @emph{Oct 3, 2010}
+
+The @emph{LilyPond Report} is back, with its two
+@qq{grumpy-and-fluffy} editors! This issue mainly deals with
+microtonal notation in LilyPond, but does also include a how-to
+about running LilyPond from an USB key, not to forget the regular
+release news, the bug report of the Report, and some news from
+the frog pond!
+
+Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-21, read
+LilyPond Report 21} now; comments and contributions are
+warmly encouraged!
+
+@newsEnd
+
+
+@newsItem
+@subsubheading Alpha test two of 2.14 -- LilyPond 2.13.35 released! @emph{Sep 29, 2010}
+
+LilyPond 2.13.35 is out; this is the second alpha test of the
+upcoming 2.14 stable release. Users are invited to experiment
+with this version. New features since 2.12.3 are listed in the
+@qq{Changes} manual on the website section about
+@ref{Development}.
+
+Three known regressions against 2.12.3 still exist:
+@uref{http://code.google.com/p/lilypond/issues/detail?id=1173,
+Issue 1173 MetronomeMarks cannot be aligned on a note if a
+multi-measure rest exists in another voice}, and two spacing
+bugs:
+@uref{http://code.google.com/p/lilypond/issues/detail?id=1240,
+Issue 1240} and
+@uref{http://code.google.com/p/lilypond/issues/detail?id=1252,
+Issue 1252}. If you decide to test 2.13.35, do not be surprised
+to discover problems; just send us polite @ref{Bug reports}.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading Alpha test of 2.14 -- LilyPond 2.13.34 released! @emph{Sep 21, 2010}
+
+LilyPond 2.13.34 is out; this is the first alpha test of the
+upcoming 2.14 stable release. Users are invited to experiment
+with this version. New features since 2.12.3 are listed in the
+@qq{Changes} manual on the website section about
+@ref{Development}.
+
+One known regression against 2.12.3 still exist:
+@uref{http://code.google.com/p/lilypond/issues/detail?id=1173,
+Issue 1173 MetronomeMarks cannot be aligned on a note if a
+multi-measure rest exists in another voice}, but we expect to find
+more. If you decide to test 2.13.34, do not be surprised to
+discover problems; just send us polite @ref{Bug reports}.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.33 released! @emph{Sep 10, 2010}
+
+We are happy to announce the release of LilyPond 2.13.33. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+@newsEnd
+
+
+
+
+@newsItem
+@subsubheading LilyPond 2.13.32 released! @emph{Sep 3, 2010}
+
+We are happy to announce the release of LilyPond 2.13.32. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #20. @emph{Sep 2, 2010}
+
+The @emph{LilyPond Report} is back, with its two
+@qq{grumpy-and-fluffy} editors! This issue contains a review of an
+online notation editor using lilypond, along with the regular
+release news, snippet of the report, news from the frog pond, and
+the bug report of the report!
+
+Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-20, read
+LilyPond Report 20} now; comments and contributions are
+warmly encouraged!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.31 released! @emph{Aug 24, 2010}
+
+We are happy to announce the release of LilyPond 2.13.31. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.30 released! @emph{Aug 13, 2010}
+
+We are happy to announce the release of LilyPond 2.13.30. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #19. @emph{Aug 9, 2010}
+
+The @emph{LilyPond Report} is back, with its two
+@qq{grumpy-and-fluffy} editors! This issue contains some
+conference news, along with the regular release news, snippet of
+the report, news from the frog pond, and the bug report of the
+report!
+Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-19, read
+LilyPond Report 19} now; comments and contributions are
+warmly encouraged!
+@newsEnd
+
+
+
+
+@newsItem
+@subsubheading LilyPond 2.13.29 released! @emph{Aug 4, 2010}
+
+We are happy to announce the release of LilyPond 2.13.29. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+This release radically changes the autobeaming rules, so use extra
+caution and expect breakage.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.28 released! @emph{July 13, 2010}
+
+We are happy to announce the release of LilyPond 2.13.28. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+This release includes some major untested changes to the windows
+lilypad editor. Windows users should not be using this release
+because it is intended for developers only, but you ignore these
+warnings and try it anyway, use extra caution.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.27 released! @emph{July 5, 2010}
+
+We are happy to announce the release of LilyPond 2.13.27. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+
+@newsItem
+@subsubheading Testing our new website! @emph{June 29, 2010}
+
+We're testing our new website! For the next 24 hours, the new
+website will be the default website; after that, we will switch
+back to the old website while we examine feedback and make
+improvements to the new website.
+
+Please send feedback to @code{lilypond-user}; you can find more
+information on our page about @ref{Contact}.
+
+@warning{There are a few known problems with translations. If you
+are a non-English speaker, you may prefer to view the old lilypond
+website at:
+@uref{http://lilypond.org/web/}}
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.26 released! @emph{June 26, 2010}
+
+We are happy to announce the release of LilyPond 2.13.26. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.25 released! @emph{June 20, 2010}
+
+We are happy to announce the release of LilyPond 2.13.25. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.24 released! @emph{June 14, 2010}
+
+We are happy to announce the release of LilyPond 2.13.24. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.23 released! @emph{June 3, 2010}
+
+We are happy to announce the release of LilyPond 2.13.23. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.22 released! @emph{May 27, 2010}
+
+We are happy to announce the release of LilyPond 2.13.22. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.21 released! @emph{May 12, 2010}
+
+We are happy to announce the release of LilyPond 2.13.21. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+This release should be of particular interest to package
+maintainers: we have made a few changes to the configure script
+and the required libraries. Barring any urgent bug reports, this
+is the build system and libraries that will be used for the next
+stable release.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #18. @emph{May 11, 2010}
+
+The @emph{LilyPond Report} is back, with its two
+@qq{grumpy-and-fluffy} editors! This issue will be filled
+with emotion and coolness, paper bags and zigzag-ending
+staves, plus the usual Frogs and Bugs.
+
+Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-18, read
+LilyPond Report 18} now; comments and contributions are
+warmly encouraged!
+@newsEnd
+
+
+
+@newsItem
+@subsubheading LilyPond 2.13.20 released! @emph{May 5, 2010}
+
+We are happy to announce the release of LilyPond 2.13.20. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+Minor syntax change: the undocumented @code{\cresc} and
+@code{\decresc} have changed. In addition, the [options] for the
+LaTeX mode of @code{lilypond-book} now comes after the
+@code{@{lilypond@}}, following normal LaTeX practice. As always,
+see the Changes document for more information.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.19 released! @emph{April 24, 2010}
+
+We are happy to announce the release of LilyPond 2.13.19. This
+release contains the usual number of bugfixes. However, 11
+critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.18 released! @emph{April 16, 2010}
+
+We are happy to announce the release of LilyPond 2.13.18. This
+release contains the usual number of bugfixes, along with improved
+website translations. However, 14 critical issues still remain,
+so this release is intended for developers only.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.17 released! @emph{April 2, 2010}
+
+We are happy to announce the release of LilyPond 2.13.17. This
+release includes bugfixes for 4 critical issues. However, 15
+critical issues still remain, so this release is intended for
+developers only.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.16 released! @emph{March 15, 2010}
+
+We are happy to announce the release of LilyPond 2.13.16. This
+release is intended for developers only, and includes the usual
+round of bugfixes.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.15 released! @emph{March 4, 2010}
+
+We are happy to announce the release of LilyPond 2.13.15. This
+release is intended for developers only, and includes a few
+updates to the binary build process in addition to the usual round
+of bugfixes.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #17. @emph{March 1, 2010}
+
+Yay, the Report is back, with a new team! It has been said that
+two heads are better than one — does it apply to newsletters as
+well? Read on and let us know! In this issue we’ll talk about
+websites and poetry, frogs and bugs, not to mention an extensive
+review of the Frescobaldi editor!
+
+What are you waiting for? Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-17, read
+LilyPond Report 17} now!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.14 released! @emph{February 27, 2010}
+
+We are happy to announce the release of LilyPond 2.13.14. This
+release is intended for developers only, and includes a large
+translation update in addition to the usual round of bugfixes.
+@newsEnd
+
+@newsItem
+@subsubheading LilyPond 2.13.13 released! @emph{February 13, 2010}
+
+We are happy to announce the release of LilyPond 2.13.13. This
+release is intended for developers only, and fixes various
+problems with documentation build system as well as adding an
+output-preview-framework for our SVG backend. In addition, the
+binaries are now approximately 6 megabytes smaller.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.12 released! @emph{February 2, 2010}
+
+We are happy to announce the release of LilyPond 2.13.12. This
+release is intended for developers only, and brings more stability
+and fewer bugs to the build system and Contributor's Guide.
+@newsEnd
@newsItem
@subsubheading LilyPond 2.13.11 released! @emph{January 16, 2010}
@newsItem
@subsubheading lilypond.org日本語訳 (lilypond.org Japanese translation). @emph{2008年4月8日 (April 4, 2008)}
-Lilypond.orgのいくつかのページの日本語訳が出来ました。
+lilypond.orgのいくつかのページの日本語訳が出来ました。
@newsEnd
graphics.
@*
Author Kris Shaffer remarks
-“GNU Lilypond generates beautiful graphics that make commercial
+“GNU LilyPond generates beautiful graphics that make commercial
alternatives seem second-rate.”
This article is now available @uref{http://www.linuxjournal.com/article/8583,on-line}.
@newsEnd
@newsItem
@subsubheading 2.5.23 released - @emph{May 6, 2005}
This release has a couple of small bugfixes, and a new feature. It is
-now possible to start and stop the StaffSymbol, during a piece of
-music, by doing \stopStaff \startStaff. This can be used to produce
-Ossia
-staves. (@ref{Changes},
+now possible to start and stop the @code{StaffSymbol}, during a piece of
+music, by doing @code{\stopStaff \startStaff}. This can be used to
+produce Ossia staves. (@ref{Changes},
@ref{Old downloads})
@newsEnd
@newsItem
@subsubheading February 26, 2005
-The @uref{http://lsr.dsi.unimi.it/,Lilypond Snippet
-Repository (LSR)} is a searchable database of Lilypond code
+The @uref{http://lsr.dsi.unimi.it/,LilyPond Snippet
+Repository (LSR)} is a searchable database of LilyPond code
snippets. You can add snippets too, so join the LSR project, and
-contribute creative ideas for using Lilypond.
+contribute creative ideas for using LilyPond.
@newsEnd
@newsItem
@subsubheading October 29, 2004
-2.3.25 is the final release candidate for Lilypond 2.4.
+2.3.25 is the final release candidate for LilyPond 2.4.
Werner has been overhauling the TeX macros and
lilypond-book. In addition, this release contains an
important fix for raggedbottom page-layout.
@newsItem
@subsubheading July 23, 2004
-Lilypond 2.3.8 fixes a few minor bugs in the new slur code,
+LilyPond 2.3.8 fixes a few minor bugs in the new slur code,
and has rewritten support for ledger lines. Now, in tight
situations, ledger lines will be shortened so they stay
separate. This also required a cleanup of the Ambitus
projects / lilypond.git / blobdiff