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 @ref{Tiny
324 examples}. We have very limited resources to deal with bug
325 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 FIXME: before going live, rewrite this to apply to lilypond
381 generally. Right now it's (deliberately) website-specific.
383 @subheading This document
385 @subsubheading High priority / blocks release
389 - python: automatically insert latest version numbers into these
390 pages. Script already exists for the old website, but might
391 (or might not!) require tweaking.
393 - translation infrastructure.
395 @subsubheading Low priority / may never
397 - perl: web-texi2html.pl needs to be un-hacked; I did things
398 really messily. Possibly even merge/share functions with
399 the doc init.pl file?
401 - somebody to implement/work on a media=handheld CSS sheet
403 - remove the attributes from the <body> tag. In general, clean up
404 the HTML produced by texi2html
409 @unnumberedsec Development
412 @divClass{heading-center}
413 @heading Development materials for LilyPond @versionDevel{}
415 @warning{These are @emph{unstable development} versions. If you
416 have the slightest doubt about how to use or install LilyPond, we
417 urge you to use the stable @ref{Download}, and read the stable
422 @divClass{column-center-top}
423 @subheading Release numbers
425 There are two sets of releases for LilyPond: stable releases, and
426 unstable development releases. Stable versions have an
427 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
428 Development versions have an odd-numbered @q{minor} version number
429 (e.g., 2.7, 2.9, 2.11).
434 @divClass{column-left-bottom}
437 Instructions for git and compiling are in the Contributor's Guide.
440 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
443 Documentation writers and testers will generally want to download
446 @downloadDevelLinuxNormal
448 @downloadDevelLinuxBig
450 @downloadDevelLinuxPPC
452 @downloadDevelFreeBSDNormal
454 @downloadDevelFreeBSDBig
456 @downloadDevelDarwinNormal
458 @downloadDevelDarwinPPC
460 @downloadDevelWindows
465 FIXME: these need the automatic symlinks or something. Maybe even
466 a hard-coded url to lilypond.org/docs/2.13 or something??
470 @uref{lm-big-html, big html}
475 @uref{mg-big-html, big html}
479 @uref{essay-html, html}
480 @uref{essay-big-html, big html}
481 @uref{essay-pdf, pdf}
484 @uref{notation-html, html}
485 @uref{notation-big-html, big html}
486 @uref{notation-pdf, pdf}
489 @uref{usage-html, html}
490 @uref{usage-big-html, big html}
491 @uref{usage-pdf, pdf}
494 @uref{snippets-html, html}
495 @uref{snippets-big-html, big html}
496 @uref{snippets-pdf, pdf}
499 @uref{changes-html, html}
500 @uref{changes-big-html, big html}
501 @uref{changes-pdf, pdf}
504 @uref{internals-html, html}
505 @uref{internals-big-html, big html}
506 @uref{internals-pdf, pdf}
511 @divClass{column-right-top}
512 @subheading Contributors' Guide
514 LilyPond development is a fairly complicated matter. LilyPond is
515 a large, (mostly) stable project. At any point in time, we have
516 between 5 and 25 active contributors. In order to help new
517 contributors, and to keep the whole system (mostly) stable, we
518 have written a manual for contributors.
520 @divClass{keep-bullets}
523 @item @uref{contributor/index.html, Contributor's guide (split HTML)}:
524 the manual is split between many HTML pages.
525 @emph{(small download for each page)}
527 @item @uref{contributor-big-page.html, Contributor's guide (big HTML)}:
528 read this manual as one huge HTML page.
529 @emph{(large single download, around 10? Mb)}
531 @item @uref{contributor.pdf, contributor.pdf}:
532 download as a PDF file.
533 @emph{(large single download, 2.8 Mb)}
535 @item @uref{FIXME, contributor.info}:
536 GNU info format for documentation. FIXME, link broken.
542 @divClass{column-right-bottom}
543 @subheading Regression tests
545 @divClass{keep-bullets}
548 @item @uref{../input/regression/collated-files.html, Regression tests}:
549 This releases' tests. (also in
550 @uref{../input/regression/collated-files.pdf, pdf})
552 @item @uref{../input/regression/musicxml/collated-files.html,
553 MusicXML Regression tests}:
554 This releases' MusicXML tests. (also in
555 @uref{../input/regression/musicxml/collated-files.pdf, pdf})
557 @item @uref{http://lilypond.org/test, Archive of regression tests}:
558 Comparisons beteween versions.
565 @unnumberedsec Authors
567 @help{Under construction; this is not an accurate list!}
571 http://lilypond.org/web/about/thanks
573 Documentation/topdocs/AUTHORS.texi
576 http://lilypond.org/web/switch/
579 @divClass{column-left-top}
580 @subheading Current Development Team
582 @divClass{keep-bullets}
587 @divClass{column-right-top}
588 @subheading Previous Development Team Positions
590 @divClass{keep-bullets}
596 @divClass{column-center-bottom}
597 @subheading Programming contributors
599 @divClass{keep-bullets}
602 @subheading Font contributors
606 @subheading Documentation contributors
610 @subheading Support contributors
614 @subheading Translation contributors
616 @contributorsTranslations
624 @unnumberedsec Publications
626 @divClass{column-center-top}
627 @subheading What we wrote
629 @divClass{keep-bullets}
633 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
634 for automated music engraving}. Proceedings of the XIV Colloquium
635 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
636 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
639 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
640 the Art of Shipping}. Forum Internacional Software Livre 2006
641 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
645 Erik Sandberg, @emph{Separating input language and formatter in
646 GNU Lilypond}. Master's Thesis, Uppsala University, Department of
647 Information Technology March 2006.
648 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
657 @divClass{column-center-bottom}
659 @subheading What others wrote
661 @divClass{keep-bullets}
667 The German LinuxUser magazine wrote an
668 @uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
669 article about lilypond}.
675 In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
676 articles on his personal site}, Andrew Hawryluk compares Finale
677 and LilyPond in general terms, and evaluates in detail engraving
678 capabilities of both pieces of software. The second article is an
679 instructive analysis of Rachmaninoff's Piano Prelude 6 engraving,
680 including comparisons with a reference hand-engraved edition.
685 Linux journal cover Linux Journal publishes an article titled
686 @uref{http://www.linuxjournal.com/article/8364, Make Stunning
687 Schenker Graphs with GNU LilyPond}. It is a in-depth but hands-on
688 feature article with crisp LilyPond graphics. Author Kris Shaffer
689 remarks “GNU Lilypond generates beautiful graphics that make
690 commercial alternatives seem second-rate.”
695 The Belgian newspaper De Standaard investigates what drives Free
696 Software authors in an article titled
697 @uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
698 Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
699 knowlegde) in its `DS2 bijlage'. LilyPond is used as an example
700 and the article is interspersed with quotes from an `email
701 interview' with Jan Nieuwenhuizen. This marks LilyPond's first
702 appearance in mainstream printed press.
707 A French article on the LilyPond 2.6 release appeared on
708 @uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
713 The editors of Computer!Totaal, a Dutch computer magazine,
714 @uref{http://lilypond.org/web/images/computer-totaal.jpeg,
715 describe LilyPond} in the October 2004 issue as: @qq{Wonderful
716 free (open source) software [..] The sheet music produced by
717 LilyPond is exceptionally pretty [..] a very powerful system that
718 can do almost anything.}
723 Dave Phillips wrote an introductory article for Linux Journal At
724 the sounding edge: LilyPond, parts
725 @uref{http://www.linuxjournal.com/article/7657, one} and
726 @uref{http://www.linuxjournal.com/article/7719, two}.
731 Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
732 linuxmusician.com (site now defunct). This interview was also
734 @uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
740 Jazz singer Gail Selkirk writes about
741 @uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
742 Diving into LilyPond}. @qq{... you can make lead sheets or full
743 orchestral parts, and the results can be stunning.}
744 @uref{http://www.computermusic.co.uk/, Computer Music Special},
754 @unnumberedsec Old news
756 @include general/news.itexi