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.
13 @divClass{column-center-top}
14 @subheading Interacting with the community
19 @ref{Contact}: get help, discuss, and keep in touch!
22 @ref{Tiny examples}: these are @emph{highly} recommended when
26 @ref{Bug reports}: something went wrong.
31 @divClass{column-left-bottom}
32 @subheading Making LilyPond better
37 @ref{Help us}: your assistance is requested.
40 @ref{Development}: for contributors and testers.
43 @ref{Authors}: the people who made LilyPond what it is today.
48 @divClass{column-right-bottom}
49 @subheading Miscellaneous
54 @ref{Publications}: what we wrote, and have had written about us.
57 @ref{Old news}: an archive.
78 @unnumberedsec Contact
81 @divClass{column-left-bottom}
82 @subheading User Discussions and Help
84 @subsubheading User mailist: @code{lilypond-user@@gnu.org}
86 This mailist is the main place for users to discuss and help each
90 @uref{http://mail.gnu.org/mailman/listinfo/lilypond-user,
91 lilypond-user subscribe and info}
93 @uref{http://mail.gnu.org/archive/html/lilypond-user/,
95 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
97 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
100 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
101 send to lilypond-user with gmane}
104 @warning{When asking questions, please use @ref{Tiny examples}!}
109 Some level of support is provided on our IRC channel,
112 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
115 This channel has no public archive, so any question that may
116 be useful for others would better be posted to one of the mailing lists.
119 @subsubheading Other languages
121 @uref{http://es.groups.yahoo.com/group/lilypond-es,
124 @uref{http://www.lilypondforum.de/,
127 @uref{http://groups.google.com/group/lilypond-brasil,
130 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
133 @uref{http://www.lilypondforum.nl/,
139 @divClass{column-right-top}
140 @subheading Stay Informed
142 @subsubheading LilyPond Report
144 The easiest way to keep touch is by reading our community
145 newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
147 @subsubheading Releases mailist: @code{info-lilypond@@gnu.org}
149 This mailist is a low-volume, read-only list which receives
150 notifications of new releases.
153 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
154 info-lilypond subscribe and info}
156 @uref{http://mail.gnu.org/archive/html/info-lilypond/,
158 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
160 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
163 @c don't include gmane posting here. -gp
170 @divClass{column-right-bottom}
171 @subheading Developer Discussion
173 @subsubheading Developer mailist: @code{lilypond-devel@@gnu.org}
175 Most developer discussion takes place on this list. Patches
179 @uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
180 lilypond-devel subscribe and info}
182 @uref{http://mail.gnu.org/archive/html/lilypond-devel/,
184 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
186 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
189 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
190 send to lilypond-devel with gmane}
194 @subsubheading Bug mailist: @code{bug-lilypond@@gnu.org}
196 Bug-specific discussion takes place here.
199 @uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
200 bug-lilypond subscribe and info}
202 @uref{http://mail.gnu.org/archive/html/bug-lilypond/,
204 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
206 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
209 @c don't include gmane posting here. -gp
212 @warning{Before sending a message to the bug list, please read our
213 guidelines for @ref{Bug reports}.}
222 @unnumberedsec Tiny examples
224 @divClass{column-center-top}
225 @subheading What are @qq{Tiny examples}?
227 A tiny example is an example from which nothing can be removed.
229 These used to be called @qq{minimal examples}.
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 2.13.3
415 @warning{These are @emph{unstable development} versions. If you
416 have the slighest 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-left-bottom}
425 @uref{http://download.linuxaudio.org/lilypond/binaries/linux-x86/lilypond-2.13.3-1.linux-x86.sh,
426 lilypond-2.13.3-1.linux-x86.sh}
428 @uref{http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.13.3-1.linux-64.sh,
429 lilypond-2.13.3-1.linux-64.sh}
431 @uref{http://download.linuxaudio.org/lilypond/binaries/linux-ppc/lilypond-2.13.3-1.linux-ppc.sh,
432 lilypond-2.13.3-1.linux-ppc.sh}
434 @uref{http://download.linuxaudio.org/lilypond/binaries/freebsd-x86/lilypond-2.13.3-1.freebsd-x86.sh,
435 lilypond-2.13.3-1.freebsd-x86.sh}
437 @uref{http://download.linuxaudio.org/lilypond/binaries/freebsd-64/lilypond-2.13.3-1.freebsd-64.sh,
438 lilypond-2.13.3-1.freebsd-64.sh}
441 http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.13.3-1.darwin-x86.tar.bz2,
442 lilypond-2.13.3-1.darwin-x86.tar.bz2}
445 http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.13.3-1.darwin-ppc.tar.bz2,
446 lilypond-2.13.3-1.darwin-ppc.tar.bz2}
449 http://download.linuxaudio.org/lilypond/binaries/mingw/lilypond-2.13.3-1.mingw.exe,
450 lilypond-2.13.3-1.mingw-exe}
484 @divClass{column-right-bottom}
485 @subheading Contributors' Guide
487 FIXME write CG intro + links.
494 @unnumberedsec Authors
498 http://lilypond.org/web/about/thanks
500 Documentation/topdocs/AUTHORS.texi
503 http://lilypond.org/web/switch/
509 @unnumberedsec Publications
511 @divClass{column-center-top}
513 @subheading What we wrote
515 @divClass{keep-bullets}
519 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
520 for automated music engraving}. Proceedings of the XIV Colloquium
521 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
522 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
525 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
526 the Art of Shipping}. Forum Internacional Software Livre 2006
527 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
531 Erik Sandberg, @emph{Separating input language and formatter in
532 GNU Lilypond}. Master's Thesis, Uppsala University, Department of
533 Information Technology March 2006.
534 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
543 @divClass{column-center-bottom}
545 @subheading What others wrote
547 @divClass{keep-bullets}
553 In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
554 articles on his personal site}, Andrew Hawryluk compares Finale
555 and LilyPond in general terms, and evaluates in detail engraving
556 capabilities of both pieces of software. The second article is an
557 instructive analysis of Rachmaninoff's Piano Prelude 6 engraving,
558 including comparisons with a reference hand-engraved edition.
563 linux journal cover Linux Journal publishes an article titled
564 @uref{http://www.linuxjournal.com/article/8364, Make Stunning
565 Schenker Graphs with GNU LilyPond}. It is a in-depth but hands-on
566 feature article with crisp LilyPond graphics. Author Kris Shaffer
567 remarks “GNU Lilypond generates beautiful graphics that make
568 commercial alternatives seem second-rate.”
573 The Belgian newspaper De Standaard investigates what drives Free
574 Software authors in an article titled
575 @uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
576 Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
577 knowlegde) in its `DS2 bijlage'. LilyPond is used as an example
578 and the article is interspersed with quotes from an `email
579 interview' with Jan Nieuwenhuizen. This marks LilyPond's first
580 appearance in mainstream printed press.
585 A French article on the LilyPond 2.6 release appeared on
586 @uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
591 The editors of Computer!Totaal, a Dutch computer magazine,
592 @uref{http://lilypond.org/web/images/computer-totaal.jpeg,
593 describe LilyPond} in the October 2004 issue as: @qq{Wonderful
594 free (open source) software [..] The sheet music produced by
595 LilyPond is exceptionally pretty [..] a very powerful system that
596 can do almost anything.}
601 Dave Phillips wrote an introductory article for Linux Journal At
602 the sounding edge: LilyPond, parts
603 @uref{http://www.linuxjournal.com/article/7657, one} and
604 @uref{http://www.linuxjournal.com/article/7719, two}.
609 Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
610 linuxmusician.com (site now defunct). This interview was also
612 @uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
618 Jazz singer Gail Selkirk writes about
619 @uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
620 Diving into LilyPond}. @qq{... you can make lead sheets or full
621 orchestral parts, and the results can be stunning.}
622 @uref{http://www.computermusic.co.uk/, Computer Music Special},
632 @unnumberedsec Old news
634 @include general/news.itexi