1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. For details, see the Contributors'
7 Guide, node Updating translation committishes..
10 @include included/acknowledge.itexi
11 @include included/authors.itexi
12 @include included/helpus.itexi
17 @divClass{link-headings}
19 @divClass{column-center-top}
20 @subheading Interacting with the community
25 @ref{Contact}: get help, discuss, and keep in touch!
28 @ref{Tiny examples}: these are @emph{highly} recommended when
32 @ref{Bug reports}: something went wrong.
37 @divClass{column-left-bottom}
38 @subheading Making LilyPond better
43 @ref{Help us}: your assistance is requested.
46 @ref{Sponsoring}: financial contributions.
49 @ref{Development}: for contributors and testers.
52 @ref{Google Summer of Code}: ideas for Google Summer of Code (GSoC).
55 @ref{Authors}: the people who made LilyPond what it is today.
58 @ref{Acknowledgements}: projects and institutions that support LilyPond
63 @divClass{column-right-bottom}
64 @subheading Miscellaneous
69 @ref{Publications}: what we wrote, and have had written about us.
72 @ref{Old news}: an archive.
75 @ref{Attic}: announcements and changelogs from past versions.
90 * Google Summer of Code::
101 @unnumberedsec Contact
104 @divClass{column-left-bottom}
105 @subheading User Discussions and Help
107 @subsubheading User mailing list: @code{lilypond-user@@gnu.org}
109 This mailing list is the main place for users to discuss and help
113 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
114 lilypond-user subscribe and info}
116 @uref{http://lists.gnu.org/archive/html/lilypond-user/,
118 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
120 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
123 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
124 send to lilypond-user with gmane}
127 @warning{When asking questions, please use @ref{Tiny examples}!}
129 @subsubheading LilyPond Snippet Repository
131 The LilyPond Snippet Repository is a large collection of
132 user-submitted examples, which can freely be copied and used
133 in your own works. See what other people have written,
137 @uref{http://lsr.di.unimi.it}
140 Particularly instructive examples from LSR are included in our
141 official documentation, in @ref{Snippets}.
146 Some level of support is provided on our IRC channel,
149 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
152 This channel has no public archive, so any question that may
153 be useful for others would better be posted to one of the mailing lists.
156 <form action="http://webchat.freenode.net"
160 <input name="nick" type="text" size="15" value="">
162 <input name="channels" type="hidden" value="lilypond">
163 <input type="submit" value="Join #lilypond IRC Chat">
166 <script language="JavaScript" type="text/javascript">
167 var username = "web";
168 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
169 : window.navigator.language;
170 username += '-' + lang.substr(0, 2);
171 username += '-' + navigator.appName.substr(0, 2);
172 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
173 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
174 document.forms["f_lily_irc"].nick.value = username;
178 @subsubheading Other languages
181 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
182 Spanish mailing list}
184 @uref{http://www.lilypondforum.de/,
187 @uref{http://groups.google.com/group/lilypond-brasil,
190 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
193 @uref{http://www.lilypondforum.nl/,
200 @divClass{column-right-top}
201 @subheading Stay Informed
203 @subsubheading LilyPond Report
205 The easiest way to keep touch is by reading our community
206 newsletter, the LilyPond Report:
209 @uref{http://news.lilynet.net}
212 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
214 This mailing list is a low-volume, read-only list which receives
215 notifications of new releases.
218 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
219 info-lilypond subscribe and info}
221 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
223 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
225 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
228 @c don't include gmane posting here. -gp
235 @divClass{column-right-bottom}
236 @subheading Developer Discussion
238 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
240 Most developer discussion takes place on this list. Patches
244 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
245 lilypond-devel subscribe and info}
247 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
249 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
251 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
254 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
255 send to lilypond-devel with gmane}
259 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
261 Bug-specific discussion takes place here.
264 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
265 bug-lilypond subscribe and info}
267 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
269 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
271 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
274 @c don't include gmane posting here. -gp
277 @warning{Before sending a message to the bug list, please read our
278 guidelines for @ref{Bug reports}.}
282 @divClass{column-right-bottom}
283 @subheading Sensitive emails
285 Private matters should be sent to Graham Percival (project
286 manager), who will discuss it with those concerned.
292 @unnumberedsec Tiny examples
294 @divClass{column-center-top}
295 @subheading What are @qq{Tiny examples}?
297 A tiny example is an example from which @strong{nothing} can be removed.
300 @divClass{column-left-bottom}
301 @subheading Why create them?
303 @divClass{keep-bullets}
307 The simpler the example is, the quicker potential helpers can
308 understand it and help you.
311 A tiny example demonstrates that you have put effort towards
312 solving the problem yourself. When people send huge portions of
313 input, it looks like they don't care if we help them or not.
316 Creating a tiny example helps you to understand what is
317 happening. Many false problem reports can be avoided by
318 attempting to create a tiny example; if you cannot replicate a
319 @qq{bug} in a tiny example, then the problem was probably an
320 insufficient understanding of LilyPond, not an actual bug!
328 @divClass{column-right-bottom}
329 @subheading How to create them?
331 @divClass{keep-bullets}
335 Include the @code{\version} number.
338 Make it small! Examples about spacing or page layout might
339 require many bars of music, but most issues can be reproduced
340 using less than a single measure.
343 When trying to create an example, try commenting out @w{(@code{%}
344 or @code{%@{ @dots{} %@}})} sections of your file. If you
345 can comment something while still demonstrating the main idea,
346 then remove the commented-material.
349 Avoid using complicated notes, keys or time signatures, unless
350 the bug is about the behavior of those items.
353 Do not use @code{\override} or @code{\set} commands unless the bug
354 is about those specific commands.
357 Optionally, attach an image showing the desired graphical output.
364 @divClass{column-center-bottom}
365 @subheading How tiny should they be?
367 Is the code below a minimal example?
371 \include "english.ly"
376 \numericTimeSignature
378 <cs' d'' b''>16 <cs' d'' b''>8.
379 %% Here: the tie on the D's looks funny
380 %% Too tall? Left-hand endpoint is not aligned with the B tie?
382 <cs' d'' b''>8 [ <b d'' a''> ]
387 Well, it is not very big, but a truly minimal example is here:
392 % middle tie looks funny here:
393 <c' d'' b''>8. ~ <c' d'' b''>8
397 Very few tiny examples exceed 10 lines of code -
398 quite often 4 lines are enough to demonstrate the problem!
404 @unnumberedsec Bug reports
407 @divClass{heading-center}
408 If you have input that results in a crash or wrong output,
412 @divClass{column-center-top}
413 @subheading Step 1: Known bugs
415 We may already know about this bug. Check here:
418 @uref{http://code.google.com/p/lilypond/issues/list}
421 @warning{Please @strong{DO NOT} add bug reports directly to the
422 bug tracker. Once an issue has been added to the tracker, feel
423 free to add more information to that report.}
428 @divClass{column-left-bottom}
429 @subheading Step 2: Creating a bug report
431 If you have discovered a bug which is not listed,
432 please help us by creating a bug report.
434 @warning{We only accept reports in the form of
435 @ref{Tiny examples}. We have very limited resources,
436 so any non-minimal example will be rejected. Almost
437 every bug can be demonstrated in four notes or less!}
439 Here is an example of a good bug report:
442 % Accidentals should be printed for only
443 % the first note in a tie, but this version
444 % prints flats on both notes.
455 @divClass{column-right-bottom}
456 @subheading Step 3: Sending a bug report
458 Once you have verified that the issue is not already known and
459 created a bug report, please send it to us!
461 @divClass{keep-bullets}
465 If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org,
466 bug-lilypond@@gnu.org} mailing list, send an email like normal.
469 If you are not subscribed, you can still post a bug report with
471 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
472 gmane lilypond.bugs web interface}.
474 However, there is a strict @qq{no top-posting} check on the gmane
475 interface, which is often incorrectly triggered by lilypond files.
476 To avoid this, please add:
479 > I'm not top posting.
483 (you @emph{must} include the @code{>} ) to the top of your bug
490 @divClass{column-center-bottom}
491 @subheading Step 4: Wait for a response
493 Once your bug report has been sent to the list, our Bug Squad will
494 examine it; they may ask you for more information. You will be notified
495 when the report will be added to the bug tracker. Please allow up to 4
496 days, as we have a limited number of volunteers for this task.
498 Once a bug has been added to the tracker, you can comment it to add
499 more information about it.
500 You may also mark the bug so that you automatically receive emails when
501 any activity on the bug occurs. This requires you have a google account
505 @divClass{column-center-bottom}
506 @subheading Optional help: show the desired behavior
508 Once an issue has been added to the tracker, it can be very
509 helpful if we can see the desired output. Feel free to add input
510 code and/or images (possibly created with other tools) which
511 demonstrate what you think it should look like!
518 @unnumberedsec Help us
520 @divClass{column-center-top}
525 @divClass{column-left-top}
526 @divClass{keep-bullets}
532 @divClass{column-right-top}
539 @unnumberedsec Sponsoring
541 @divClass{keep-bullets}
542 @divClass{column-left-top}
548 @item some users have paid for new features
549 @item some developers have added new features for hire
552 The LilyPond project does not organize such efforts; we neither
553 endorse nor discourage such agreements. Any contracts between
554 private individuals is the business of those individuals, not
559 @divClass{column-right-top}
560 @subheading Guidelines
562 Any user wanting to offer money in exchange for work should bear
563 in mind the following points:
567 LilyPond developers may advertise their services on the lilypond
568 email lists from time to time.
571 Any agreements between private individuals should include the
572 normal precautions when conducting business: who pays, how much do
573 they pay, with what method of payment, and upon what set of
574 conditions. We suggest that any ambiguity or uncertainty in these
575 questions should be resolved before any work begins.
581 @divClass{column-center-bottom}
582 @subheading Interested developers
584 Here is a list of people who have expressed an interest in
585 bounties. Note that the amount of work done by individuals varies
586 quite a bit throughout the years. We do not guarantee that this
587 list is up-to-date, nor do we guarantee that the people listed
588 here have any ability. The only criteria is "XYZ asked to be
589 listed on this page".
591 Looking at the git history is a good way to determine who the most
592 active and experienced developers are. Statistics up to version
595 @multitable @columnfractions .3 .3 .3
596 @item @uref{http://lilypond.org/~graham/gitstats-all/, overall history}
597 @tab @uref{http://lilypond.org/~graham/gitstats-1year/, past year}
598 @tab @uref{http://lilypond.org/~graham/gitstats-3months/, past three months}
601 Interested developers:
603 @item @email{dak@@gnu.org, David Kastrup}
604 Donations are required to let me continue my current fulltime work on
605 LilyPond. I focus on user and programmer interface design, coherence,
606 implementation, simplification, documentation, and debugging.
609 @c @item @email{name@@adress.domain, Name}
610 @c area of interest (256 chars max)
619 @unnumberedsec Development
621 @divClass{heading-center}
623 @heading Development for LilyPond @version
626 @heading Development for LilyPond @versionDevel
630 @c we normally don't allow named references, but in this case
631 @c it's good to emphasize the "stable" part. -gp
632 @warning{These are @emph{unstable development} versions. If you
633 have the slightest doubt about how to use or install LilyPond, we
634 urge you to use the @ref{Download, stable Download}, and read the
635 @ref{Manuals, stable Manuals}.}
639 @divClass{column-center-top}
640 @subheading Release numbers
642 There are two sets of releases for LilyPond: stable releases, and
643 unstable development releases. Stable versions have an
644 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
645 Development versions have an odd-numbered @q{minor} version number
646 (e.g., 2.7, 2.9, 2.11).
651 @divClass{column-left-top}
654 Instructions for git and compiling are in the Contributor's Guide.
657 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
660 Documentation writers and testers will generally want to download
665 @downloadDevelLinuxNormal
667 @downloadDevelLinuxBig
669 @downloadDevelLinuxPPC
671 @downloadDevelFreeBSDNormal
673 @downloadDevelFreeBSDBig
675 @downloadDevelDarwinNormal
677 @downloadDevelDarwinPPC
679 @downloadDevelWindows
688 @divClass{column-right-top}
689 @subheading Contributor's Guide
691 LilyPond development is a fairly complicated matter. In order to
692 help new contributors, and to keep the whole system (mostly)
693 stable, we have written a manual for development tasks.
695 @docLinksBare{Contributor's Guide, contributor,
696 @rcontribnamed{Top,Contributor's Guide},
697 @manualDevelContributorSplit,
698 @manualDevelContributorBig, 500 kB,
699 @manualDevelContributorPdf, 2.8 MB}
704 @divClass{column-center-top}
705 @subheading Regression tests
707 @divClass{keep-bullets}
713 @uref{../../input/regression/collated-files.html, Regression tests}:
714 This release's regtests.
715 (@uref{../../input/regression/collated-files.pdf, pdf version})
718 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
719 This release's musicXML tests.
720 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
723 @uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}:
724 This release's abc2ly tests.
725 (@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version})
728 @uref{../../input/regression/lilypond-book/collated-files.html, lilypond-book tests}:
729 This release's lilypond-book tests.
730 (@uref{../../input/regression/lilypond-book/collated-files.pdf, pdf version})
736 @subsubheading Development version
739 @item @regtestDevel (@regtestDevelPdf{})
741 @item @regtestDevelXml (@regtestDevelXmlPdf{})
743 @item @regtestDevelAbc (@regtestDevelAbcPdf{})
745 @item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{})
748 @subsubheading Stable version
751 @item @regtestStable (@regtestStablePdf{})
753 @item @regtestStableXml (@regtestStableXmlPdf{})
755 @item @regtestStableAbc (@regtestStableAbcPdf{})
757 @item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{})
762 @subsubheading All versions
765 @item @uref{http://lilypond.org/test, Comparisons between regression tests}
767 @item @uref{http://lilypond.org/download/binaries/test-output/,
768 Archive of all regression tests}
777 @divClass{column-center-bottom}
781 @warning{These manuals are for LilyPond @version{}; the latest
782 manuals can be found at @url{http://lilypond.org}}
785 @divClass{normal-table}
786 @multitable @columnfractions .3 .3 .3
787 @headitem Introduction
790 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
792 @docLinkBig{Learning,learning,@manualDevelLearningBig}
794 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
797 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
799 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
801 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
804 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
806 @docLinkBig{Essay,essay,@manualDevelEssayBig}
808 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
811 @multitable @columnfractions .3 .3 .3
815 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
817 @docLinkBig{Notation,notation,@manualDevelNotationBig}
819 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
822 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
824 @docLinkBig{Usage,usage,@manualDevelUsageBig}
826 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
829 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
831 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
833 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
836 @multitable @columnfractions .3 .3 .3
840 @docLinkSplit{Web,web,@manualDevelWebSplit}
842 @docLinkBig{Web,web,@manualDevelWebBig}
844 @docLinkPdf{Web,web,@manualDevelWebPdf}
847 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
849 @docLinkBig{Changes,changes,@manualDevelChangesBig}
851 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
854 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
856 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
858 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
861 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
863 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
865 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
869 @multitable @columnfractions .3
870 @headitem Downloadable
884 @node Google Summer of Code
885 @unnumberedsec Google Summer of Code
887 @divClass{column-center-top}
888 @subheading What is Google Summer of Code?
890 A global program run by Google that offers students stipends for working
891 on open source software projects during summer vacations.
893 It is an excellent opportunity to find new contributors, and encourage
894 students already participating in LilyPond development, to become more
895 involved. One of our contributors was accepted in the 2012 program as
896 part of the @uref{http://www.gnu.org/, GNU project}; and we are always
897 looking for others to participate in future programs.
901 @divClass{column-center-bottom}
902 @subheading Our Ideas List
904 Below is a list of projects that were suggested for the GSoC 2012
905 students and is retained here as an inspiration for anyone
906 who is interested in developing LilyPond for future GSoC projects.
908 There are many more things that can be done to improve LilyPond and
909 members of the LilyPond development team are always willing to help
910 those who would like to tackle projects such as those listed below.
912 A full list of all the current open issues can be found
913 @uref{http://code.google.com/p/lilypond/issues/list, here}.
915 @subheading Grace notes
917 Fix problems with synchronization of grace notes. Grace notes can
918 intefere with LilyPond's timing and cause odd effects, especially when
919 multiple staffs are used where some have grace notes and others don't.
921 @strong{Difficulty:} medium
922 @strong{Requirements:} C++, MIDI
923 @strong{Recommended:} familiarity with LilyPond internals
924 @strong{Mentor(s):} Mike Solomon, Carl Sorensen
928 Improving MusicXML import and export functions:
930 @divClass{keep-bullets}
934 Handle basic musical content export like the MIDI export (i.e. using
935 dedicated exporter classes, derived from the translator class).
938 Build the XML tree of the basic musical content, add a connection from
939 music event to XML tag.
942 Let all LilyPond engravers do their job.
945 Link each output object (i.e. each stencil or group of stencils) to the
946 music cause (and thus to the XML tag in the XML tree).
949 Add an XML output backend, which can then add layout information for
950 each output object to the XML tags.
955 @strong{Difficulty:} medium
956 @strong{Requirements:} MusicXML, Python, basic LilyPond knowledge
957 @strong{Mentor(s):} Reinhold Kainhofer, Mike Solomon
959 Familiarity with other scorewriters (for cross-testing) would also help.
962 @subheading Improve slurs and ties
964 The default curves of slurs and ties are often unsatisfactory. Ties
965 @q{broken} by clef or staff changes are not handled well. The project
966 could include collecting and sorting examples of bad output, deciding on
967 the intended output and writing code to improve them.
969 @strong{Difficulty:} hard
970 @strong{Requirements:} C++, experience with writing heuristics
971 @strong{Recommended knowledge:} LilyPond knowledge, aesthetic sense
972 @strong{Mentor(s):} Mike Solomon
974 @subheading Adding variants of font glyphs
976 @divClass{keep-bullets}
980 Adding @q{on} and @q{between} staff-line variants.
983 Shorter and narrower variants of some glyphs for example, accidentals.
984 Another, more specific example could be an ancient notation breve
985 notehead coming in two variants one with a small or big @q{hole} within
991 @strong{Difficulty:} easy
992 @strong{Requirements:} MetaFont, C++, good eye for details
993 @strong{Recommended knowledge:} basic LilyPond knowledge
994 @strong{Mentor(s):} Werner Lemberg
996 @subheading Improve default beam positioning
998 For regular, cross-staff, broken and kneed beams. Beaming should depend
999 on context and neighbor notes
1000 (see @uref{http://icking-music-archive.org/lists/sottisier/sottieng.pdf,
1001 section 2.2 here}). If possible also reduce beaming-computation time.
1003 @strong{Difficulty:} medium
1004 @strong{Requirements:} C++, experience with writing heuristics
1005 @strong{Recommended knowledge:} aesthetic sense
1006 @strong{Mentor(s):} Mike Solomon, Carl Sorensen
1008 @subheading Help improve compilation behavior
1010 Automatic code analysis tools, like valgrind memory leak detection or
1011 callgrind code profilers, provide valuable information about possible
1012 flaws in our C++ code. Cleaning up warnings would allow us to automate
1013 the rejection of any patch which introduced extra warnings.
1015 @strong{Difficulty:} medium
1016 @strong{Requirements:} C++
1017 @strong{Mentor(s):} Joe Neeman, Reinhold Kainhofer
1023 @unnumberedsec Authors
1025 @divClass{column-left-top}
1026 @subheading Current Development Team
1028 @divClass{keep-bullets}
1033 @divClass{column-right-top}
1034 @subheading Previous Development Team
1036 @divClass{keep-bullets}
1042 @divClass{column-center-top}
1043 @subheading Current Contributors
1045 @divClass{keep-bullets}
1046 @subsubheading Programming
1054 @subsubheading Documentation
1058 @subsubheading Bug squad
1062 @subsubheading Support
1066 @subsubheading Translation
1068 @translationsCurrent
1074 @divClass{column-center-bottom}
1075 @subheading Previous Contributors
1077 @divClass{keep-bullets}
1078 @subsubheading Programming
1086 @subsubheading Documentation
1090 @c uncomment when we have any previous members -gp
1091 @c @subsubheading Bug squad
1095 @subsubheading Support
1099 @subsubheading Translation
1101 @translationsPrevious
1106 @node Acknowledgements
1107 @unnumberedsec Acknowledgements
1109 @divClass{column-center-top}
1110 @subheading Acknowledgements
1112 @divClass{keep-bullets}
1113 @acknowledgementsCurrent
1119 @unnumberedsec Publications
1121 @divClass{column-center-top}
1122 @subheading What we wrote about LilyPond
1124 @divClass{keep-bullets}
1126 @include we-wrote.itexi
1131 @divClass{column-center-bottom}
1132 @subheading What people did with LilyPond
1134 @divClass{keep-bullets}
1136 @include others-did.itexi
1141 @contactUsAbout{academic papers}
1145 @unnumberedsec Old news
1147 @divClass{heading-center}
1148 @warning{Many old announcements and changelogs can be found in
1152 @include web/news-front.itexi
1154 @include web/news.itexi
1158 @unnumberedsec Attic
1160 @divClass{column-center-top}
1161 @subheading Announcements
1163 Announcements and news by version:
1164 @uref{http://lilypond.org/doc/v2.16/Documentation/web/index#Lilypond-2_002e16_002e0-released_0021-August-24_002c-2012-1,v2.16},
1165 @uref{http://lilypond.org/doc/v2.14/Documentation/web/index#LilyPond-2_002e14_002e0-released_0021-June-6_002c-2011,v2.14},
1166 @miscLink{announce-v2.12,v2.12},
1167 @miscLink{announce-v2.10,v2.10},
1168 @miscLink{announce-v2.8,v2.8},
1169 @miscLink{announce-v2.6,v2.6},
1170 @miscLink{announce-v2.4,v2.4},
1171 @miscLink{announce-v2.2,v2.2},
1172 @miscLink{announce-v2.0,v2.0},
1173 @miscLink{ANNOUNCE-1.2,v1.2},
1174 @miscLink{ANNOUNCE-1.0,v1.0},
1175 @miscLink{ANNOUNCE-0.1,v0.1}
1177 Descriptive list of changes by version:
1178 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/index.html,v2.16},
1179 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/index.html,v2.14},
1180 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS,v2.12},
1181 @uref{http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS,v2.10},
1182 @uref{http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS,v2.8},
1183 @uref{http://lilypond.org/doc/v2.6/Documentation/topdocs/NEWS,v2.6},
1184 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS,v2.4},
1185 @uref{http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS,v2.2},
1186 @uref{http://lilypond.org/doc/v2.0/Documentation/topdocs/out-www/NEWS,v2.0},
1187 @uref{http://lilypond.org/doc/v1.8/Documentation/topdocs/out-www/NEWS,v1.8},
1188 @uref{http://lilypond.org/doc/v1.6/Documentation/out-www/NEWS,v1.6},
1189 @miscLink{NEWS-1.4,v1.4},
1190 @miscLink{NEWS-1.2,v1.2}
1194 @divClass{column-center-bottom}
1197 Thanks to developers, contributors, bug hunters and suggestions for
1198 @miscLink{THANKS-2.16,v2.16},
1199 @miscLink{THANKS-2.14,v2.14},
1200 @miscLink{THANKS-2.12,v2.12},
1201 @miscLink{THANKS-2.10,v2.10},
1202 @miscLink{THANKS-2.8,v2.8},
1203 @miscLink{THANKS-2.6,v2.6},
1204 @miscLink{THANKS-2.4,v2.4},
1205 @miscLink{THANKS-2.2,v2.2},
1206 @miscLink{THANKS-2.0,v2.0},
1207 @miscLink{THANKS-1.8,v1.8}
1211 @divClass{column-center-bottom}
1212 @subheading Changelogs
1214 Developers' changelogs by version:
1215 @miscLink{ChangeLog-2.10,v2.10},
1216 @miscLink{ChangeLog-2.3,v2.3},
1217 @miscLink{ChangeLog-2.1,v2.1},
1218 @miscLink{ChangeLog-1.5,v1.5 (1)},
1219 @miscLink{CHANGES-1.5,v1.5 (2)},
1220 @miscLink{CHANGES-1.4,v1.4},
1221 @miscLink{CHANGES-1.3,v1.3},
1222 @miscLink{CHANGES-1.2,v1.2},
1223 @miscLink{CHANGES-1.1,v1.1},
1224 @miscLink{CHANGES-1.0,v1.0},
1225 @miscLink{CHANGES-0.1,v0.1},
1226 @miscLink{CHANGES-0.0,v0.0}