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
16 @divClass{link-headings}
18 @divClass{column-center-top}
19 @subheading Interacting with the community
24 @ref{Contact}: get help, discuss, and keep in touch!
27 @ref{Tiny examples}: these are @emph{highly} recommended when
31 @ref{Bug reports}: something went wrong.
36 @divClass{column-left-bottom}
37 @subheading Making LilyPond better
42 @ref{Help us}: your assistance is requested.
45 @ref{Development}: for contributors and testers.
48 @ref{Authors}: the people who made LilyPond what it is today.
53 @divClass{column-right-bottom}
54 @subheading Miscellaneous
59 @ref{Publications}: what we wrote, and have had written about us.
62 @ref{Old news}: an archive.
84 @unnumberedsec Contact
87 @divClass{column-left-bottom}
88 @subheading User Discussions and Help
90 @subsubheading User mailing list: @code{lilypond-user@@gnu.org}
92 This mailing list is the main place for users to discuss and help
96 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
97 lilypond-user subscribe and info}
99 @uref{http://lists.gnu.org/archive/html/lilypond-user/,
101 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
103 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
106 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
107 send to lilypond-user with gmane}
110 @warning{When asking questions, please use @ref{Tiny examples}!}
112 @subsubheading LilyPond Snippet Repository
114 The LilyPond Snippet Repository is a large collection of
115 user-submitted examples, which can freely be copied and used
116 in your own works. See what other people have written,
120 @uref{http://lsr.dsi.unimi.it}
123 Particularly instructive examples from LSR are included in our
124 official documentation, in @ref{Snippets}.
129 Some level of support is provided on our IRC channel,
132 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
135 This channel has no public archive, so any question that may
136 be useful for others would better be posted to one of the mailing lists.
139 <form action="http://webchat.freenode.net"
143 <input name="nick" type="text" size="15" value="">
145 <input name="channels" type="hidden" value="lilypond">
146 <input type="submit" value="Join #lilypond IRC Chat">
149 <script language="JavaScript" type="text/javascript">
150 var username = "web";
151 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
152 : window.navigator.language;
153 username += '-' + lang.substr(0, 2);
154 username += '-' + navigator.appName.substr(0, 2);
155 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
156 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
157 document.forms["f_lily_irc"].nick.value = username;
161 @subsubheading Other languages
164 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
165 Spanish mailing list}
167 @uref{http://www.lilypondforum.de/,
170 @uref{http://groups.google.com/group/lilypond-brasil,
173 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
176 @uref{http://www.lilypondforum.nl/,
183 @divClass{column-right-top}
184 @subheading Stay Informed
186 @subsubheading LilyPond Report
188 The easiest way to keep touch is by reading our community
189 newsletter, the LilyPond Report:
192 @uref{http://news.lilynet.net}
195 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
197 This mailing list is a low-volume, read-only list which receives
198 notifications of new releases.
201 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
202 info-lilypond subscribe and info}
204 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
206 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
208 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
211 @c don't include gmane posting here. -gp
218 @divClass{column-right-bottom}
219 @subheading Developer Discussion
221 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
223 Most developer discussion takes place on this list. Patches
227 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
228 lilypond-devel subscribe and info}
230 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
232 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
234 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
237 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
238 send to lilypond-devel with gmane}
242 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
244 Bug-specific discussion takes place here.
247 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
248 bug-lilypond subscribe and info}
250 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
252 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
254 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
257 @c don't include gmane posting here. -gp
260 @warning{Before sending a message to the bug list, please read our
261 guidelines for @ref{Bug reports}.}
268 @unnumberedsec Tiny examples
270 @divClass{column-center-top}
271 @subheading What are @qq{Tiny examples}?
273 A tiny example is an example from which nothing can be removed.
276 @divClass{column-left-bottom}
277 @subheading Why create them?
279 @divClass{keep-bullets}
283 The simpler the example is, the quicker potential helpers can
284 understand it and help you.
287 A simple example demonstrates that you have put effort towards
288 solving the problem yourself. When people send huge portions of
289 input, it looks like they don't care how if we help them or not.
292 Creating a tiny example forces you to understand what is
293 happening. Many false problem reports can be avoided by
294 attempting to create a tiny example; if you cannot replicate a
295 @qq{bug} in a tiny example, then the problem was probably an
296 insufficient understanding of LilyPond, not an actual bug!
304 @divClass{column-right-bottom}
305 @subheading How do I create them?
307 @divClass{keep-bullets}
311 Include the \version number.
314 Make it small! Examples about spacing or page layout might
315 require many bars of music, but most issues can be reproduced
316 using only a single measure.
319 When trying to create an example, try commenting out @w{(@code{%}
320 or @code{%@{ @dots{} %@}})} sections of your file. If you can
321 comment something while still demonstrating the main idea, then
322 remove the commented-material!
325 Avoid using complicated notes, keys, or time signatures, unless
326 the bug is about the behavior of those items.
329 Do not use @code{\override} or @code{\set} commands unless the bug
330 is about those particular commands.
341 @unnumberedsec Bug reports
343 @divClass{column-center-top}
344 @subheading Step 1: Known bugs
346 If you have input that results in a crash or an erroneous output,
347 then that is a bug. There is a list of current bugs on our google
351 @uref{http://code.google.com/p/lilypond/issues/list}
354 @warning{Please @strong{DO NOT} add bug reports directly to the
355 bug tracker. Once an issue has been added to the tracker, feel
356 free to add more information to that report.}
361 @divClass{column-left-bottom}
362 @subheading Step 2: Creating a bug report
364 If you have discovered a bug which is not listed, please help us
365 by creating a bug report.
367 @warning{We only accept bug reports in the form of
368 @ref{Tiny examples}. We have very limited resources to deal with
369 bug reports, so any non-minimal example will be rejected. Almost
370 every bug can be demonstrated in four notes or less!}
372 Here is an example of a good bug report:
375 %% the octavation command doesn't
376 %% change the output at all!
388 @divClass{column-right-bottom}
389 @subheading Step 3: Sending a bug report
391 Once you have verified that the issue is not already known and
392 created a bug report, please send it to us!
394 @divClass{keep-bullets}
398 If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org,
399 bug-lilypond@@gnu.org} mailing list, send an email like normal.
402 If you are not subscribed, you can still post a bug report with
404 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
405 gmane lilypond.bugs web interface}.
407 However, there is a strict @qq{no top-posting} check on the gmane
408 interface, which is often incorrectly triggered by lilypond files.
409 To avoid this, please add:
412 > I'm not top posting.
416 (you @emph{must} include the @code{>} ) to the top of your bug
422 Once your bug has been sent to the list, our Bug Squad will
423 examine the report. Please allow up to 24 hours, as we have a
424 limited number of volunteers for this task. They may ask you for
425 more information, or may add the report to the tracker and let you
426 know what the issue number is.
428 You may mark the bug so that you automatically receive emails when
429 any activity on the bug occurs. This requires you have a google
435 @unnumberedsec Help us
437 @divClass{column-center-top}
442 @divClass{column-left-top}
443 @divClass{keep-bullets}
449 @divClass{column-right-top}
456 @unnumberedsec Development
458 @divClass{heading-center}
460 @heading Development for LilyPond @version
463 @heading Development for LilyPond @versionDevel
467 @warning{These are @emph{unstable development} versions. If you
468 have the slightest doubt about how to use or install LilyPond, we
469 urge you to use the stable @ref{Download}, and read the stable
474 @divClass{column-center-top}
475 @subheading Release numbers
477 There are two sets of releases for LilyPond: stable releases, and
478 unstable development releases. Stable versions have an
479 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
480 Development versions have an odd-numbered @q{minor} version number
481 (e.g., 2.7, 2.9, 2.11).
486 @divClass{column-left-top}
489 Instructions for git and compiling are in the Contributor's Guide.
492 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
495 Documentation writers and testers will generally want to download
500 @downloadDevelLinuxNormal
502 @downloadDevelLinuxBig
504 @downloadDevelLinuxPPC
506 @downloadDevelFreeBSDNormal
508 @downloadDevelFreeBSDBig
510 @downloadDevelDarwinNormal
512 @downloadDevelDarwinPPC
514 @downloadDevelWindows
523 @divClass{column-right-top}
524 @subheading Contributor's Guide
526 LilyPond development is a fairly complicated matter. In order to
527 help new contributors, and to keep the whole system (mostly)
528 stable, we have written a manual for development tasks.
530 @docLinksBare{Contributor's Guide, contributor,
531 @rcontribnamed{Top,Contributor's Guide},
532 @manualDevelContributorSplit,
533 @manualDevelContributorBig, 500 kB,
534 @manualDevelContributorPdf, 2.8 MB}
539 @divClass{column-center-top}
540 @subheading Regression tests
542 @divClass{keep-bullets}
548 @uref{../../input/regression/collated-files.html, Regression tests}:
549 This release's regtests.
550 (@uref{../../input/regression/collated-files.pdf, pdf version})
553 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
554 This release's musicXML tests.
555 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
558 @uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}:
559 This release's abc2ly tests.
560 (@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version})
563 @uref{../../input/regression/lilypond-book/collated-files.html, lilypond-book tests}:
564 This release's lilypond-book tests.
565 (@uref{../../input/regression/lilypond-book/collated-files.pdf, pdf version})
571 @subsubheading Development version
574 @item @regtestDevel (@regtestDevelPdf{})
576 @item @regtestDevelXml (@regtestDevelXmlPdf{})
578 @item @regtestDevelAbc (@regtestDevelAbcPdf{})
580 @item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{})
583 @subsubheading Stable version
586 @item @regtestStable (@regtestStablePdf{})
588 @item @regtestStableXml (@regtestStableXmlPdf{})
590 @item @regtestStableAbc (@regtestStableAbcPdf{})
592 @item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{})
597 @subsubheading All versions
600 @item @uref{http://lilypond.org/test, Archive of regression tests}:
601 Comparisons between versions.
609 @divClass{column-center-bottom}
613 @warning{These manuals are for LilyPond @version{}; the latest
614 manuals can be found at @url{http://lilypond.org}}
617 @divClass{normal-table}
618 @multitable @columnfractions .3 .3 .3
619 @headitem Introduction
621 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
623 @docLinkBig{Learning,learning,@manualDevelLearningBig}
625 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
628 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
630 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
632 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
635 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
637 @docLinkBig{Essay,essay,@manualDevelEssayBig}
639 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
644 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
646 @docLinkBig{Notation,notation,@manualDevelNotationBig}
648 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
651 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
653 @docLinkBig{Usage,usage,@manualDevelUsageBig}
655 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
658 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
660 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
662 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
667 @docLinkSplit{Web,web,@manualDevelWebSplit}
669 @docLinkBig{Web,web,@manualDevelWebBig}
671 @docLinkPdf{Web,web,@manualDevelWebPdf}
674 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
676 @docLinkBig{Changes,changes,@manualDevelChangesBig}
678 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
681 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
683 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
685 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
688 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
690 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
692 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
695 @headitem Downloadable
710 @unnumberedsec Authors
712 @divClass{column-left-top}
713 @subheading Current Development Team
715 @divClass{keep-bullets}
720 @divClass{column-right-top}
721 @subheading Previous Development Team
723 @divClass{keep-bullets}
729 @divClass{column-center-top}
730 @subheading Current Contributors
732 @divClass{keep-bullets}
733 @subsubheading Programming
741 @subsubheading Documentation
745 @subsubheading Bug squad
749 @subsubheading Support
753 @subsubheading Translation
761 @divClass{column-center-bottom}
762 @subheading Previous Contributors
764 @divClass{keep-bullets}
765 @subsubheading Programming
773 @subsubheading Documentation
777 @c uncomment when we have any previous members -gp
778 @c @subsubheading Bug squad
782 @subsubheading Support
786 @subsubheading Translation
788 @translationsPrevious
796 @unnumberedsec Publications
798 @divClass{column-center-top}
799 @subheading What we wrote about LilyPond
801 @divClass{keep-bullets}
803 @include we-wrote.itexi
809 @divClass{column-center-bottom}
811 @subheading What people did with LilyPond
814 @divClass{keep-bullets}
816 @include others-did.itexi
823 @unnumberedsec Old news
825 @include web/news-front.itexi
827 @include web/news.itexi