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/authors.itexi
16 @divClass{column-center-top}
17 @subheading Interacting with the community
22 @ref{Contact}: get help, discuss, and keep in touch!
25 @ref{Tiny examples}: these are @emph{highly} recommended when
29 @ref{Bug reports}: something went wrong.
34 @divClass{column-left-bottom}
35 @subheading Making LilyPond better
40 @ref{Help us}: your assistance is requested.
43 @ref{Development}: for contributors and testers.
46 @ref{Authors}: the people who made LilyPond what it is today.
51 @divClass{column-right-bottom}
52 @subheading Miscellaneous
57 @ref{Publications}: what we wrote, and have had written about us.
60 @ref{Old news}: an archive.
81 @unnumberedsec Contact
84 @divClass{column-left-bottom}
85 @subheading User Discussions and Help
87 @subsubheading User mailing list: @code{lilypond-user@@gnu.org}
89 This mailing list is the main place for users to discuss and help
93 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
94 lilypond-user subscribe and info}
96 @uref{http://lists.gnu.org/archive/html/lilypond-user/,
98 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
100 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
103 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
104 send to lilypond-user with gmane}
107 @warning{When asking questions, please use @ref{Tiny examples}!}
112 Some level of support is provided on our IRC channel,
115 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
118 This channel has no public archive, so any question that may
119 be useful for others would better be posted to one of the mailing lists.
122 <form action="http://webchat.freenode.net"
126 <input name="nick" type="text" size="15" value="">
128 <input name="channels" type="hidden" value="lilypond">
129 <input type="submit" value="Join #lilypond IRC Chat">
132 <script language="JavaScript" type="text/javascript">
133 var username = "web";
134 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
135 : window.navigator.language;
136 username += '-' + lang.substr(0, 2);
137 username += '-' + navigator.appName.substr(0, 2);
138 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
139 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
140 document.forms["f_lily_irc"].nick.value = username;
144 @subsubheading Other languages
147 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
148 Spanish mailing list}
150 @uref{http://www.lilypondforum.de/,
153 @uref{http://groups.google.com/group/lilypond-brasil,
156 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
159 @uref{http://www.lilypondforum.nl/,
166 @divClass{column-right-top}
167 @subheading Stay Informed
169 @subsubheading LilyPond Report
171 The easiest way to keep touch is by reading our community
172 newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
174 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
176 This mailing list is a low-volume, read-only list which receives
177 notifications of new releases.
180 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
181 info-lilypond subscribe and info}
183 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
185 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
187 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
190 @c don't include gmane posting here. -gp
197 @divClass{column-right-bottom}
198 @subheading Developer Discussion
200 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
202 Most developer discussion takes place on this list. Patches
206 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
207 lilypond-devel subscribe and info}
209 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
211 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
213 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
216 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
217 send to lilypond-devel with gmane}
221 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
223 Bug-specific discussion takes place here.
226 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
227 bug-lilypond subscribe and info}
229 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
231 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
233 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
236 @c don't include gmane posting here. -gp
239 @warning{Before sending a message to the bug list, please read our
240 guidelines for @ref{Bug reports}.}
247 @unnumberedsec Tiny examples
249 @divClass{column-center-top}
250 @subheading What are @qq{Tiny examples}?
252 A tiny example is an example from which nothing can be removed.
255 @divClass{column-left-bottom}
256 @subheading Why create them?
258 @divClass{keep-bullets}
262 The simpler the example is, the quicker potential helpers can
263 understand it and help you.
266 A simple example demonstrates that you have put effort towards
267 solving the problem yourself. When people send huge portions of
268 input, it looks like they don't care how if we help them or not.
271 Creating a tiny example forces you to understand what is
272 happening. Many false problem reports can be avoided by
273 attempting to create a tiny example; if you cannot replicate a
274 @qq{bug} in a tiny example, then the problem was probably an
275 insufficient understanding of LilyPond, not an actual bug!
283 @divClass{column-right-bottom}
284 @subheading How do I create them?
286 @divClass{keep-bullets}
290 Include the \version number.
293 Make it small! Examples about spacing or page layout might
294 require many bars of music, but most issues can be reproduced
295 using only a single measure.
298 When trying to create an example, try commenting out @w{(@code{%}
299 or @code{%@{ @dots{} %@}})} sections of your file. If you can
300 comment something while still demonstrating the main idea, then
301 remove the commented-material!
304 Avoid using complicated notes, keys, or time signatures, unless
305 the bug is about the behavior of those items.
308 Do not use @code{\override} or @code{\set} commands unless the bug
309 is about those particular commands.
320 @unnumberedsec Bug reports
322 @divClass{column-center-top}
323 @subheading Step 1: Known bugs
325 If you have input that results in a crash or an erroneous output,
326 then that is a bug. There is a list of current bugs on our google
330 @uref{http://code.google.com/p/lilypond/issues/list}
333 @warning{Please @strong{DO NOT} add bug reports directly to the
334 bug tracker. Once an issue has been added to the tracker, feel
335 free to add more information to that report.}
340 @divClass{column-left-bottom}
341 @subheading Step 2: Creating a bug report
343 If you have discovered a bug which is not listed, please help us
344 by creating a bug report.
346 @warning{We only accept bug reports in the form of @ref{Tiny
347 examples}. We have very limited resources to deal with bug
348 reports, so any non-minimal example will be rejected. Almost
349 every bug can be demonstrated in four notes or less!}
351 Here is an example of a good bug report:
354 %% the octavation command doesn't
355 %% change the output at all!
358 \paper@{ ragged-right=##t @}
368 @divClass{column-right-bottom}
369 @subheading Step 3: Sending a bug report
371 Once you have verified that the issue is not already known and
372 created a bug report, please send it to us!
374 Unfortunately there is a strict @qq{no top-posting} check on the
375 bug list, which is often incorrectly triggered by lilypond files.
376 To avoid this, please add
379 > I'm not top posting.
383 (you must include the @code{>} ) to the top of your bug report.
385 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
386 Post with the gmane lilypond.bugs interface}, or send an email to
387 @uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
389 Once your bug has been sent to the list, our Bug Meister will
390 examine the report. He may ask you for more information, or may
391 add the report to the tracker and let you know what the issue
394 You may mark the bug so that you automatically receive emails when
395 any activity on the bug occurs. This requires you have a google
401 @unnumberedsec Help us
403 @divClass{column-center-top}
404 @subheading We need you!
406 The LilyPond development team is quite small; we really want to
407 get more people involved. Please consider helping your fellow
408 LilyPond users by contributing to development!
410 Even working on small tasks can have a big impact: taking care
411 of them let experienced developers work on advanced tasks, instead
412 of spending time on those simple tasks.
417 @divClass{column-left-top}
418 @subheading Simple tasks
420 @divClass{keep-bullets}
424 Mailing list support: answer questions from fellow users.
427 Bug reporting: help users create proper @ref{Bug reports}, and aid
428 the Bug Team in handling @rcontrib{Issues}.
431 Documentation: small changes can be proposed by following the
432 guidelines for @rcontrib{Documentation suggestions}.
435 LilyPond Snippet Repository (LSR): create and fix snippets. See
436 @rcontrib{Adding and editing snippets}.
439 Discussions, reviews, and testing: the developers often ask for
440 feedback about new documentation, potential syntax changes, and
441 testing new features. Please contribute to these discussions!
445 @subheading Moderate tasks
447 @warning{These jobs generally require that you have the program
448 and documentation source files, but do not require a full
449 development environment. See @rcontrib{Starting with Git}.}
454 @rcontrib{Documentation work}, and
455 @rcontrib{Building documentation without compiling LilyPond}.
458 Website: the website is built from the normal documentation
459 source. See the info about documentation, and also
460 @rcontrib{Website work}.
463 Translations: see @rcontrib{Translating the documentation}, and
464 @rcontrib{Translating the website}.
469 @subheading Complex tasks
471 @warning{These jobs generally require that you have the source
472 code and can compile LilyPond. See @rcontrib{Starting with Git},
473 and @rcontrib{Compiling LilyPond}.}
475 We suggest that new contributors using Windows use a virtual
476 machine to run @emph{lilybuntu}. See
477 @rcontrib{Using a Virtual Machine to Compile LilyPond}.
481 Bugfixes, new features: the best way to begin is to join the
482 Frogs, and read @rcontrib{Programming work}.
490 @divClass{column-right-top}
495 Website and mailist: @uref{http://frogs.lilynet.net}
497 The Frogs are ordinary LilyPond users who have chosen to get
498 involved in their favorite software's development. Fixing bugs,
499 implementing new features, documenting the source code: there's a
500 lot to be done, but most importantly: this is a chance for
501 everyone to learn more about LilyPond, about Free Software, about
502 programming... and to have fun. If you're curious about any of
503 it, then the word is: @emph{Join the Frogs!}
507 @help{not active yet; either comment out or begin these projects
510 @subsubheading Grand LilyPond Input Syntax Standardization
512 Website: @uref{http://lilypond.org/~graham/gliss}
514 GLISS will stabilize the (non-tweak) input syntax for the upcoming
515 LilyPond 3.0. After updating to 3.0, the input syntax for
516 untweaked music will remain stable for the foreseeable future.
518 We will have an extensive discussion period to determine the final
521 @subsubheading Grand Organizing Project
523 Website and mailist: TODO
525 GOP is our big recruiting drive for new contributors.
531 @divClass{column-center-bottom}
532 @subheading Interested?
539 @unnumberedsec Development
541 @divClass{heading-center}
543 @heading Development for LilyPond @version
546 @heading Development for LilyPond @versionDevel
550 @warning{These are @emph{unstable development} versions. If you
551 have the slightest doubt about how to use or install LilyPond, we
552 urge you to use the stable @ref{Download}, and read the stable
557 @divClass{column-center-top}
558 @subheading Release numbers
560 There are two sets of releases for LilyPond: stable releases, and
561 unstable development releases. Stable versions have an
562 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
563 Development versions have an odd-numbered @q{minor} version number
564 (e.g., 2.7, 2.9, 2.11).
569 @divClass{column-left-top}
572 Instructions for git and compiling are in the Contributor's Guide.
575 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
578 Documentation writers and testers will generally want to download
583 @downloadDevelLinuxNormal
585 @downloadDevelLinuxBig
587 @downloadDevelLinuxPPC
589 @downloadDevelFreeBSDNormal
591 @downloadDevelFreeBSDBig
593 @downloadDevelDarwinNormal
595 @downloadDevelDarwinPPC
597 @downloadDevelWindows
606 @divClass{column-right-top}
607 @subheading Contributor's Guide
609 LilyPond development is a fairly complicated matter. In order to
610 help new contributors, and to keep the whole system (mostly)
611 stable, we have written a manual for development tasks.
613 @docLinksBare{Contributor's Guide, contributor,
614 @rcontribnamed{Top,Contributor's Guide},
615 @manualDevelContributorSplit,
616 @manualDevelContributorBig, 500 kB,
617 @manualDevelContributorPdf, 2.8 MB}
622 @divClass{column-center-top}
623 @subheading Regression tests
625 @divClass{keep-bullets}
631 @uref{../../input/regression/collated-files.html, Regression tests}:
632 This release's regtests.
633 (@uref{../../input/regression/collated-files.pdf, pdf version})
636 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
637 This release's musicXML tests.
638 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
642 @item @regtestDevel (@regtestDevelPdf{})
644 @item @regtestDevelXml (@regtestDevelXmlPdf{})
646 @item @regtestStable (@regtestStablePdf{})
648 @item @regtestStableXml (@regtestStableXmlPdf{})
652 @item @uref{http://lilypond.org/test, Archive of regression tests}:
653 Comparisons between versions.
661 @divClass{column-center-bottom}
665 @warning{These manuals are for LilyPond @version{}; the latest
666 manuals can be found at @url{http://lilypond.org}}
669 @divClass{normal-table}
670 @multitable @columnfractions .3 .3 .3
671 @headitem Introduction
673 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
675 @docLinkBig{Learning,learning,@manualDevelLearningBig}
677 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
680 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
682 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
684 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
687 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
689 @docLinkBig{Essay,essay,@manualDevelEssayBig}
691 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
696 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
698 @docLinkBig{Notation,notation,@manualDevelNotationBig}
700 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
703 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
705 @docLinkBig{Usage,usage,@manualDevelUsageBig}
707 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
710 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
712 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
714 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
719 @docLinkSplit{Web,web,@manualDevelWebSplit}
721 @docLinkBig{Web,web,@manualDevelWebBig}
723 @docLinkPdf{Web,web,@manualDevelWebPdf}
726 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
728 @docLinkBig{Changes,changes,@manualDevelChangesBig}
730 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
733 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
735 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
737 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
740 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
742 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
744 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
747 @headitem Downloadable
762 @unnumberedsec Authors
764 @help{Under construction; this is not an accurate list!}
767 @divClass{column-left-top}
768 @subheading Current Development Team
770 @divClass{keep-bullets}
775 @divClass{column-right-top}
776 @subheading Previous Development Team
778 @divClass{keep-bullets}
784 @divClass{column-center-top}
785 @subheading Current Contributors
787 @divClass{keep-bullets}
788 @subsubheading Programming
796 @subsubheading Documentation
800 @subsubheading Support
804 @subsubheading Translation
812 @divClass{column-center-bottom}
813 @subheading Previous Contributors
815 @divClass{keep-bullets}
816 @subsubheading Programming
824 @subsubheading Documentation
828 @subsubheading Support
832 @subsubheading Translation
834 @translationsPrevious
842 @unnumberedsec Publications
844 @divClass{column-center-top}
845 @subheading What we wrote
847 @divClass{keep-bullets}
851 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
852 the Art of Shipping}. Forum Internacional Software Livre 2006
853 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
857 Erik Sandberg, @emph{Separating input language and formatter in
858 GNU Lilypond}. Master's Thesis, Uppsala University, Department of
859 Information Technology March 2006.
860 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
864 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
865 for automated music engraving}. Proceedings of the XIV Colloquium
866 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
867 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
875 @divClass{column-center-bottom}
877 @subheading What others wrote
879 @divClass{keep-bullets}
885 The German LinuxUser magazine wrote an
886 @uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
887 article about LilyPond}.
893 In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
894 articles on his personal site}, Andrew Hawryluk compares Finale
895 and LilyPond in general terms, and evaluates engraving
896 capabilities of both pieces of software in detail. The second
897 article is an instructive analysis of engraving issues in
898 Rachmaninoff's Piano Prelude No. 6, including comparisons with a
899 hand-engraved reference edition.
904 @uref{http://distrowatch.com,DistroWatch} awards LilyPond and
905 @uref{http://distrowatch.com/weekly.php?issue=20060605,writes}
906 @qq{Ladies and Gentleman, we are pleased to announce that, based
907 on readers' requests, the DistroWatch May 2006 donation has been
908 awarded to LilyPond (@euro{}190.00) and Lua (US$250.00).}
913 @uref{http://linuxjournal.com,Linux Journal} publishes an article
914 titled @uref{http://www.linuxjournal.com/article/8364, Make
915 Stunning Schenker Graphs with GNU LilyPond}. It is an in-depth
916 but hands-on feature article with crisp LilyPond graphics. Author
917 Kris Shaffer remarks @qq{GNU Lilypond generates beautiful graphics
918 that make commercial alternatives seem second-rate.}
923 The Belgian newspaper De Standaard investigates what drives Free
924 Software authors in an article titled
925 @uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
926 Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
927 knowlegde) in its @q{DS2 bijlage}. LilyPond is used as an example
928 and the article is interspersed with quotes from an email
929 interview with Jan Nieuwenhuizen. This marks LilyPond's first
930 appearance in mainstream printed press.
935 A French article on the LilyPond 2.6 release appeared on
936 @uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
941 The editors of Computer!Totaal, a Dutch computer magazine,
942 @uref{http://lilypond.org/web/images/computer-totaal.jpeg,
943 describe LilyPond} in the October 2004 issue as: @qq{Wonderful
944 free (open source) software [..] The sheet music produced by
945 LilyPond is exceptionally pretty [..] a very powerful system that
946 can do almost anything.}
951 Dave Phillips wrote an introductory article for
952 @uref{http://linuxjournal.com,Linux Journal}: At
953 the sounding edge: LilyPond, parts
954 @uref{http://www.linuxjournal.com/article/7657, one} and
955 @uref{http://www.linuxjournal.com/article/7719, two}.
961 @uref{http://www.all-day-breakfast.com/cannam/linux-musician/lilypond.html,interviewed}
962 Han-Wen Nienhuys and Jan Nieuwenhuizen on linuxmusician.com
963 (original site defunct). This interview was also reviewed in a
964 @uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
970 Jazz singer Gail Selkirk writes about
971 @uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
972 Diving into LilyPond}. @qq{... you can make lead sheets or full
973 orchestral parts, and the results can be stunning.}
974 @uref{http://www.computermusic.co.uk/, Computer Music Special},
984 @unnumberedsec Old news
986 @include web/news-front.itexi
988 @include web/news.itexi