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
86 The main place for users to discuss and help each other is the
87 @uref{http://mail.gnu.org/mailman/listinfo/lilypond-user,
88 lilypond-user@@gnu.org} mailist. To see what this mailist is
90 @uref{http://mail.gnu.org/archive/html/lilypond-user/,
91 lilypond-user archives}.
93 You may easily post messages to the mailist with the
94 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
95 lilypond.general gmane interface}.
97 @warning{When asking questions, please use @ref{Tiny examples}!}
99 @help{we could add a "subscribe to -user" box here?}
104 Some level of support is provided on our IRC channel,
107 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
110 This channel has no public archive, so any question that may
111 be useful for others would better be posted to one of the mailing lists.
114 @subsubheading Other languages
116 @help{send mailists or forums where non-English discussion occurs.}
121 @divClass{column-right-top}
122 @subheading Stay Informed
124 @subsubheading LilyPond Report
126 The easiest way to keep touch is by reading our community
127 newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
129 @subsubheading Releases mailing list
131 @uref{http://mail.gnu.org/mailman/listinfo/info-lilypond,
132 info-lilypond@@gnu.org}
133 is a low-volume, read-only list which receives notifications of
134 new releases. To see what the mailist is like, browse the
135 @uref{http://mail.gnu.org/archive/html/info-lilypond/,
136 info-lilypond archive}.
141 @divClass{column-right-bottom}
142 @subheading Developer Discussion
144 Most developer discussion takes place on
145 @uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
146 lilypond-devel@@gnu.org}. Patches should be sent here. You can
147 browse the @uref{http://mail.gnu.org/archive/html/lilypond-devel/,
148 lilypond-devel archives}, or send a message directly with the
149 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.development,
150 lilypond.development gmane interface}.
152 Bug-specific discussion takes place on the
153 @uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
154 bug-lilypond@@gnu.org}. You can browse the
155 @uref{http://mail.gnu.org/archive/html/bug-lilypond/, bug-lilypond
158 @warning{Before sending a message to the bug list, please read our
159 guidelines for @ref{Bug reports}.}
166 @unnumberedsec Tiny examples
168 @divClass{column-center-top}
169 @subheading What are @qq{Tiny examples}?
171 A tiny example is an example from which nothing can be removed.
173 These used to be called @qq{minimal examples}.
176 @divClass{column-left-bottom}
177 @subheading Why create them?
179 @divClass{keep-bullets}
183 The simpler the example is, the quicker potential helpers can
184 understand it and help you.
187 A simple example demonstrates that you have put effort towards
188 solving the problem yourself. When people send huge portions of
189 input, it looks like they don't care how if we help them or not.
192 Creating a tiny example forces you to understand what is
193 happening. Many false problem reports can be avoided by
194 attempting to create a tiny example; if you cannot replicate a
195 @qq{bug} in a tiny example, then the problem was probably an
196 insufficient understanding of LilyPond, not an actual bug!
204 @divClass{column-right-bottom}
205 @subheading How do I create them?
207 @divClass{keep-bullets}
211 Include the \version number.
214 Make it small! Examples about spacing or page layout might
215 require many bars of music, but most issues can be reproduced
216 using only a single measure.
219 When trying to create an example, try commenting out @w{(@code{%}
220 or @code{%@{ @dots{} %@}})} sections of your file. If you can
221 comment something while still demonstrating the main idea, then
222 remove the commented-material!
225 Avoid using complicated notes, keys, or time signatures, unless
226 the bug is about the behavior of those items.
229 Do not use @code{\override} or @code{\set} commands unless the bug
230 is about those particular commands.
241 @unnumberedsec Bug reports
243 @divClass{column-center-top}
244 @subheading Step 1: Known bugs
246 If you have input that results in a crash or an erroneous output,
247 then that is a bug. There is a list of current bugs on our google
251 @uref{http://code.google.com/p/lilypond/issues/list}
254 @warning{Please @strong{DO NOT} add bug reports directly to the
255 bug tracker. Once an issue has been added to the tracker, feel
256 free to add more information to that report.}
261 @divClass{column-left-bottom}
262 @subheading Step 2: Creating a bug report
264 If you have discovered a bug which is not listed, please help us
265 by creating a bug report.
267 @warning{We only accept bug reports in the form of @ref{Tiny
268 examples}. We have very limited resources to deal with bug
269 reports, so any non-minimal example will be rejected. Almost
270 every bug can be demonstrated in four notes or less!}
272 Here is an example of a good bug report:
275 %% the octavation command doesn't
276 %% change the output at all!
279 \paper@{ ragged-right=##t @}
289 @divClass{column-right-bottom}
290 @subheading Step 3: Sending a bug report
292 Once you have verified that the issue is not already known and
293 created a bug report, please send it to us!
295 Unfortunately there is a strict @qq{no top-posting} check on the
296 bug list, which is often incorrectly triggered by lilypond files.
297 To avoid this, please add
300 > I'm not top posting.
304 (you must include the @code{>} ) to the top of your bug report.
306 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
307 Post with the gmane lilypond.bugs interface}, or send an email to
308 @uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
310 Once your bug has been sent to the list, our Bug Meister will
311 examine the report. He may ask you for more information, or may
312 add the report to the tracker and let you know what the issue
315 You may mark the bug so that you automatically receive emails when
316 any activity on the bug occurs. This requires you have a google
322 @unnumberedsec Help us
324 FIXME: before going live, rewrite this to apply to lilypond
325 generally. Right now it's (deliberately) website-specific.
327 @subheading This document
329 @subsubheading High priority / blocks release
333 - python: automatically insert latest version numbers into these
334 pages. Script already exists for the old website, but might
335 (or might not!) require tweaking.
337 - translation infrastructure.
339 @subsubheading Low priority / may never
341 - perl: web-texi2html.pl needs to be un-hacked; I did things
342 really messily. Possibly even merge/share functions with
343 the doc init.pl file?
345 - somebody to implement/work on a media=handheld CSS sheet
347 - remove the attributes from the <body> tag. In general, clean up
348 the HTML produced by texi2html
353 @unnumberedsec Development
356 @divClass{heading-center}
357 @heading Development materials for LilyPond 2.13.3
359 @warning{These are @emph{unstable development} versions. If you
360 have the slighest doubt about how to use or install LilyPond, we
361 urge you to use the stable @ref{Download}, and read the stable
366 @divClass{column-left-bottom}
369 @uref{http://download.linuxaudio.org/lilypond/binaries/linux-x86/lilypond-2.13.3-1.linux-x86.sh,
370 lilypond-2.13.3-1.linux-x86.sh}
372 @uref{http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.13.3-1.linux-64.sh,
373 lilypond-2.13.3-1.linux-64.sh}
375 @uref{http://download.linuxaudio.org/lilypond/binaries/linux-ppc/lilypond-2.13.3-1.linux-ppc.sh,
376 lilypond-2.13.3-1.linux-ppc.sh}
378 @uref{http://download.linuxaudio.org/lilypond/binaries/freebsd-x86/lilypond-2.13.3-1.freebsd-x86.sh,
379 lilypond-2.13.3-1.freebsd-x86.sh}
381 @uref{http://download.linuxaudio.org/lilypond/binaries/freebsd-64/lilypond-2.13.3-1.freebsd-64.sh,
382 lilypond-2.13.3-1.freebsd-64.sh}
385 http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.13.3-1.darwin-x86.tar.bz2,
386 lilypond-2.13.3-1.darwin-x86.tar.bz2}
389 http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.13.3-1.darwin-ppc.tar.bz2,
390 lilypond-2.13.3-1.darwin-ppc.tar.bz2}
393 http://download.linuxaudio.org/lilypond/binaries/mingw/lilypond-2.13.3-1.mingw.exe,
394 lilypond-2.13.3-1.mingw-exe}
428 @divClass{column-right-bottom}
429 @subheading Contributors' Guide
431 FIXME write CG intro + links.
438 @unnumberedsec Authors
442 http://lilypond.org/web/about/thanks
444 Documentation/topdocs/AUTHORS.texi
447 http://lilypond.org/web/switch/
453 @unnumberedsec Publications
455 @divClass{column-center-top}
457 @subheading What we wrote
459 @divClass{keep-bullets}
463 Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
464 for automated music engraving}. Proceedings of the XIV Colloquium
465 on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
466 (@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
469 Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
470 the Art of Shipping}. Forum Internacional Software Livre 2006
471 (FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
475 Erik Sandberg, @emph{Separating input language and formatter in
476 GNU Lilypond}. Master's Thesis, Uppsala University, Department of
477 Information Technology March 2006.
478 (@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
487 @divClass{column-center-bottom}
489 @subheading What others wrote
491 @divClass{keep-bullets}
497 In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
498 articles on his personal site}, Andrew Hawryluk compares Finale
499 and LilyPond in general terms, and evaluates in detail engraving
500 capabilities of both pieces of software. The second article is an
501 instructive analysis of Rachmaninoff's Piano Prelude 6 engraving,
502 including comparisons with a reference hand-engraved edition.
507 linux journal cover Linux Journal publishes an article titled
508 @uref{http://www.linuxjournal.com/article/8364, Make Stunning
509 Schenker Graphs with GNU LilyPond}. It is a in-depth but hands-on
510 feature article with crisp LilyPond graphics. Author Kris Shaffer
511 remarks “GNU Lilypond generates beautiful graphics that make
512 commercial alternatives seem second-rate.”
517 The Belgian newspaper De Standaard investigates what drives Free
518 Software authors in an article titled
519 @uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
520 Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
521 knowlegde) in its `DS2 bijlage'. LilyPond is used as an example
522 and the article is interspersed with quotes from an `email
523 interview' with Jan Nieuwenhuizen. This marks LilyPond's first
524 appearance in mainstream printed press.
529 A French article on the LilyPond 2.6 release appeared on
530 @uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
535 The editors of Computer!Totaal, a Dutch computer magazine,
536 @uref{http://lilypond.org/web/images/computer-totaal.jpeg,
537 describe LilyPond} in the October 2004 issue as: @qq{Wonderful
538 free (open source) software [..] The sheet music produced by
539 LilyPond is exceptionally pretty [..] a very powerful system that
540 can do almost anything.}
545 Dave Phillips wrote an introductory article for Linux Journal At
546 the sounding edge: LilyPond, parts
547 @uref{http://www.linuxjournal.com/article/7657, one} and
548 @uref{http://www.linuxjournal.com/article/7719, two}.
553 Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
554 linuxmusician.com (site now defunct). This interview was also
556 @uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
562 Jazz singer Gail Selkirk writes about
563 @uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
564 Diving into LilyPond}. @qq{... you can make lead sheets or full
565 orchestral parts, and the results can be stunning.}
566 @uref{http://www.computermusic.co.uk/, Computer Music Special},
576 @unnumberedsec Old news
578 @include general/news.itexi