1 @c -*- coding: utf-8; mode: texinfo; documentlanguage: zh -*-
2 @c This file is part of web.texi
4 Translation of GIT committish: 5239637b8f00a0307b860dac05189f297c7c198a
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. See TRANSLATION for details.
10 @c Translators: Ben Luo, Anthony Fok
12 @include included/authors.itexi
13 @include included/helpus.itexi
17 @translationof Community
19 @divClass{link-headings}
21 @divClass{column-center-top}
27 @ref{Contact}: get help, discuss, and keep in touch!
30 @ref{Tiny examples}: these are @emph{highly} recommended when
34 @ref{Bug reports}: something went wrong.
39 @divClass{column-left-bottom}
40 @subheading 使 LilyPond 更好
45 @ref{Help us}: your assistance is requested.
48 @ref{Sponsoring}: financial contributions.
51 @ref{Development}: for contributors and testers.
54 @ref{GSoC 2012}: our ideas for 2012 edition of Google Summer of Code.
57 @ref{Authors}: the people who made LilyPond what it is today.
62 @divClass{column-right-bottom}
68 @ref{Publications}: what we wrote, and have had written about us.
71 @ref{Old news}: an archive.
74 @ref{Attic}: announcements and changelogs from past versions.
100 @translationof Contact
103 @divClass{column-left-bottom}
106 @subsubheading 用户邮件列表: @code{lilypond-user@@gnu.org}
108 This mailing list is the main place for users to discuss and help
112 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
113 lilypond-user subscribe and info}
115 @uref{http://lists.gnu.org/archive/html/lilypond-user/,
117 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
119 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
122 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
123 send to lilypond-user with gmane}
126 @warning{When asking questions, please use @ref{Tiny examples}!}
128 @subsubheading LilyPond 片断仓库
130 The LilyPond Snippet Repository (LilyPond 片断仓库) is a large collection of
131 user-submitted examples, which can freely be copied and used
132 in your own works. See what other people have written,
136 @uref{http://lsr.dsi.unimi.it}
139 Particularly instructive examples from LSR are included in our
140 official documentation, in @ref{Snippets}.
145 Some level of support is provided on our IRC channel,
148 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
151 This channel has no public archive, so any question that may
152 be useful for others would better be posted to one of the mailing lists.
155 <form action="http://webchat.freenode.net"
159 <input name="nick" type="text" size="15" value="">
161 <input name="channels" type="hidden" value="lilypond">
162 <input type="submit" value="Join #lilypond IRC Chat">
165 <script language="JavaScript" type="text/javascript">
166 var username = "web";
167 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
168 : window.navigator.language;
169 username += '-' + lang.substr(0, 2);
170 username += '-' + navigator.appName.substr(0, 2);
171 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
172 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
173 document.forms["f_lily_irc"].nick.value = username;
180 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
181 Spanish mailing list}
183 @uref{http://www.lilypondforum.de/,
186 @uref{http://groups.google.com/group/lilypond-brasil,
189 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
192 @uref{http://www.lilypondforum.nl/,
199 @divClass{column-right-top}
202 @subsubheading LilyPond 报告
204 The easiest way to keep touch is by reading our community
205 newsletter, the LilyPond Report:
208 @uref{http://news.lilynet.net}
211 @subsubheading 发行版邮件列表: @code{info-lilypond@@gnu.org}
212 This mailing list is a low-volume, read-only list which receives
213 notifications of new releases.
216 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
217 info-lilypond subscribe and info}
219 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
221 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
223 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
226 @c don't include gmane posting here. -gp
233 @divClass{column-right-bottom}
236 @subsubheading 开发者邮件列表: @code{lilypond-devel@@gnu.org}
238 Most developer discussion takes place on this list. Patches
242 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
243 lilypond-devel subscribe and info}
245 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
247 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
249 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
252 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
253 send to lilypond-devel with gmane}
257 @subsubheading 错误邮件列表: @code{bug-lilypond@@gnu.org}
259 Bug-specific discussion takes place here.
262 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
263 bug-lilypond subscribe and info}
265 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
267 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
269 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
272 @c don't include gmane posting here. -gp
275 @warning{Before sending a message to the bug list, please read our
276 guidelines for @ref{Bug reports}.}
280 @divClass{column-right-bottom}
281 @subheading Sensitive emails
283 Private matters should be sent to Graham Percival (project
284 manager), who will discuss it with those concerned.
291 @translationof Tiny examples
293 @divClass{column-center-top}
294 @subheading 什么是 @qq{小例子}?
296 一个小例子 (tiny example) is an example from which @strong{nothing} can be removed.
299 @divClass{column-left-bottom}
300 @subheading 为什么要创建小例子?
302 @divClass{keep-bullets}
306 The simpler the example is, the quicker potential helpers can
307 understand it and help you.
310 A tiny example demonstrates that you have put effort towards
311 solving the problem yourself. When people send huge portions of
312 input, it looks like they don't care if we help them or not.
315 Creating a tiny example helps you to understand what is
316 happening. Many false problem reports can be avoided by
317 attempting to create a tiny example; if you cannot replicate a
318 @qq{bug} in a tiny example, then the problem was probably an
319 insufficient understanding of LilyPond, not an actual bug!
327 @divClass{column-right-bottom}
330 @divClass{keep-bullets}
334 Include the @code{\version} number.
337 Make it small! Examples about spacing or page layout might
338 require many bars of music, but most issues can be reproduced
339 using less than a single measure.
342 When trying to create an example, try commenting out @w{(@code{%}
343 or @code{%@{ @dots{} %@}})} sections of your file. If you
344 can comment something while still demonstrating the main idea,
345 then remove the commented-material.
348 Avoid using complicated notes, keys or time signatures, unless
349 the bug is about the behavior of those items.
352 Do not use @code{\override} or @code{\set} commands unless the bug
353 is about those specific commands.
356 Optionally, attach an image showing the desired graphical output.
363 @divClass{column-center-bottom}
364 @subheading How tiny should they be?
366 Is the code below a minimal example?
370 \include "english.ly"
375 \numericTimeSignature
377 <cs' d'' b''>16 <cs' d'' b''>8.
378 %% Here: the tie on the D's looks funny
379 %% Too tall? Left-hand endpoint is not aligned with the B tie?
381 <cs' d'' b''>8 [ <b d'' a''> ]
386 Well, it is not very big, but a truly minimal example is here:
391 % middle tie looks funny here:
392 <c' d'' b''>8. ~ <c' d'' b''>8
396 Very few tiny examples exceed 10 lines of code -
397 quite often 4 lines are enough to demonstrate the problem!
404 @translationof 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 第 1 步:检查是否已知错误
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 第 2 步:创建错误报告
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 第 3 步:发送错误报告
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 第 4 步:等待回应
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 days,
496 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
505 @divClass{column-center-bottom}
506 @subheading 可选的帮助:展示所期望的行为
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 @translationof Help us
520 @divClass{column-center-top}
525 @divClass{column-left-top}
526 @divClass{keep-bullets}
532 @divClass{column-right-top}
540 @translationof Sponsoring
542 @divClass{keep-bullets}
543 @divClass{column-left-top}
549 @item some users have paid for new features
550 @item some developers have added new features for hire
553 The LilyPond project does not organize such efforts; we neither
554 endorse nor discourage such agreements. Any contracts between
555 private individuals is the business of those individuals, not
560 @divClass{column-right-top}
561 @subheading Guidelines
563 Any user wanting to offer money in exchange for work should bear
564 in mind the following points:
568 LilyPond developers may advertise their services on the lilypond
569 email lists from time to time.
572 Any agreements between private individuals should include the
573 normal precautions when conducting business: who pays, how much do
574 they pay, with what method of payment, and upon what set of
575 conditions. We suggest that any ambiguity or uncertainty in these
576 questions should be resolved before any work begins.
582 @divClass{column-center-bottom}
583 @subheading Interested developers
585 Here is a list of people who have expressed an interest in
586 bounties. Note that the amount of work done by individuals varies
587 quite a bit throughout the years. We do not guarantee that this
588 list is up-to-date, nor do we guarantee that the people listed
589 here have any ability. The only criteria is "XYZ asked to be
590 listed on this page".
592 Looking at the git history is a good way to determine who the most
593 active and experienced developers are. Statistics up to version
596 @multitable @columnfractions .3 .3 .3
597 @item @uref{http://lilypond.org/~graham/gitstats-all/, overall history}
598 @tab @uref{http://lilypond.org/~graham/gitstats-1year/, past year}
599 @tab @uref{http://lilypond.org/~graham/gitstats-3months/, past three months}
602 Interested developers:
604 @item @email{dak@@gnu.org, David Kastrup}
605 Donations are required to let me continue my current fulltime work on
606 LilyPond. I focus on user and programmer interface design, coherence,
607 implementation, simplification, documentation, and debugging.
610 @c @item @email{name@@adress.domain, Name}
611 @c area of interest (256 chars max)
621 @translationof Development
623 @divClass{heading-center}
625 @heading Development for LilyPond @version
628 @heading Development for LilyPond @versionDevel
632 @c we normally don't allow named references, but in this case
633 @c it's good to emphasize the "stable" part. -gp
634 @warning{These are @emph{unstable development} versions. If you
635 have the slightest doubt about how to use or install LilyPond, we
636 urge you to use the @ref{Download, stable Download}, and read the
637 @ref{Manuals, stable Manuals}.}
641 @divClass{column-center-top}
642 @subheading Release numbers 发行号
644 There are two sets of releases for LilyPond: stable releases, and
645 unstable development releases. Stable versions have an
646 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
647 Development versions have an odd-numbered @q{minor} version number
648 (e.g., 2.7, 2.9, 2.11).
653 @divClass{column-left-top}
656 Instructions for git and compiling are in the Contributor's Guide.
659 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
662 Documentation writers and testers will generally want to download
667 @downloadDevelLinuxNormal
669 @downloadDevelLinuxBig
671 @downloadDevelLinuxPPC
673 @downloadDevelFreeBSDNormal
675 @downloadDevelFreeBSDBig
677 @downloadDevelDarwinNormal
679 @downloadDevelDarwinPPC
681 @downloadDevelWindows
690 @divClass{column-right-top}
693 LilyPond development is a fairly complicated matter. In order to
694 help new contributors, and to keep the whole system (mostly)
695 stable, we have written a manual for development tasks.
697 @docLinksBare{Contributor's Guide, contributor,
698 @rcontribnamed{Top,Contributor's Guide},
699 @manualDevelContributorSplit,
700 @manualDevelContributorBig, 500 kB,
701 @manualDevelContributorPdf, 2.8 MB}
706 @divClass{column-center-top}
709 @divClass{keep-bullets}
715 @uref{../../input/regression/collated-files.html, Regression tests}:
716 This release's regtests.
717 (@uref{../../input/regression/collated-files.pdf, pdf version})
720 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
721 This release's musicXML tests.
722 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
725 @uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}:
726 This release's abc2ly tests.
727 (@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version})
730 @uref{../../input/regression/lilypond-book/collated-files.html, lilypond-book tests}:
731 This release's lilypond-book tests.
732 (@uref{../../input/regression/lilypond-book/collated-files.pdf, pdf version})
741 @item @regtestDevel (@regtestDevelPdf{})
743 @item @regtestDevelXml (@regtestDevelXmlPdf{})
745 @item @regtestDevelAbc (@regtestDevelAbcPdf{})
747 @item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{})
753 @item @regtestStable (@regtestStablePdf{})
755 @item @regtestStableXml (@regtestStableXmlPdf{})
757 @item @regtestStableAbc (@regtestStableAbcPdf{})
759 @item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{})
767 @item @uref{http://lilypond.org/test, Comparisons between regression tests}
769 @item @uref{http://lilypond.org/download/binaries/test-output/,
770 Archive of all regression tests}
779 @divClass{column-center-bottom}
783 @warning{These manuals are for LilyPond @version{}; the latest
784 manuals can be found at @url{http://lilypond.org}}
787 @divClass{normal-table}
788 @multitable @columnfractions .3 .3 .3
789 @headitem Introduction
791 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
793 @docLinkBig{Learning,learning,@manualDevelLearningBig}
795 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
798 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
800 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
802 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
805 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
807 @docLinkBig{Essay,essay,@manualDevelEssayBig}
809 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
814 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
816 @docLinkBig{Notation,notation,@manualDevelNotationBig}
818 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
821 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
823 @docLinkBig{Usage,usage,@manualDevelUsageBig}
825 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
828 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
830 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
832 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
837 @docLinkSplit{Web,web,@manualDevelWebSplit-zh}
839 @docLinkBig{Web,web,@manualDevelWebBig-zh}
841 @docLinkPdf{Web,web,@manualDevelWebPdf-zh}
844 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
846 @docLinkBig{Changes,changes,@manualDevelChangesBig}
848 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
851 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
853 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
855 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
858 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
860 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
862 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
865 @headitem Downloadable
880 @unnumberedsec GSoC 2012
881 @translationof GSoC 2012
883 @divClass{column-center-top}
884 @subheading What is Google Summer of Code?
886 It is a global program run by Google that offers students stipends
887 for working on open source software projects during summer vacations.
889 The LilyPond Team decided that this is an excellent opportunity to find
890 new contributors and encourage students already participating in LilyPond
891 development to become more involved. One of our contributors was accepted
892 for 2012 edition of the program as part of the
893 @uref{http://www.gnu.org/, GNU project};
894 we hope to participate in future editions as well.
898 @divClass{column-center-bottom}
899 @subheading Our 2012 Ideas List
901 Below is a list of projects that we suggested for GSoC 2012 students.
902 Although the application period is over, we decided to keep this webpage
903 online as an inspiration for anyone who is interested in developing LilyPond.
904 Some members of the development team are willing to help people who would like
905 to tackle these projects.
907 Of course, there are many more things to improve in LilyPond, including
908 very small ones. A full list of all known issues can be found
909 @uref{http://code.google.com/p/lilypond/issues/list, here}.
911 @subheading Grace notes
913 Fix problems with synchronization of grace notes,
914 together with all underlying architecture (see
915 @uref{http://code.google.com/p/lilypond/issues/detail?id=34,
916 issue 34 in our tracker}). Grace notes are confusing to LilyPond's
917 timing because they're like going back in time. This causes weird
918 effects, especially when one staff has a grace note and the other
923 @strong{Requirements:} C++, MIDI
925 @strong{Recommended:} familiarity with LilyPond internals
927 @strong{Mentor(s):} Mike Solomon, Carl Sorensen
931 Adding comprehensive MusicXML export and improving import,
932 together with tests checking that it works. Depending on time available,
933 implement some or all of the following:
935 @divClass{keep-bullets}
939 Handle basic musical content export like the MIDI export (i.e. using
940 dedicated exporter classes, derived from the translator class)
943 Build the XML tree of the basic musical content,
944 add a connection from music event to XML tag
947 Let all LilyPond engravers do their job
950 Add ability to link each output object
951 (basically each stencil / group of stencils) to the music cause
952 (and thus to the XML tag in the XML tree)
955 Add a XML output backend, which can then add the layout information
956 for each output object to the XML tags
961 The goal will be considered achieved when a (previously chosen) score
962 could be imported from MusicXML and exported back with no unintentional
967 @strong{Requirements:} MusicXML, Python, basic LilyPond knowledge
969 @strong{Mentor(s):} Reinhold Kainhofer, Mike Solomon
971 Familiarity with other scorewriters (for cross-testing) would be a nice
974 @subheading Improve slurs and ties
976 The default shape of slur and tie curves is often unsatisfactory.
977 Ties on enharmonic notes @code{@{ cis'~ des' @}} are not supported,
978 ties "broken" by clef or staff change aren't supported well.
979 The project includes collecting and sorting examples of bad output,
980 deciding on the intended output and writing the actual code.
984 @strong{Requirements:} C++, experience with writing heuristics
986 @strong{Recommended knowledge:} LilyPond knowledge, aesthetic sense
988 @strong{Mentor(s):} Mike Solomon
990 @subheading Adding special variant of font glyphs
991 Adding on-staff-line, between-staff-line, shorter and narrower variants
992 of some glyphs, for example accidentals, together with a generic
993 infrastructure to support them. An example is ancient notation breve
994 notehead coming in two variants, with smaller and bigger hole.
998 @strong{Requirements:} MetaFont, C++, good eye for details
1000 @strong{Recommended knowledge:} basic LilyPond knowledge
1002 @strong{Mentor(s):} Werner Lemberg
1004 @subheading Improve beaming
1006 Default positioning of regular, cross-staff, broken and kneed beams
1007 should be improved. Beaming should depend on context and neighbor notes
1008 (see @uref{http://icking-music-archive.org/lists/sottisier/sottieng.pdf,
1009 section 2.2 here}). If possible, reduce beaming computation time.
1013 @strong{Requirements:} C++, experience with writing heuristics
1015 @strong{Recommended knowledge:} aesthetic sense
1017 @strong{Mentor(s):} Mike Solomon, Carl Sorensen
1019 @subheading Clean up various compilation warnings
1021 Clean up compiler warnings, static code analysis, and valgrind warnings.
1022 Automatic code analysis tools (warnings in @code{g++} and @code{clang})
1023 and analysis tools like valgrind memory leak detection and callgrind
1024 code profilers provide valuable information about possible flaws in C++
1025 code. Cleaning these warnings would allow us to automatically reject
1026 any patch which introduced extra warnings.
1030 @strong{Requirements:} C++
1032 @strong{Mentor(s):} Joe Neeman, Reinhold Kainhofer
1041 @translationof Authors
1043 @divClass{column-left-top}
1046 @divClass{keep-bullets}
1051 @divClass{column-right-top}
1054 @divClass{keep-bullets}
1060 @divClass{column-center-top}
1063 @divClass{keep-bullets}
1076 @subsubheading 错误组 (Bug squad)
1086 @translationsCurrent
1092 @divClass{column-center-bottom}
1095 @divClass{keep-bullets}
1108 @c uncomment when we have any previous members -gp
1109 @c @subsubheading Bug squad
1119 @translationsPrevious
1128 @translationof Publications
1130 @divClass{column-center-top}
1131 @subheading 我们写的有关 LilyPond 的文章
1133 @divClass{keep-bullets}
1135 @include we-wrote.itexi
1140 @divClass{column-center-bottom}
1141 @subheading 大家怎么用 LilyPond 的
1143 @divClass{keep-bullets}
1145 @include others-did.itexi
1150 @contactUsAbout{学术论文}
1155 @translationof Old news
1157 @divClass{heading-center}
1158 @warning{Many old announcements and changelogs can be found in
1162 @include web/news-front.itexi
1164 @include web/news.itexi
1168 @unnumberedsec Attic
1169 @translationof Attic
1171 @divClass{column-center-top}
1172 @subheading Announcements
1174 Announcements and news by version:
1175 @uref{http://lilypond.org/doc/v2.14/Documentation/web/index#LilyPond-2_002e14_002e0-released_0021-June-6_002c-2011,v2.14},
1176 @miscLink{announce-v2.12,v2.12},
1177 @miscLink{announce-v2.10,v2.10},
1178 @miscLink{announce-v2.8,v2.8},
1179 @miscLink{announce-v2.6,v2.6},
1180 @miscLink{announce-v2.4,v2.4},
1181 @miscLink{announce-v2.2,v2.2},
1182 @miscLink{announce-v2.0,v2.0},
1183 @miscLink{ANNOUNCE-1.2,v1.2},
1184 @miscLink{ANNOUNCE-1.0,v1.0},
1185 @miscLink{ANNOUNCE-0.1,v0.1}
1187 Descriptive list of changes by version:
1188 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/index.html,v2.14},
1189 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS,v2.12},
1190 @uref{http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS,v2.10},
1191 @uref{http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS,v2.8},
1192 @uref{http://lilypond.org/doc/v2.6/Documentation/topdocs/NEWS,v2.6},
1193 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS,v2.4},
1194 @uref{http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS,v2.2},
1195 @uref{http://lilypond.org/doc/v2.0/Documentation/topdocs/out-www/NEWS,v2.0},
1196 @uref{http://lilypond.org/doc/v1.8/Documentation/topdocs/out-www/NEWS,v1.8},
1197 @uref{http://lilypond.org/doc/v1.6/Documentation/out-www/NEWS,v1.6},
1198 @miscLink{NEWS-1.4,v1.4},
1199 @miscLink{NEWS-1.2,v1.2}
1203 @divClass{column-center-bottom}
1204 @subheading Changelogs
1206 Developers' changelogs by version:
1207 @miscLink{ChangeLog-2.10,v2.10},
1208 @miscLink{ChangeLog-2.3,v2.3},
1209 @miscLink{ChangeLog-2.1,v2.1},
1210 @miscLink{ChangeLog-1.5,v1.5 (1)},
1211 @miscLink{CHANGES-1.5,v1.5 (2)},
1212 @miscLink{CHANGES-1.4,v1.4},
1213 @miscLink{CHANGES-1.3,v1.3},
1214 @miscLink{CHANGES-1.2,v1.2},
1215 @miscLink{CHANGES-1.1,v1.1},
1216 @miscLink{CHANGES-1.0,v1.0},
1217 @miscLink{CHANGES-0.1,v0.1},
1218 @miscLink{CHANGES-0.0,v0.0}