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 @subsubheading Other languages
124 @uref{http://es.groups.yahoo.com/group/lilypond-es,
127 @uref{http://www.lilypondforum.de/,
130 @uref{http://groups.google.com/group/lilypond-brasil,
133 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
136 @uref{http://www.lilypondforum.nl/,
143 @divClass{column-right-top}
144 @subheading Stay Informed
146 @subsubheading LilyPond Report
148 The easiest way to keep touch is by reading our community
149 newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
151 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
153 This mailing list is a low-volume, read-only list which receives
154 notifications of new releases.
157 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
158 info-lilypond subscribe and info}
160 @uref{http://mail.gnu.org/archive/html/info-lilypond/,
162 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
164 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
167 @c don't include gmane posting here. -gp
174 @divClass{column-right-bottom}
175 @subheading Developer Discussion
177 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
179 Most developer discussion takes place on this list. Patches
183 @uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
184 lilypond-devel subscribe and info}
186 @uref{http://mail.gnu.org/archive/html/lilypond-devel/,
188 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
190 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
193 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
194 send to lilypond-devel with gmane}
198 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
200 Bug-specific discussion takes place here.
203 @uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
204 bug-lilypond subscribe and info}
206 @uref{http://mail.gnu.org/archive/html/bug-lilypond/,
208 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
210 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
213 @c don't include gmane posting here. -gp
216 @warning{Before sending a message to the bug list, please read our
217 guidelines for @ref{bug reports}.}
224 @unnumberedsec Tiny examples
226 @divClass{column-center-top}
227 @subheading What are @qq{Tiny examples}?
229 A tiny example is an example from which nothing can be removed.
232 @divClass{column-left-bottom}
233 @subheading Why create them?
235 @divClass{keep-bullets}
239 The simpler the example is, the quicker potential helpers can
240 understand it and help you.
243 A simple example demonstrates that you have put effort towards
244 solving the problem yourself. When people send huge portions of
245 input, it looks like they don't care how if we help them or not.
248 Creating a tiny example forces you to understand what is
249 happening. Many false problem reports can be avoided by
250 attempting to create a tiny example; if you cannot replicate a
251 @qq{bug} in a tiny example, then the problem was probably an
252 insufficient understanding of LilyPond, not an actual bug!
260 @divClass{column-right-bottom}
261 @subheading How do I create them?
263 @divClass{keep-bullets}
267 Include the \version number.
270 Make it small! Examples about spacing or page layout might
271 require many bars of music, but most issues can be reproduced
272 using only a single measure.
275 When trying to create an example, try commenting out @w{(@code{%}
276 or @code{%@{ @dots{} %@}})} sections of your file. If you can
277 comment something while still demonstrating the main idea, then
278 remove the commented-material!
281 Avoid using complicated notes, keys, or time signatures, unless
282 the bug is about the behavior of those items.
285 Do not use @code{\override} or @code{\set} commands unless the bug
286 is about those particular commands.
297 @unnumberedsec Bug reports
299 @divClass{column-center-top}
300 @subheading Step 1: Known bugs
302 If you have input that results in a crash or an erroneous output,
303 then that is a bug. There is a list of current bugs on our google
307 @uref{http://code.google.com/p/lilypond/issues/list}
310 @warning{Please @strong{DO NOT} add bug reports directly to the
311 bug tracker. Once an issue has been added to the tracker, feel
312 free to add more information to that report.}
317 @divClass{column-left-bottom}
318 @subheading Step 2: Creating a bug report
320 If you have discovered a bug which is not listed, please help us
321 by creating a bug report.
323 @warning{We only accept bug reports in the form of
324 @ref{tiny examples}. We have very limited resources to deal with
325 bug reports, so any non-minimal example will be rejected. Almost
326 every bug can be demonstrated in four notes or less!}
328 Here is an example of a good bug report:
331 %% the octavation command doesn't
332 %% change the output at all!
335 \paper@{ ragged-right=##t @}
345 @divClass{column-right-bottom}
346 @subheading Step 3: Sending a bug report
348 Once you have verified that the issue is not already known and
349 created a bug report, please send it to us!
351 Unfortunately there is a strict @qq{no top-posting} check on the
352 bug list, which is often incorrectly triggered by lilypond files.
353 To avoid this, please add
356 > I'm not top posting.
360 (you must include the @code{>} ) to the top of your bug report.
362 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
363 Post with the gmane lilypond.bugs interface}, or send an email to
364 @uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
366 Once your bug has been sent to the list, our Bug Meister will
367 examine the report. He may ask you for more information, or may
368 add the report to the tracker and let you know what the issue
371 You may mark the bug so that you automatically receive emails when
372 any activity on the bug occurs. This requires you have a google
378 @unnumberedsec Help us
380 TODO: talk about the Frogs, document suggestions, encourage getting
381 involved, etc. Maybe mention GLISS and GOP, if those are happening
386 @unnumberedsec Development
389 @divClass{heading-center}
390 @heading Development materials for LilyPond @versionDevel{}
392 @warning{These are @emph{unstable development} versions. If you
393 have the slightest doubt about how to use or install LilyPond, we
394 urge you to use the stable @ref{download}, and read the stable
399 @divClass{column-center-top}
400 @subheading Release numbers
402 There are two sets of releases for LilyPond: stable releases, and
403 unstable development releases. Stable versions have an
404 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
405 Development versions have an odd-numbered @q{minor} version number
406 (e.g., 2.7, 2.9, 2.11).
411 @divClass{column-left-bottom}
414 Instructions for git and compiling are in the Contributor's Guide.
417 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
420 Documentation writers and testers will generally want to download
425 @downloadDevelLinuxNormal
427 @downloadDevelLinuxBig
429 @downloadDevelLinuxPPC
431 @downloadDevelFreeBSDNormal
433 @downloadDevelFreeBSDBig
435 @downloadDevelDarwinNormal
437 @downloadDevelDarwinPPC
439 @downloadDevelWindows
448 @help these need the automatic symlinks or something. Maybe even
449 a hard-coded url to lilypond.org/docs/2.13 or something??
453 @uref{lm-big-html, big html}
458 @uref{mg-big-html, big html}
462 @uref{essay-html, html}
463 @uref{essay-big-html, big html}
464 @uref{essay-pdf, pdf}
467 @uref{notation-html, html}
468 @uref{notation-big-html, big html}
469 @uref{notation-pdf, pdf}
472 @uref{usage-html, html}
473 @uref{usage-big-html, big html}
474 @uref{usage-pdf, pdf}
477 @uref{snippets-html, html}
478 @uref{snippets-big-html, big html}
479 @uref{snippets-pdf, pdf}
482 @uref{changes-html, html}
483 @uref{changes-big-html, big html}
484 @uref{changes-pdf, pdf}
487 @uref{internals-html, html}
488 @uref{internals-big-html, big html}
489 @uref{internals-pdf, pdf}
494 @divClass{column-right-top}
495 @subheading Contributors' Guide
497 LilyPond development is a fairly complicated matter. LilyPond is
498 a large, (mostly) stable project. At any point in time, we have
499 between 5 and 25 active contributors. In order to help new
500 contributors, and to keep the whole system (mostly) stable, we
501 have written a manual for contributors.
503 @divClass{keep-bullets}
506 @item @uref{contributor/index.html, Contributor's guide (split HTML)}:
507 the manual is split between many HTML pages.
508 @emph{(small download for each page)}
510 @item @uref{contributor-big-page.html, Contributor's guide (big HTML)}:
511 read this manual as one huge HTML page.
512 @emph{(large single download, around 10? Mb)}
514 @item @uref{contributor.pdf, contributor.pdf}:
515 download as a PDF file.
516 @emph{(large single download, 2.8 Mb)}
518 @c @item @uref{TODO, contributor.info}:
519 @c GNU info format for documentation. TODO, link broken.
525 @divClass{column-right-bottom}
526 @subheading Regression tests
528 @divClass{keep-bullets}
531 @c add an extra ../ to counteract the sed hack in the makefile
532 @item @uref{../../input/regression/collated-files.html, Regression tests}:
533 This releases' tests. (also in
534 @uref{../input/regression/collated-files.pdf, pdf})
536 @c add an extra ../ to counteract the sed hack in the makefile
537 @item @uref{../../input/regression/musicxml/collated-files.html,
538 MusicXML Regression tests}:
539 This releases' MusicXML tests. (also in
540 @uref{../input/regression/musicxml/collated-files.pdf, pdf})
542 @item @uref{http://lilypond.org/test, Archive of regression tests}:
543 Comparisons beteween versions.
550 @unnumberedsec Authors
552 @help{Under construction; this is not an accurate list!}
556 http://lilypond.org/web/about/thanks
558 Documentation/topdocs/AUTHORS.texi
561 http://lilypond.org/web/switch/
564 @divClass{column-left-top}
565 @subheading Current Development Team
567 @divClass{keep-bullets}
572 @divClass{column-right-top}
573 @subheading Previous Development Team Positions
575 @divClass{keep-bullets}
581 @divClass{column-center-bottom}
582 @subheading Programming contributors
584 @divClass{keep-bullets}
587 @subheading Font contributors
591 @subheading Documentation contributors
595 @subheading Support contributors
599 @subheading Translation contributors
601 @contributorsTranslations
609 @unnumberedsec Publications
611 @divClass{column-center-top}
612 @subheading What we wrote
614 @divClass{keep-bullets}
618 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
619 the Art of Shipping}. Forum Internacional Software Livre 2006
620 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
624 Erik Sandberg, @emph{Separating input language and formatter in
625 GNU Lilypond}. Master's Thesis, Uppsala University, Department of
626 Information Technology March 2006.
627 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
631 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
632 for automated music engraving}. Proceedings of the XIV Colloquium
633 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
634 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
642 @divClass{column-center-bottom}
644 @subheading What others wrote
646 @divClass{keep-bullets}
652 The German LinuxUser magazine wrote an
653 @uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
654 article about lilypond}.
660 In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
661 articles on his personal site}, Andrew Hawryluk compares Finale
662 and LilyPond in general terms, and evaluates in detail engraving
663 capabilities of both pieces of software. The second article is an
664 instructive analysis of Rachmaninoff's Piano Prelude 6 engraving,
665 including comparisons with a reference hand-engraved edition.
670 Linux journal cover Linux Journal publishes an article titled
671 @uref{http://www.linuxjournal.com/article/8364, Make Stunning
672 Schenker Graphs with GNU LilyPond}. It is a in-depth but hands-on
673 feature article with crisp LilyPond graphics. Author Kris Shaffer
674 remarks “GNU Lilypond generates beautiful graphics that make
675 commercial alternatives seem second-rate.”
680 The Belgian newspaper De Standaard investigates what drives Free
681 Software authors in an article titled
682 @uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
683 Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
684 knowlegde) in its `DS2 bijlage'. LilyPond is used as an example
685 and the article is interspersed with quotes from an `email
686 interview' with Jan Nieuwenhuizen. This marks LilyPond's first
687 appearance in mainstream printed press.
692 A French article on the LilyPond 2.6 release appeared on
693 @uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
698 The editors of Computer!Totaal, a Dutch computer magazine,
699 @uref{http://lilypond.org/web/images/computer-totaal.jpeg,
700 describe LilyPond} in the October 2004 issue as: @qq{Wonderful
701 free (open source) software [..] The sheet music produced by
702 LilyPond is exceptionally pretty [..] a very powerful system that
703 can do almost anything.}
708 Dave Phillips wrote an introductory article for Linux Journal At
709 the sounding edge: LilyPond, parts
710 @uref{http://www.linuxjournal.com/article/7657, one} and
711 @uref{http://www.linuxjournal.com/article/7719, two}.
716 Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
717 linuxmusician.com (site now defunct). This interview was also
719 @uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
725 Jazz singer Gail Selkirk writes about
726 @uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
727 Diving into LilyPond}. @qq{... you can make lead sheets or full
728 orchestral parts, and the results can be stunning.}
729 @uref{http://www.computermusic.co.uk/, Computer Music Special},
739 @unnumberedsec Old news
741 @include general/news.itexi