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 own 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 @divClass{keep-bullets}
396 If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org,
397 bug-lilypond@@gnu.org} mailing list, send an email like normal.
400 If you are not subscribed, you can still post a bug report with
402 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
403 gmane lilypond.bugs web interface}.
405 However, there is a strict @qq{no top-posting} check on the gmane
406 interface, which is often incorrectly triggered by lilypond files.
407 To avoid this, please add:
410 > I'm not top posting.
414 (you @emph{must} include the @code{>} ) to the top of your bug
420 Once your bug has been sent to the list, our Bug Squad will
421 examine the report. Please allow up to 24 hours, as we have a
422 limited number of volunteers for this task. They may ask you for
423 more information, or may add the report to the tracker and let you
424 know what the issue number is.
426 You may mark the bug so that you automatically receive emails when
427 any activity on the bug occurs. This requires you have a google
433 @unnumberedsec Help us
435 @divClass{column-center-top}
440 @divClass{column-left-top}
441 @divClass{keep-bullets}
447 @divClass{column-right-top}
454 @unnumberedsec Development
456 @divClass{heading-center}
458 @heading Development for LilyPond @version
461 @heading Development for LilyPond @versionDevel
465 @warning{These are @emph{unstable development} versions. If you
466 have the slightest doubt about how to use or install LilyPond, we
467 urge you to use the stable @ref{Download}, and read the stable
472 @divClass{column-center-top}
473 @subheading Release numbers
475 There are two sets of releases for LilyPond: stable releases, and
476 unstable development releases. Stable versions have an
477 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
478 Development versions have an odd-numbered @q{minor} version number
479 (e.g., 2.7, 2.9, 2.11).
484 @divClass{column-left-top}
487 Instructions for git and compiling are in the Contributor's Guide.
490 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
493 Documentation writers and testers will generally want to download
498 @downloadDevelLinuxNormal
500 @downloadDevelLinuxBig
502 @downloadDevelLinuxPPC
504 @downloadDevelFreeBSDNormal
506 @downloadDevelFreeBSDBig
508 @downloadDevelDarwinNormal
510 @downloadDevelDarwinPPC
512 @downloadDevelWindows
521 @divClass{column-right-top}
522 @subheading Contributor's Guide
524 LilyPond development is a fairly complicated matter. In order to
525 help new contributors, and to keep the whole system (mostly)
526 stable, we have written a manual for development tasks.
528 @docLinksBare{Contributor's Guide, contributor,
529 @rcontribnamed{Top,Contributor's Guide},
530 @manualDevelContributorSplit,
531 @manualDevelContributorBig, 500 kB,
532 @manualDevelContributorPdf, 2.8 MB}
537 @divClass{column-center-top}
538 @subheading Regression tests
540 @divClass{keep-bullets}
546 @uref{../../input/regression/collated-files.html, Regression tests}:
547 This release's regtests.
548 (@uref{../../input/regression/collated-files.pdf, pdf version})
551 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
552 This release's musicXML tests.
553 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
557 @item @regtestDevel (@regtestDevelPdf{})
559 @item @regtestDevelXml (@regtestDevelXmlPdf{})
561 @item @regtestStable (@regtestStablePdf{})
563 @item @regtestStableXml (@regtestStableXmlPdf{})
567 @item @uref{http://lilypond.org/test, Archive of regression tests}:
568 Comparisons between versions.
576 @divClass{column-center-bottom}
580 @warning{These manuals are for LilyPond @version{}; the latest
581 manuals can be found at @url{http://lilypond.org}}
584 @divClass{normal-table}
585 @multitable @columnfractions .3 .3 .3
586 @headitem Introduction
588 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
590 @docLinkBig{Learning,learning,@manualDevelLearningBig}
592 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
595 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
597 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
599 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
602 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
604 @docLinkBig{Essay,essay,@manualDevelEssayBig}
606 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
611 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
613 @docLinkBig{Notation,notation,@manualDevelNotationBig}
615 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
618 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
620 @docLinkBig{Usage,usage,@manualDevelUsageBig}
622 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
625 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
627 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
629 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
634 @docLinkSplit{Web,web,@manualDevelWebSplit}
636 @docLinkBig{Web,web,@manualDevelWebBig}
638 @docLinkPdf{Web,web,@manualDevelWebPdf}
641 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
643 @docLinkBig{Changes,changes,@manualDevelChangesBig}
645 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
648 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
650 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
652 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
655 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
657 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
659 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
662 @headitem Downloadable
677 @unnumberedsec Authors
679 @divClass{column-left-top}
680 @subheading Current Development Team
682 @divClass{keep-bullets}
687 @divClass{column-right-top}
688 @subheading Previous Development Team
690 @divClass{keep-bullets}
696 @divClass{column-center-top}
697 @subheading Current Contributors
699 @divClass{keep-bullets}
700 @subsubheading Programming
708 @subsubheading Documentation
712 @subsubheading Bug squad
716 @subsubheading Support
720 @subsubheading Translation
728 @divClass{column-center-bottom}
729 @subheading Previous Contributors
731 @divClass{keep-bullets}
732 @subsubheading Programming
740 @subsubheading Documentation
744 @c uncomment when we have any previous members -gp
745 @c @subsubheading Bug squad
749 @subsubheading Support
753 @subsubheading Translation
755 @translationsPrevious
763 @unnumberedsec Publications
765 @divClass{column-center-top}
766 @subheading What we wrote about LilyPond
768 @divClass{keep-bullets}
772 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
773 the Art of Shipping}. Forum Internacional Software Livre 2006
774 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
778 Erik Sandberg, @emph{Separating input language and formatter in
779 GNU LilyPond}. Master's Thesis, Uppsala University, Department of
780 Information Technology March 2006.
781 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
785 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
786 for automated music engraving}. Proceedings of the XIV Colloquium
787 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
788 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
796 @divClass{column-center-bottom}
798 @subheading What people did with LilyPond
801 @divClass{keep-bullets}
805 Graham Percival, Tosten Anders, and George Tzanetakis,
806 @emph{Generating Targeted Rhythmic Exercises for Music Students
807 with Constraint Satisfaction Programming}, International Computer
808 Music Conference 2008.
811 Alexandre Tachard Passos, Marcos Sampaio, Pedro Kröger, Givaldo de Cidra,
812 @emph{Functional Harmonic Analysis and Computational Musicology
813 in Rameau}, Proceedings of the 12th Brazilian Symposium on Computer
814 Music, 2009, pp. 207-210.
817 Alberto Simões, Anália Lourenço and José João Almeida,
818 @emph{Using Text Mining Techniques for Classical Music Scores Analysis},
819 New Trends in Artificial Intelligence, 2007 J. Neves et al ed.
824 @emph{Real-time generation of music notation via audience interaction using
825 python and GNU lilypond}. Proceedings of the 2005 Conference on New interfaces
826 For Musical Expression (Vancouver, Canada, May 26 - 28, 2005).
836 @unnumberedsec Old news
838 @include web/news-front.itexi
840 @include web/news.itexi