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. See TRANSLATION for details.
9 @include general/basic-authors.itexi
15 @divClass{column-center-top}
16 @subheading Interacting with the community
21 @ref{contact}: get help, discuss, and keep in touch!
24 @ref{tiny examples}: these are @emph{highly} recommended when
28 @ref{bug reports}: something went wrong.
33 @divClass{column-left-bottom}
34 @subheading Making LilyPond better
39 @ref{help us}: your assistance is requested.
42 @ref{development}: for contributors and testers.
45 @ref{authors}: the people who made LilyPond what it is today.
50 @divClass{column-right-bottom}
51 @subheading Miscellaneous
56 @ref{publications}: what we wrote, and have had written about us.
59 @ref{old news}: an archive.
80 @unnumberedsec Contact
83 @divClass{column-left-bottom}
84 @subheading User Discussions and Help
86 @subsubheading User mailing list: @code{lilypond-user@@gnu.org}
88 This mailing list is the main place for users to discuss and help
92 @uref{http://mail.gnu.org/mailman/listinfo/lilypond-user,
93 lilypond-user subscribe and info}
95 @uref{http://mail.gnu.org/archive/html/lilypond-user/,
97 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
99 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
102 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
103 send to lilypond-user with gmane}
106 @warning{When asking questions, please use @ref{tiny examples}!}
111 Some level of support is provided on our IRC channel,
114 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
117 This channel has no public archive, so any question that may
118 be useful for others would better be posted to one of the mailing lists.
121 <form action="http://webchat.freenode.net"
125 <input name="nick" type="text" size="15" value="">
127 <input name="channels" type="hidden" value="lilypond">
128 <input type="submit" value="Join #lilypond IRC Chat">
131 <script language="JavaScript" type="text/javascript">
132 var username = "web";
133 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
134 : window.navigator.language;
135 username += '-' + lang.substr(0, 2);
136 username += '-' + navigator.appName.substr(0, 2);
137 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
138 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
139 document.forms["f_lily_irc"].nick.value = username;
143 @subsubheading Other languages
146 @uref{http://es.groups.yahoo.com/group/lilypond-es,
149 @uref{http://www.lilypondforum.de/,
152 @uref{http://groups.google.com/group/lilypond-brasil,
155 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
158 @uref{http://www.lilypondforum.nl/,
165 @divClass{column-right-top}
166 @subheading Stay Informed
168 @subsubheading LilyPond Report
170 The easiest way to keep touch is by reading our community
171 newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
173 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
175 This mailing list is a low-volume, read-only list which receives
176 notifications of new releases.
179 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
180 info-lilypond subscribe and info}
182 @uref{http://mail.gnu.org/archive/html/info-lilypond/,
184 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
186 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
189 @c don't include gmane posting here. -gp
196 @divClass{column-right-bottom}
197 @subheading Developer Discussion
199 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
201 Most developer discussion takes place on this list. Patches
205 @uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
206 lilypond-devel subscribe and info}
208 @uref{http://mail.gnu.org/archive/html/lilypond-devel/,
210 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
212 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
215 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
216 send to lilypond-devel with gmane}
220 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
222 Bug-specific discussion takes place here.
225 @uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
226 bug-lilypond subscribe and info}
228 @uref{http://mail.gnu.org/archive/html/bug-lilypond/,
230 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
232 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
235 @c don't include gmane posting here. -gp
238 @warning{Before sending a message to the bug list, please read our
239 guidelines for @ref{bug reports}.}
246 @unnumberedsec Tiny examples
248 @divClass{column-center-top}
249 @subheading What are @qq{Tiny examples}?
251 A tiny example is an example from which nothing can be removed.
254 @divClass{column-left-bottom}
255 @subheading Why create them?
257 @divClass{keep-bullets}
261 The simpler the example is, the quicker potential helpers can
262 understand it and help you.
265 A simple example demonstrates that you have put effort towards
266 solving the problem yourself. When people send huge portions of
267 input, it looks like they don't care how if we help them or not.
270 Creating a tiny example forces you to understand what is
271 happening. Many false problem reports can be avoided by
272 attempting to create a tiny example; if you cannot replicate a
273 @qq{bug} in a tiny example, then the problem was probably an
274 insufficient understanding of LilyPond, not an actual bug!
282 @divClass{column-right-bottom}
283 @subheading How do I create them?
285 @divClass{keep-bullets}
289 Include the \version number.
292 Make it small! Examples about spacing or page layout might
293 require many bars of music, but most issues can be reproduced
294 using only a single measure.
297 When trying to create an example, try commenting out @w{(@code{%}
298 or @code{%@{ @dots{} %@}})} sections of your file. If you can
299 comment something while still demonstrating the main idea, then
300 remove the commented-material!
303 Avoid using complicated notes, keys, or time signatures, unless
304 the bug is about the behavior of those items.
307 Do not use @code{\override} or @code{\set} commands unless the bug
308 is about those particular commands.
319 @unnumberedsec Bug reports
321 @divClass{column-center-top}
322 @subheading Step 1: Known bugs
324 If you have input that results in a crash or an erroneous output,
325 then that is a bug. There is a list of current bugs on our google
329 @uref{http://code.google.com/p/lilypond/issues/list}
332 @warning{Please @strong{DO NOT} add bug reports directly to the
333 bug tracker. Once an issue has been added to the tracker, feel
334 free to add more information to that report.}
339 @divClass{column-left-bottom}
340 @subheading Step 2: Creating a bug report
342 If you have discovered a bug which is not listed, please help us
343 by creating a bug report.
345 @warning{We only accept bug reports in the form of
346 @ref{tiny examples}. We have very limited resources to deal with
347 bug reports, so any non-minimal example will be rejected. Almost
348 every bug can be demonstrated in four notes or less!}
350 Here is an example of a good bug report:
353 %% the octavation command doesn't
354 %% change the output at all!
357 \paper@{ ragged-right=##t @}
367 @divClass{column-right-bottom}
368 @subheading Step 3: Sending a bug report
370 Once you have verified that the issue is not already known and
371 created a bug report, please send it to us!
373 Unfortunately there is a strict @qq{no top-posting} check on the
374 bug list, which is often incorrectly triggered by lilypond files.
375 To avoid this, please add
378 > I'm not top posting.
382 (you must include the @code{>} ) to the top of your bug report.
384 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
385 Post with the gmane lilypond.bugs interface}, or send an email to
386 @uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
388 Once your bug has been sent to the list, our Bug Meister will
389 examine the report. He may ask you for more information, or may
390 add the report to the tracker and let you know what the issue
393 You may mark the bug so that you automatically receive emails when
394 any activity on the bug occurs. This requires you have a google
400 @unnumberedsec Help us
402 TODO: talk about the Frogs, document suggestions, encourage getting
403 involved, etc. Maybe mention GLISS and GOP, if those are happening
406 frog mailist: @uref{http://frogs.lily.net}
410 @unnumberedsec Development
413 @divClass{heading-center}
414 @heading Development materials for LilyPond @versionDevel{}
416 @warning{These are @emph{unstable development} versions. If you
417 have the slightest doubt about how to use or install LilyPond, we
418 urge you to use the stable @ref{download}, and read the stable
423 @divClass{column-center-top}
424 @subheading Release numbers
426 There are two sets of releases for LilyPond: stable releases, and
427 unstable development releases. Stable versions have an
428 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
429 Development versions have an odd-numbered @q{minor} version number
430 (e.g., 2.7, 2.9, 2.11).
435 @divClass{column-left-bottom}
438 Instructions for git and compiling are in the Contributor's Guide.
441 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
444 Documentation writers and testers will generally want to download
449 @downloadDevelLinuxNormal
451 @downloadDevelLinuxBig
453 @downloadDevelLinuxPPC
455 @downloadDevelFreeBSDNormal
457 @downloadDevelFreeBSDBig
459 @downloadDevelDarwinNormal
461 @downloadDevelDarwinPPC
463 @downloadDevelWindows
472 @help {these need the automatic symlinks or something. Maybe even
473 a hard-coded url to lilypond.org/docs/2.13 or something??}
477 @uref{lm-big-html, big html}
482 @uref{mg-big-html, big html}
486 @uref{essay-html, html}
487 @uref{essay-big-html, big html}
488 @uref{essay-pdf, pdf}
491 @uref{notation-html, html}
492 @uref{notation-big-html, big html}
493 @uref{notation-pdf, pdf}
496 @uref{usage-html, html}
497 @uref{usage-big-html, big html}
498 @uref{usage-pdf, pdf}
501 @uref{snippets-html, html}
502 @uref{snippets-big-html, big html}
503 @uref{snippets-pdf, pdf}
506 @uref{changes-html, html}
507 @uref{changes-big-html, big html}
508 @uref{changes-pdf, pdf}
511 @uref{internals-html, html}
512 @uref{internals-big-html, big html}
513 @uref{internals-pdf, pdf}
518 @divClass{column-right-top}
519 @subheading Contributors' Guide
521 LilyPond development is a fairly complicated matter. LilyPond is
522 a large, (mostly) stable project. At any point in time, we have
523 between 5 and 25 active contributors. In order to help new
524 contributors, and to keep the whole system (mostly) stable, we
525 have written a manual for contributors.
527 @divClass{keep-bullets}
530 @item @uref{../contributor/index.html, Contributor's guide (split HTML)}:
531 the manual is split between many HTML pages.
532 @emph{(small download for each page)}
534 @item @uref{../contributor-big-page.html, Contributor's guide (big HTML)}:
535 read this manual as one huge HTML page.
536 @emph{(large single download, around 10? Mb)}
538 @item @uref{../contributor.pdf, contributor.pdf}:
539 download as a PDF file.
540 @emph{(large single download, 2.8 Mb)}
542 @c @item @uref{TODO, contributor.info}:
543 @c GNU info format for documentation. TODO, link broken.
549 @divClass{column-right-bottom}
550 @subheading Regression tests
552 @divClass{keep-bullets}
555 @item @uref{../../input/regression/collated-files.html, Regression tests}:
556 This releases' tests. (also in
557 @uref{../input/regression/collated-files.pdf, pdf})
559 @item @uref{../../input/regression/musicxml/collated-files.html,
560 MusicXML Regression tests}:
561 This releases' MusicXML tests. (also in
562 @uref{../input/regression/musicxml/collated-files.pdf, pdf})
564 @item @uref{http://lilypond.org/test, Archive of regression tests}:
565 Comparisons beteween versions.
572 @unnumberedsec Authors
574 @help{Under construction; this is not an accurate list!}
578 http://lilypond.org/web/about/thanks
580 Documentation/topdocs/AUTHORS.texi
583 http://lilypond.org/web/switch/
586 @divClass{column-left-top}
587 @subheading Current Development Team
589 @divClass{keep-bullets}
594 @divClass{column-right-top}
595 @subheading Previous Development Team Positions
597 @divClass{keep-bullets}
603 @divClass{column-center-bottom}
604 @subheading Programming contributors
606 @divClass{keep-bullets}
609 @subheading Font contributors
613 @subheading Documentation contributors
617 @subheading Support contributors
621 @subheading Translation contributors
623 @contributorsTranslations
631 @unnumberedsec Publications
633 @divClass{column-center-top}
634 @subheading What we wrote
636 @divClass{keep-bullets}
640 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
641 the Art of Shipping}. Forum Internacional Software Livre 2006
642 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
646 Erik Sandberg, @emph{Separating input language and formatter in
647 GNU Lilypond}. Master's Thesis, Uppsala University, Department of
648 Information Technology March 2006.
649 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
653 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
654 for automated music engraving}. Proceedings of the XIV Colloquium
655 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
656 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
664 @divClass{column-center-bottom}
666 @subheading What others wrote
668 @divClass{keep-bullets}
674 The German LinuxUser magazine wrote an
675 @uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
676 article about lilypond}.
682 In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
683 articles on his personal site}, Andrew Hawryluk compares Finale
684 and LilyPond in general terms, and evaluates in detail engraving
685 capabilities of both pieces of software. The second article is an
686 instructive analysis of Rachmaninoff's Piano Prelude 6 engraving,
687 including comparisons with a reference hand-engraved edition.
692 Linux journal cover Linux Journal publishes an article titled
693 @uref{http://www.linuxjournal.com/article/8364, Make Stunning
694 Schenker Graphs with GNU LilyPond}. It is a in-depth but hands-on
695 feature article with crisp LilyPond graphics. Author Kris Shaffer
696 remarks “GNU Lilypond generates beautiful graphics that make
697 commercial alternatives seem second-rate.”
702 The Belgian newspaper De Standaard investigates what drives Free
703 Software authors in an article titled
704 @uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
705 Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
706 knowlegde) in its `DS2 bijlage'. LilyPond is used as an example
707 and the article is interspersed with quotes from an `email
708 interview' with Jan Nieuwenhuizen. This marks LilyPond's first
709 appearance in mainstream printed press.
714 A French article on the LilyPond 2.6 release appeared on
715 @uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
720 The editors of Computer!Totaal, a Dutch computer magazine,
721 @uref{http://lilypond.org/web/images/computer-totaal.jpeg,
722 describe LilyPond} in the October 2004 issue as: @qq{Wonderful
723 free (open source) software [..] The sheet music produced by
724 LilyPond is exceptionally pretty [..] a very powerful system that
725 can do almost anything.}
730 Dave Phillips wrote an introductory article for Linux Journal At
731 the sounding edge: LilyPond, parts
732 @uref{http://www.linuxjournal.com/article/7657, one} and
733 @uref{http://www.linuxjournal.com/article/7719, two}.
738 Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
739 linuxmusician.com (site now defunct). This interview was also
741 @uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
747 Jazz singer Gail Selkirk writes about
748 @uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
749 Diving into LilyPond}. @qq{... you can make lead sheets or full
750 orchestral parts, and the results can be stunning.}
751 @uref{http://www.computermusic.co.uk/, Computer Music Special},
761 @unnumberedsec Old news
763 @include general/news.itexi