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 LilyPond Report:
176 @uref{http://news.lilynet.net}
179 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
181 This mailing list is a low-volume, read-only list which receives
182 notifications of new releases.
185 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
186 info-lilypond subscribe and info}
188 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
190 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
192 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
195 @c don't include gmane posting here. -gp
202 @divClass{column-right-bottom}
203 @subheading Developer Discussion
205 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
207 Most developer discussion takes place on this list. Patches
211 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
212 lilypond-devel subscribe and info}
214 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
216 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
218 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
221 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
222 send to lilypond-devel with gmane}
226 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
228 Bug-specific discussion takes place here.
231 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
232 bug-lilypond subscribe and info}
234 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
236 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
238 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
241 @c don't include gmane posting here. -gp
244 @warning{Before sending a message to the bug list, please read our
245 guidelines for @ref{Bug reports}.}
252 @unnumberedsec Tiny examples
254 @divClass{column-center-top}
255 @subheading What are @qq{Tiny examples}?
257 A tiny example is an example from which nothing can be removed.
260 @divClass{column-left-bottom}
261 @subheading Why create them?
263 @divClass{keep-bullets}
267 The simpler the example is, the quicker potential helpers can
268 understand it and help you.
271 A simple example demonstrates that you have put effort towards
272 solving the problem yourself. When people send huge portions of
273 input, it looks like they don't care how if we help them or not.
276 Creating a tiny example forces you to understand what is
277 happening. Many false problem reports can be avoided by
278 attempting to create a tiny example; if you cannot replicate a
279 @qq{bug} in a tiny example, then the problem was probably an
280 insufficient understanding of LilyPond, not an actual bug!
288 @divClass{column-right-bottom}
289 @subheading How do I create them?
291 @divClass{keep-bullets}
295 Include the \version number.
298 Make it small! Examples about spacing or page layout might
299 require many bars of music, but most issues can be reproduced
300 using only a single measure.
303 When trying to create an example, try commenting out @w{(@code{%}
304 or @code{%@{ @dots{} %@}})} sections of your file. If you can
305 comment something while still demonstrating the main idea, then
306 remove the commented-material!
309 Avoid using complicated notes, keys, or time signatures, unless
310 the bug is about the behavior of those items.
313 Do not use @code{\override} or @code{\set} commands unless the bug
314 is about those particular commands.
325 @unnumberedsec Bug reports
327 @divClass{column-center-top}
328 @subheading Step 1: Known bugs
330 If you have input that results in a crash or an erroneous output,
331 then that is a bug. There is a list of current bugs on our google
335 @uref{http://code.google.com/p/lilypond/issues/list}
338 @warning{Please @strong{DO NOT} add bug reports directly to the
339 bug tracker. Once an issue has been added to the tracker, feel
340 free to add more information to that report.}
345 @divClass{column-left-bottom}
346 @subheading Step 2: Creating a bug report
348 If you have discovered a bug which is not listed, please help us
349 by creating a bug report.
351 @warning{We only accept bug reports in the form of @ref{Tiny
352 examples}. We have very limited resources to deal with bug
353 reports, so any non-minimal example will be rejected. Almost
354 every bug can be demonstrated in four notes or less!}
356 Here is an example of a good bug report:
359 %% the octavation command doesn't
360 %% change the output at all!
363 \paper@{ ragged-right=##t @}
373 @divClass{column-right-bottom}
374 @subheading Step 3: Sending a bug report
376 Once you have verified that the issue is not already known and
377 created a bug report, please send it to us!
379 Unfortunately there is a strict @qq{no top-posting} check on the
380 bug list, which is often incorrectly triggered by lilypond files.
381 To avoid this, please add
384 > I'm not top posting.
388 (you must include the @code{>} ) to the top of your bug report.
390 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
391 Post with the gmane lilypond.bugs interface}, or send an email to
392 @uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
394 Once your bug has been sent to the list, our Bug Meister will
395 examine the report. He may ask you for more information, or may
396 add the report to the tracker and let you know what the issue
399 You may mark the bug so that you automatically receive emails when
400 any activity on the bug occurs. This requires you have a google
406 @unnumberedsec Help us
408 @divClass{column-center-top}
413 @divClass{column-left-top}
414 @divClass{keep-bullets}
420 @divClass{column-right-top}
427 @unnumberedsec Development
429 @divClass{heading-center}
431 @heading Development for LilyPond @version
434 @heading Development for LilyPond @versionDevel
438 @warning{These are @emph{unstable development} versions. If you
439 have the slightest doubt about how to use or install LilyPond, we
440 urge you to use the stable @ref{Download}, and read the stable
445 @divClass{column-center-top}
446 @subheading Release numbers
448 There are two sets of releases for LilyPond: stable releases, and
449 unstable development releases. Stable versions have an
450 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
451 Development versions have an odd-numbered @q{minor} version number
452 (e.g., 2.7, 2.9, 2.11).
457 @divClass{column-left-top}
460 Instructions for git and compiling are in the Contributor's Guide.
463 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
466 Documentation writers and testers will generally want to download
471 @downloadDevelLinuxNormal
473 @downloadDevelLinuxBig
475 @downloadDevelLinuxPPC
477 @downloadDevelFreeBSDNormal
479 @downloadDevelFreeBSDBig
481 @downloadDevelDarwinNormal
483 @downloadDevelDarwinPPC
485 @downloadDevelWindows
494 @divClass{column-right-top}
495 @subheading Contributor's Guide
497 LilyPond development is a fairly complicated matter. In order to
498 help new contributors, and to keep the whole system (mostly)
499 stable, we have written a manual for development tasks.
501 @docLinksBare{Contributor's Guide, contributor,
502 @rcontribnamed{Top,Contributor's Guide},
503 @manualDevelContributorSplit,
504 @manualDevelContributorBig, 500 kB,
505 @manualDevelContributorPdf, 2.8 MB}
510 @divClass{column-center-top}
511 @subheading Regression tests
513 @divClass{keep-bullets}
519 @uref{../../input/regression/collated-files.html, Regression tests}:
520 This release's regtests.
521 (@uref{../../input/regression/collated-files.pdf, pdf version})
524 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
525 This release's musicXML tests.
526 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
530 @item @regtestDevel (@regtestDevelPdf{})
532 @item @regtestDevelXml (@regtestDevelXmlPdf{})
534 @item @regtestStable (@regtestStablePdf{})
536 @item @regtestStableXml (@regtestStableXmlPdf{})
540 @item @uref{http://lilypond.org/test, Archive of regression tests}:
541 Comparisons between versions.
549 @divClass{column-center-bottom}
553 @warning{These manuals are for LilyPond @version{}; the latest
554 manuals can be found at @url{http://lilypond.org}}
557 @divClass{normal-table}
558 @multitable @columnfractions .3 .3 .3
559 @headitem Introduction
561 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
563 @docLinkBig{Learning,learning,@manualDevelLearningBig}
565 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
568 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
570 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
572 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
575 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
577 @docLinkBig{Essay,essay,@manualDevelEssayBig}
579 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
584 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
586 @docLinkBig{Notation,notation,@manualDevelNotationBig}
588 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
591 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
593 @docLinkBig{Usage,usage,@manualDevelUsageBig}
595 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
598 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
600 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
602 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
607 @docLinkSplit{Web,web,@manualDevelWebSplit}
609 @docLinkBig{Web,web,@manualDevelWebBig}
611 @docLinkPdf{Web,web,@manualDevelWebPdf}
614 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
616 @docLinkBig{Changes,changes,@manualDevelChangesBig}
618 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
621 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
623 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
625 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
628 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
630 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
632 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
635 @headitem Downloadable
650 @unnumberedsec Authors
652 @help{Under construction; this is not an accurate list!}
655 @divClass{column-left-top}
656 @subheading Current Development Team
658 @divClass{keep-bullets}
663 @divClass{column-right-top}
664 @subheading Previous Development Team
666 @divClass{keep-bullets}
672 @divClass{column-center-top}
673 @subheading Current Contributors
675 @divClass{keep-bullets}
676 @subsubheading Programming
684 @subsubheading Documentation
688 @subsubheading Bug squad
692 @subsubheading Support
696 @subsubheading Translation
704 @divClass{column-center-bottom}
705 @subheading Previous Contributors
707 @divClass{keep-bullets}
708 @subsubheading Programming
716 @subsubheading Documentation
720 @c uncomment when we have any previous members -gp
721 @c @subsubheading Bug squad
725 @subsubheading Support
729 @subsubheading Translation
731 @translationsPrevious
739 @unnumberedsec Publications
741 @divClass{column-center-top}
742 @subheading What we wrote about LilyPond
744 @divClass{keep-bullets}
748 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
749 the Art of Shipping}. Forum Internacional Software Livre 2006
750 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
754 Erik Sandberg, @emph{Separating input language and formatter in
755 GNU LilyPond}. Master's Thesis, Uppsala University, Department of
756 Information Technology March 2006.
757 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
761 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
762 for automated music engraving}. Proceedings of the XIV Colloquium
763 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
764 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
772 @divClass{column-center-bottom}
774 @subheading What people did with LilyPond
776 @help{Yeah, this doesn't look bad at all... there's 20-50 papers
777 out there that cite lilypond; somebody should find at least 3 or 4
778 of them, so that it doesn't look so graham-specific.}
780 @divClass{keep-bullets}
784 Graham Percival, Tosten Anders, and George Tzanetakis,
785 @emph{Generating Targeted Rhythmic Exercises for Music Students
786 with Constraint Satisfaction Programming}, International Computer
787 Music Conference 2008.
796 @unnumberedsec Old news
798 @include web/news-front.itexi
800 @include web/news.itexi