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
11 @include included/helpus.itexi
17 @divClass{column-center-top}
18 @subheading Interacting with the community
23 @ref{Contact}: get help, discuss, and keep in touch!
26 @ref{Tiny examples}: these are @emph{highly} recommended when
30 @ref{Bug reports}: something went wrong.
35 @divClass{column-left-bottom}
36 @subheading Making LilyPond better
41 @ref{Help us}: your assistance is requested.
44 @ref{Development}: for contributors and testers.
47 @ref{Authors}: the people who made LilyPond what it is today.
52 @divClass{column-right-bottom}
53 @subheading Miscellaneous
58 @ref{Publications}: what we wrote, and have had written about us.
61 @ref{Old news}: an archive.
82 @unnumberedsec Contact
85 @divClass{column-left-bottom}
86 @subheading User Discussions and Help
88 @subsubheading User mailing list: @code{lilypond-user@@gnu.org}
90 This mailing list is the main place for users to discuss and help
94 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
95 lilypond-user subscribe and info}
97 @uref{http://lists.gnu.org/archive/html/lilypond-user/,
99 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
101 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
104 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
105 send to lilypond-user with gmane}
108 @warning{When asking questions, please use @ref{Tiny examples}!}
113 Some level of support is provided on our IRC channel,
116 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
119 This channel has no public archive, so any question that may
120 be useful for others would better be posted to one of the mailing lists.
123 <form action="http://webchat.freenode.net"
127 <input name="nick" type="text" size="15" value="">
129 <input name="channels" type="hidden" value="lilypond">
130 <input type="submit" value="Join #lilypond IRC Chat">
133 <script language="JavaScript" type="text/javascript">
134 var username = "web";
135 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
136 : window.navigator.language;
137 username += '-' + lang.substr(0, 2);
138 username += '-' + navigator.appName.substr(0, 2);
139 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
140 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
141 document.forms["f_lily_irc"].nick.value = username;
145 @subsubheading Other languages
148 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
149 Spanish mailing list}
151 @uref{http://www.lilypondforum.de/,
154 @uref{http://groups.google.com/group/lilypond-brasil,
157 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
160 @uref{http://www.lilypondforum.nl/,
167 @divClass{column-right-top}
168 @subheading Stay Informed
170 @subsubheading LilyPond Report
172 The easiest way to keep touch is by reading our community
173 newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
175 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
177 This mailing list is a low-volume, read-only list which receives
178 notifications of new releases.
181 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
182 info-lilypond subscribe and info}
184 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
186 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
188 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
191 @c don't include gmane posting here. -gp
198 @divClass{column-right-bottom}
199 @subheading Developer Discussion
201 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
203 Most developer discussion takes place on this list. Patches
207 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
208 lilypond-devel subscribe and info}
210 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
212 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
214 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
217 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
218 send to lilypond-devel with gmane}
222 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
224 Bug-specific discussion takes place here.
227 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
228 bug-lilypond subscribe and info}
230 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
232 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
234 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
237 @c don't include gmane posting here. -gp
240 @warning{Before sending a message to the bug list, please read our
241 guidelines for @ref{Bug reports}.}
248 @unnumberedsec Tiny examples
250 @divClass{column-center-top}
251 @subheading What are @qq{Tiny examples}?
253 A tiny example is an example from which nothing can be removed.
256 @divClass{column-left-bottom}
257 @subheading Why create them?
259 @divClass{keep-bullets}
263 The simpler the example is, the quicker potential helpers can
264 understand it and help you.
267 A simple example demonstrates that you have put effort towards
268 solving the problem yourself. When people send huge portions of
269 input, it looks like they don't care how if we help them or not.
272 Creating a tiny example forces you to understand what is
273 happening. Many false problem reports can be avoided by
274 attempting to create a tiny example; if you cannot replicate a
275 @qq{bug} in a tiny example, then the problem was probably an
276 insufficient understanding of LilyPond, not an actual bug!
284 @divClass{column-right-bottom}
285 @subheading How do I create them?
287 @divClass{keep-bullets}
291 Include the \version number.
294 Make it small! Examples about spacing or page layout might
295 require many bars of music, but most issues can be reproduced
296 using only a single measure.
299 When trying to create an example, try commenting out @w{(@code{%}
300 or @code{%@{ @dots{} %@}})} sections of your file. If you can
301 comment something while still demonstrating the main idea, then
302 remove the commented-material!
305 Avoid using complicated notes, keys, or time signatures, unless
306 the bug is about the behavior of those items.
309 Do not use @code{\override} or @code{\set} commands unless the bug
310 is about those particular commands.
321 @unnumberedsec Bug reports
323 @divClass{column-center-top}
324 @subheading Step 1: Known bugs
326 If you have input that results in a crash or an erroneous output,
327 then that is a bug. There is a list of current bugs on our google
331 @uref{http://code.google.com/p/lilypond/issues/list}
334 @warning{Please @strong{DO NOT} add bug reports directly to the
335 bug tracker. Once an issue has been added to the tracker, feel
336 free to add more information to that report.}
341 @divClass{column-left-bottom}
342 @subheading Step 2: Creating a bug report
344 If you have discovered a bug which is not listed, please help us
345 by creating a bug report.
347 @warning{We only accept bug reports in the form of @ref{Tiny
348 examples}. We have very limited resources to deal with bug
349 reports, so any non-minimal example will be rejected. Almost
350 every bug can be demonstrated in four notes or less!}
352 Here is an example of a good bug report:
355 %% the octavation command doesn't
356 %% change the output at all!
359 \paper@{ ragged-right=##t @}
369 @divClass{column-right-bottom}
370 @subheading Step 3: Sending a bug report
372 Once you have verified that the issue is not already known and
373 created a bug report, please send it to us!
375 Unfortunately there is a strict @qq{no top-posting} check on the
376 bug list, which is often incorrectly triggered by lilypond files.
377 To avoid this, please add
380 > I'm not top posting.
384 (you must include the @code{>} ) to the top of your bug report.
386 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
387 Post with the gmane lilypond.bugs interface}, or send an email to
388 @uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
390 Once your bug has been sent to the list, our Bug Meister will
391 examine the report. He may ask you for more information, or may
392 add the report to the tracker and let you know what the issue
395 You may mark the bug so that you automatically receive emails when
396 any activity on the bug occurs. This requires you have a google
402 @unnumberedsec Help us
404 @divClass{column-center-top}
409 @divClass{column-left-top}
410 @divClass{keep-bullets}
416 @divClass{column-right-top}
423 @unnumberedsec Development
425 @divClass{heading-center}
427 @heading Development for LilyPond @version
430 @heading Development for LilyPond @versionDevel
434 @warning{These are @emph{unstable development} versions. If you
435 have the slightest doubt about how to use or install LilyPond, we
436 urge you to use the stable @ref{Download}, and read the stable
441 @divClass{column-center-top}
442 @subheading Release numbers
444 There are two sets of releases for LilyPond: stable releases, and
445 unstable development releases. Stable versions have an
446 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
447 Development versions have an odd-numbered @q{minor} version number
448 (e.g., 2.7, 2.9, 2.11).
453 @divClass{column-left-top}
456 Instructions for git and compiling are in the Contributor's Guide.
459 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
462 Documentation writers and testers will generally want to download
467 @downloadDevelLinuxNormal
469 @downloadDevelLinuxBig
471 @downloadDevelLinuxPPC
473 @downloadDevelFreeBSDNormal
475 @downloadDevelFreeBSDBig
477 @downloadDevelDarwinNormal
479 @downloadDevelDarwinPPC
481 @downloadDevelWindows
490 @divClass{column-right-top}
491 @subheading Contributor's Guide
493 LilyPond development is a fairly complicated matter. In order to
494 help new contributors, and to keep the whole system (mostly)
495 stable, we have written a manual for development tasks.
497 @docLinksBare{Contributor's Guide, contributor,
498 @rcontribnamed{Top,Contributor's Guide},
499 @manualDevelContributorSplit,
500 @manualDevelContributorBig, 500 kB,
501 @manualDevelContributorPdf, 2.8 MB}
506 @divClass{column-center-top}
507 @subheading Regression tests
509 @divClass{keep-bullets}
515 @uref{../../input/regression/collated-files.html, Regression tests}:
516 This release's regtests.
517 (@uref{../../input/regression/collated-files.pdf, pdf version})
520 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
521 This release's musicXML tests.
522 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
526 @item @regtestDevel (@regtestDevelPdf{})
528 @item @regtestDevelXml (@regtestDevelXmlPdf{})
530 @item @regtestStable (@regtestStablePdf{})
532 @item @regtestStableXml (@regtestStableXmlPdf{})
536 @item @uref{http://lilypond.org/test, Archive of regression tests}:
537 Comparisons between versions.
545 @divClass{column-center-bottom}
549 @warning{These manuals are for LilyPond @version{}; the latest
550 manuals can be found at @url{http://lilypond.org}}
553 @divClass{normal-table}
554 @multitable @columnfractions .3 .3 .3
555 @headitem Introduction
557 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
559 @docLinkBig{Learning,learning,@manualDevelLearningBig}
561 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
564 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
566 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
568 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
571 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
573 @docLinkBig{Essay,essay,@manualDevelEssayBig}
575 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
580 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
582 @docLinkBig{Notation,notation,@manualDevelNotationBig}
584 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
587 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
589 @docLinkBig{Usage,usage,@manualDevelUsageBig}
591 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
594 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
596 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
598 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
603 @docLinkSplit{Web,web,@manualDevelWebSplit}
605 @docLinkBig{Web,web,@manualDevelWebBig}
607 @docLinkPdf{Web,web,@manualDevelWebPdf}
610 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
612 @docLinkBig{Changes,changes,@manualDevelChangesBig}
614 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
617 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
619 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
621 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
624 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
626 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
628 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
631 @headitem Downloadable
646 @unnumberedsec Authors
648 @help{Under construction; this is not an accurate list!}
651 @divClass{column-left-top}
652 @subheading Current Development Team
654 @divClass{keep-bullets}
659 @divClass{column-right-top}
660 @subheading Previous Development Team
662 @divClass{keep-bullets}
668 @divClass{column-center-top}
669 @subheading Current Contributors
671 @divClass{keep-bullets}
672 @subsubheading Programming
680 @subsubheading Documentation
684 @subsubheading Bug squad
688 @subsubheading Support
692 @subsubheading Translation
700 @divClass{column-center-bottom}
701 @subheading Previous Contributors
703 @divClass{keep-bullets}
704 @subsubheading Programming
712 @subsubheading Documentation
716 @c uncomment when we have any previous members -gp
717 @c @subsubheading Bug squad
721 @subsubheading Support
725 @subsubheading Translation
727 @translationsPrevious
735 @unnumberedsec Publications
737 @divClass{column-center-top}
738 @subheading What we wrote
740 @divClass{keep-bullets}
744 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
745 the Art of Shipping}. Forum Internacional Software Livre 2006
746 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
750 Erik Sandberg, @emph{Separating input language and formatter in
751 GNU Lilypond}. Master's Thesis, Uppsala University, Department of
752 Information Technology March 2006.
753 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
757 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
758 for automated music engraving}. Proceedings of the XIV Colloquium
759 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
760 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
768 @divClass{column-center-bottom}
770 @subheading What others wrote
772 @divClass{keep-bullets}
778 The German LinuxUser magazine wrote an
779 @uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
780 article about LilyPond}.
786 In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
787 articles on his personal site}, Andrew Hawryluk compares Finale
788 and LilyPond in general terms, and evaluates engraving
789 capabilities of both pieces of software in detail. The second
790 article is an instructive analysis of engraving issues in
791 Rachmaninoff's Piano Prelude No. 6, including comparisons with a
792 hand-engraved reference edition.
797 @uref{http://distrowatch.com,DistroWatch} awards LilyPond and
798 @uref{http://distrowatch.com/weekly.php?issue=20060605,writes}
799 @qq{Ladies and Gentleman, we are pleased to announce that, based
800 on readers' requests, the DistroWatch May 2006 donation has been
801 awarded to LilyPond (@euro{}190.00) and Lua (US$250.00).}
806 @uref{http://linuxjournal.com,Linux Journal} publishes an article
807 titled @uref{http://www.linuxjournal.com/article/8364, Make
808 Stunning Schenker Graphs with GNU LilyPond}. It is an in-depth
809 but hands-on feature article with crisp LilyPond graphics. Author
810 Kris Shaffer remarks @qq{GNU Lilypond generates beautiful graphics
811 that make commercial alternatives seem second-rate.}
816 The Belgian newspaper De Standaard investigates what drives Free
817 Software authors in an article titled
818 @uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
819 Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
820 knowlegde) in its @q{DS2 bijlage}. LilyPond is used as an example
821 and the article is interspersed with quotes from an email
822 interview with Jan Nieuwenhuizen. This marks LilyPond's first
823 appearance in mainstream printed press.
828 A French article on the LilyPond 2.6 release appeared on
829 @uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
834 The editors of Computer!Totaal, a Dutch computer magazine,
835 @uref{http://lilypond.org/web/images/computer-totaal.jpeg,
836 describe LilyPond} in the October 2004 issue as: @qq{Wonderful
837 free (open source) software [..] The sheet music produced by
838 LilyPond is exceptionally pretty [..] a very powerful system that
839 can do almost anything.}
844 Dave Phillips wrote an introductory article for
845 @uref{http://linuxjournal.com,Linux Journal}: At
846 the sounding edge: LilyPond, parts
847 @uref{http://www.linuxjournal.com/article/7657, one} and
848 @uref{http://www.linuxjournal.com/article/7719, two}.
854 @uref{http://www.all-day-breakfast.com/cannam/linux-musician/lilypond.html,interviewed}
855 Han-Wen Nienhuys and Jan Nieuwenhuizen on linuxmusician.com
856 (original site defunct). This interview was also reviewed in a
857 @uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
863 Jazz singer Gail Selkirk writes about
864 @uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
865 Diving into LilyPond}. @qq{... you can make lead sheets or full
866 orchestral parts, and the results can be stunning.}
867 @uref{http://www.computermusic.co.uk/, Computer Music Special},
877 @unnumberedsec Old news
879 @include web/news-front.itexi
881 @include web/news.itexi