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}!}
110 @subsubheading LilyPond Snippet Repository
112 The LilyPond Snippet Repository is a large collection of
113 user-submitted examples, which can freely be copied and used
114 in your owm works. See what other people have written,
118 @uref{http://lsr.dsi.unimi.it}
121 Particularly instructive examples from LSR are included in our
122 official documentation, in @ref{Snippets}.
127 Some level of support is provided on our IRC channel,
130 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
133 This channel has no public archive, so any question that may
134 be useful for others would better be posted to one of the mailing lists.
137 <form action="http://webchat.freenode.net"
141 <input name="nick" type="text" size="15" value="">
143 <input name="channels" type="hidden" value="lilypond">
144 <input type="submit" value="Join #lilypond IRC Chat">
147 <script language="JavaScript" type="text/javascript">
148 var username = "web";
149 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
150 : window.navigator.language;
151 username += '-' + lang.substr(0, 2);
152 username += '-' + navigator.appName.substr(0, 2);
153 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
154 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
155 document.forms["f_lily_irc"].nick.value = username;
159 @subsubheading Other languages
162 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
163 Spanish mailing list}
165 @uref{http://www.lilypondforum.de/,
168 @uref{http://groups.google.com/group/lilypond-brasil,
171 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
174 @uref{http://www.lilypondforum.nl/,
181 @divClass{column-right-top}
182 @subheading Stay Informed
184 @subsubheading LilyPond Report
186 The easiest way to keep touch is by reading our community
187 newsletter, the LilyPond Report:
190 @uref{http://news.lilynet.net}
193 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
195 This mailing list is a low-volume, read-only list which receives
196 notifications of new releases.
199 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
200 info-lilypond subscribe and info}
202 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
204 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
206 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
209 @c don't include gmane posting here. -gp
216 @divClass{column-right-bottom}
217 @subheading Developer Discussion
219 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
221 Most developer discussion takes place on this list. Patches
225 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
226 lilypond-devel subscribe and info}
228 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
230 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
232 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
235 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
236 send to lilypond-devel with gmane}
240 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
242 Bug-specific discussion takes place here.
245 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
246 bug-lilypond subscribe and info}
248 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
250 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
252 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
255 @c don't include gmane posting here. -gp
258 @warning{Before sending a message to the bug list, please read our
259 guidelines for @ref{Bug reports}.}
266 @unnumberedsec Tiny examples
268 @divClass{column-center-top}
269 @subheading What are @qq{Tiny examples}?
271 A tiny example is an example from which nothing can be removed.
274 @divClass{column-left-bottom}
275 @subheading Why create them?
277 @divClass{keep-bullets}
281 The simpler the example is, the quicker potential helpers can
282 understand it and help you.
285 A simple example demonstrates that you have put effort towards
286 solving the problem yourself. When people send huge portions of
287 input, it looks like they don't care how if we help them or not.
290 Creating a tiny example forces you to understand what is
291 happening. Many false problem reports can be avoided by
292 attempting to create a tiny example; if you cannot replicate a
293 @qq{bug} in a tiny example, then the problem was probably an
294 insufficient understanding of LilyPond, not an actual bug!
302 @divClass{column-right-bottom}
303 @subheading How do I create them?
305 @divClass{keep-bullets}
309 Include the \version number.
312 Make it small! Examples about spacing or page layout might
313 require many bars of music, but most issues can be reproduced
314 using only a single measure.
317 When trying to create an example, try commenting out @w{(@code{%}
318 or @code{%@{ @dots{} %@}})} sections of your file. If you can
319 comment something while still demonstrating the main idea, then
320 remove the commented-material!
323 Avoid using complicated notes, keys, or time signatures, unless
324 the bug is about the behavior of those items.
327 Do not use @code{\override} or @code{\set} commands unless the bug
328 is about those particular commands.
339 @unnumberedsec Bug reports
341 @divClass{column-center-top}
342 @subheading Step 1: Known bugs
344 If you have input that results in a crash or an erroneous output,
345 then that is a bug. There is a list of current bugs on our google
349 @uref{http://code.google.com/p/lilypond/issues/list}
352 @warning{Please @strong{DO NOT} add bug reports directly to the
353 bug tracker. Once an issue has been added to the tracker, feel
354 free to add more information to that report.}
359 @divClass{column-left-bottom}
360 @subheading Step 2: Creating a bug report
362 If you have discovered a bug which is not listed, please help us
363 by creating a bug report.
365 @warning{We only accept bug reports in the form of
366 @ref{Tiny examples}. We have very limited resources to deal with
367 bug reports, so any non-minimal example will be rejected. Almost
368 every bug can be demonstrated in four notes or less!}
370 Here is an example of a good bug report:
373 %% the octavation command doesn't
374 %% change the output at all!
386 @divClass{column-right-bottom}
387 @subheading Step 3: Sending a bug report
389 Once you have verified that the issue is not already known and
390 created a bug report, please send it to us!
392 Unfortunately there is a strict @qq{no top-posting} check on the
393 bug list, which is often incorrectly triggered by lilypond files.
394 To avoid this, please add
397 > I'm not top posting.
401 (you must include the @code{>} ) to the top of your bug report.
403 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
404 Post with the gmane lilypond.bugs interface}, or send an email to
405 @uref{mailto:bug-lilypond@@gnu.org, bug-lilypond@@gnu.org}.
407 Once your bug has been sent to the list, our Bug Squad will
408 examine the report. Please allow up to 24 hours, as we have a
409 limited number of volunteers for this task. They may ask you for
410 more information, or may add the report to the tracker and let you
411 know what the issue number is.
413 You may mark the bug so that you automatically receive emails when
414 any activity on the bug occurs. This requires you have a google
420 @unnumberedsec Help us
422 @divClass{column-center-top}
427 @divClass{column-left-top}
428 @divClass{keep-bullets}
434 @divClass{column-right-top}
441 @unnumberedsec Development
443 @divClass{heading-center}
445 @heading Development for LilyPond @version
448 @heading Development for LilyPond @versionDevel
452 @warning{These are @emph{unstable development} versions. If you
453 have the slightest doubt about how to use or install LilyPond, we
454 urge you to use the stable @ref{Download}, and read the stable
459 @divClass{column-center-top}
460 @subheading Release numbers
462 There are two sets of releases for LilyPond: stable releases, and
463 unstable development releases. Stable versions have an
464 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
465 Development versions have an odd-numbered @q{minor} version number
466 (e.g., 2.7, 2.9, 2.11).
471 @divClass{column-left-top}
474 Instructions for git and compiling are in the Contributor's Guide.
477 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
480 Documentation writers and testers will generally want to download
485 @downloadDevelLinuxNormal
487 @downloadDevelLinuxBig
489 @downloadDevelLinuxPPC
491 @downloadDevelFreeBSDNormal
493 @downloadDevelFreeBSDBig
495 @downloadDevelDarwinNormal
497 @downloadDevelDarwinPPC
499 @downloadDevelWindows
508 @divClass{column-right-top}
509 @subheading Contributor's Guide
511 LilyPond development is a fairly complicated matter. In order to
512 help new contributors, and to keep the whole system (mostly)
513 stable, we have written a manual for development tasks.
515 @docLinksBare{Contributor's Guide, contributor,
516 @rcontribnamed{Top,Contributor's Guide},
517 @manualDevelContributorSplit,
518 @manualDevelContributorBig, 500 kB,
519 @manualDevelContributorPdf, 2.8 MB}
524 @divClass{column-center-top}
525 @subheading Regression tests
527 @divClass{keep-bullets}
533 @uref{../../input/regression/collated-files.html, Regression tests}:
534 This release's regtests.
535 (@uref{../../input/regression/collated-files.pdf, pdf version})
538 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
539 This release's musicXML tests.
540 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
544 @item @regtestDevel (@regtestDevelPdf{})
546 @item @regtestDevelXml (@regtestDevelXmlPdf{})
548 @item @regtestStable (@regtestStablePdf{})
550 @item @regtestStableXml (@regtestStableXmlPdf{})
554 @item @uref{http://lilypond.org/test, Archive of regression tests}:
555 Comparisons between versions.
563 @divClass{column-center-bottom}
567 @warning{These manuals are for LilyPond @version{}; the latest
568 manuals can be found at @url{http://lilypond.org}}
571 @divClass{normal-table}
572 @multitable @columnfractions .3 .3 .3
573 @headitem Introduction
575 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
577 @docLinkBig{Learning,learning,@manualDevelLearningBig}
579 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
582 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
584 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
586 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
589 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
591 @docLinkBig{Essay,essay,@manualDevelEssayBig}
593 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
598 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
600 @docLinkBig{Notation,notation,@manualDevelNotationBig}
602 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
605 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
607 @docLinkBig{Usage,usage,@manualDevelUsageBig}
609 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
612 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
614 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
616 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
621 @docLinkSplit{Web,web,@manualDevelWebSplit}
623 @docLinkBig{Web,web,@manualDevelWebBig}
625 @docLinkPdf{Web,web,@manualDevelWebPdf}
628 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
630 @docLinkBig{Changes,changes,@manualDevelChangesBig}
632 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
635 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
637 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
639 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
642 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
644 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
646 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
649 @headitem Downloadable
664 @unnumberedsec Authors
666 @divClass{column-left-top}
667 @subheading Current Development Team
669 @divClass{keep-bullets}
674 @divClass{column-right-top}
675 @subheading Previous Development Team
677 @divClass{keep-bullets}
683 @divClass{column-center-top}
684 @subheading Current Contributors
686 @divClass{keep-bullets}
687 @subsubheading Programming
695 @subsubheading Documentation
699 @subsubheading Bug squad
703 @subsubheading Support
707 @subsubheading Translation
715 @divClass{column-center-bottom}
716 @subheading Previous Contributors
718 @divClass{keep-bullets}
719 @subsubheading Programming
727 @subsubheading Documentation
731 @c uncomment when we have any previous members -gp
732 @c @subsubheading Bug squad
736 @subsubheading Support
740 @subsubheading Translation
742 @translationsPrevious
750 @unnumberedsec Publications
752 @divClass{column-center-top}
753 @subheading What we wrote about LilyPond
755 @divClass{keep-bullets}
759 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
760 the Art of Shipping}. Forum Internacional Software Livre 2006
761 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
765 Erik Sandberg, @emph{Separating input language and formatter in
766 GNU LilyPond}. Master's Thesis, Uppsala University, Department of
767 Information Technology March 2006.
768 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
772 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
773 for automated music engraving}. Proceedings of the XIV Colloquium
774 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
775 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
783 @divClass{column-center-bottom}
785 @subheading What people did with LilyPond
788 @divClass{keep-bullets}
792 Graham Percival, Tosten Anders, and George Tzanetakis,
793 @emph{Generating Targeted Rhythmic Exercises for Music Students
794 with Constraint Satisfaction Programming}, International Computer
795 Music Conference 2008.
798 A. Passos, M. Silva, P. Kroger, and G. Cidra,
799 @emph{Functional Harmonic Analysis and Computational Musicology
800 in Rameau}, Proceedings of the 12th Brazilian Symposium on Compute
801 Music, 2009, pp. 207-210.
804 Alberto Simões, Anália Lourenço and José João Almeida,
805 @emph{Using Text Mining Techniques for Classical Music Scores Analysis},
806 New Trends in Artificial Intelligence, 2007 J. Neves et al ed.
811 @emph{Real-time generation of music notation via audience interaction using
812 python and GNU lilypond}. Proceedings of the 2005 Conference on New interfaces
813 For Musical Expression (Vancouver, Canada, May 26 - 28, 2005).
814 New Interfaces For Musical Expression. National University of Singapore, Singapore, 240-241.
823 @unnumberedsec Old news
825 @include web/news-front.itexi
827 @include web/news.itexi