Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
+ version that you are working on. For details, see the Contributors'
+ Guide, node Updating translation committishes..
@end ignore
-@include web/basic-authors.itexi
+@include included/authors.itexi
+@include included/helpus.itexi
-@node community
+@node Community
@unnumbered Community
+@divClass{link-headings}
@divClass{column-center-top}
@subheading Interacting with the community
@itemize
@item
-@ref{contact}: get help, discuss, and keep in touch!
+@ref{Contact}: get help, discuss, and keep in touch!
@item
-@ref{tiny examples}: these are @emph{highly} recommended when
+@ref{Tiny examples}: these are @emph{highly} recommended when
discussing LilyPond.
@item
-@ref{bug reports}: something went wrong.
+@ref{Bug reports}: something went wrong.
@end itemize
@divEnd
@itemize
@item
-@ref{help us}: your assistance is requested.
+@ref{Help us}: your assistance is requested.
@item
-@ref{development}: for contributors and testers.
+@ref{Development}: for contributors and testers.
@item
-@ref{authors}: the people who made LilyPond what it is today.
+@ref{Authors}: the people who made LilyPond what it is today.
@end itemize
@divEnd
@itemize
@item
-@ref{publications}: what we wrote, and have had written about us.
+@ref{Publications}: what we wrote, and have had written about us.
@item
-@ref{old news}: an archive.
+@ref{Old news}: an archive.
@end itemize
@divEnd
+@divEnd
@divClass{hide}
@menu
-* contact::
-* tiny examples::
-* bug reports::
-* help us::
-* development::
-* authors::
-* publications::
-* old news::
+* Contact::
+* Tiny examples::
+* Bug reports::
+* Help us::
+* Development::
+* Authors::
+* Publications::
+* Old news::
@end menu
@divEnd
-@node contact
+@node Contact
@unnumberedsec Contact
each other.
@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/lilypond-user,
+@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
lilypond-user subscribe and info}
-@uref{http://mail.gnu.org/archive/html/lilypond-user/,
+@uref{http://lists.gnu.org/archive/html/lilypond-user/,
user archive1}
@uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
archive2}
send to lilypond-user with gmane}
@end quotation
-@warning{When asking questions, please use @ref{tiny examples}!}
+@warning{When asking questions, please use @ref{Tiny examples}!}
+
+@subsubheading LilyPond Snippet Repository
+
+The LilyPond Snippet Repository is a large collection of
+user-submitted examples, which can freely be copied and used
+in your own works. See what other people have written,
+and add your own!
+
+@example
+@uref{http://lsr.dsi.unimi.it}
+@end example
+
+Particularly instructive examples from LSR are included in our
+official documentation, in @ref{Snippets}.
@subsubheading IRC
@end example
This channel has no public archive, so any question that may
-be useful for others would better be posted to one of the mailing lists.
+be useful for others would better be posted to one of the mailing lists.
@html
<form action="http://webchat.freenode.net"
@subsubheading Other languages
@quotation
-@uref{http://es.groups.yahoo.com/group/lilypond-es,
-Spanish yahoo group}
+@uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
+Spanish mailing list}
@uref{http://www.lilypondforum.de/,
German forum}
@uref{http://groups.google.com/group/lilypond-brasil,
-Portugese group}
+Portuguese group}
@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
French mailing list}
@subsubheading LilyPond Report
The easiest way to keep touch is by reading our community
-newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
+newsletter, the LilyPond Report:
+
+@example
+@uref{http://news.lilynet.net}
+@end example
@subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
@uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
info-lilypond subscribe and info}
-@uref{http://mail.gnu.org/archive/html/info-lilypond/,
+@uref{http://lists.gnu.org/archive/html/info-lilypond/,
info archive1}
@uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
archive2}
should be sent here.
@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
+@uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
lilypond-devel subscribe and info}
-@uref{http://mail.gnu.org/archive/html/lilypond-devel/,
+@uref{http://lists.gnu.org/archive/html/lilypond-devel/,
devel archive1}
@uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
archive2}
Bug-specific discussion takes place here.
@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
+@uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
bug-lilypond subscribe and info}
-@uref{http://mail.gnu.org/archive/html/bug-lilypond/,
+@uref{http://lists.gnu.org/archive/html/bug-lilypond/,
bug archive1}
@uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
archive2}
@end quotation
@warning{Before sending a message to the bug list, please read our
-guidelines for @ref{bug reports}.}
+guidelines for @ref{Bug reports}.}
@divEnd
-@node tiny examples
+@node Tiny examples
@unnumberedsec Tiny examples
@divClass{column-center-top}
-@node bug reports
+@node Bug reports
@unnumberedsec Bug reports
@divClass{column-center-top}
by creating a bug report.
@warning{We only accept bug reports in the form of
-@ref{tiny examples}. We have very limited resources to deal with
+@ref{Tiny examples}. We have very limited resources to deal with
bug reports, so any non-minimal example will be rejected. Almost
every bug can be demonstrated in four notes or less!}
%% change the output at all!
\version "2.10.0"
-\paper@{ ragged-right=##t @}
\relative c''' @{
c1
#(set-octavation 1)
Once you have verified that the issue is not already known and
created a bug report, please send it to us!
-Unfortunately there is a strict @qq{no top-posting} check on the
-bug list, which is often incorrectly triggered by lilypond files.
-To avoid this, please add
+@divClass{keep-bullets}
+@itemize
+
+@item
+If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org,
+bug-lilypond@@gnu.org} mailing list, send an email like normal.
+
+@item
+If you are not subscribed, you can still post a bug report with
+the
+@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
+gmane lilypond.bugs web interface}.
+
+However, there is a strict @qq{no top-posting} check on the gmane
+interface, which is often incorrectly triggered by lilypond files.
+To avoid this, please add:
@example
> I'm not top posting.
@end example
@noindent
-(you must include the @code{>} ) to the top of your bug report.
+(you @emph{must} include the @code{>} ) to the top of your bug
+report.
-@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
-Post with the gmane lilypond.bugs interface}, or send an email to
-@uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
+@end itemize
+@divEnd
-Once your bug has been sent to the list, our Bug Meister will
-examine the report. He may ask you for more information, or may
-add the report to the tracker and let you know what the issue
-number is.
+Once your bug has been sent to the list, our Bug Squad will
+examine the report. Please allow up to 24 hours, as we have a
+limited number of volunteers for this task. They may ask you for
+more information, or may add the report to the tracker and let you
+know what the issue number is.
You may mark the bug so that you automatically receive emails when
any activity on the bug occurs. This requires you have a google
@divEnd
-@node help us
+@node Help us
@unnumberedsec Help us
-TODO: talk about the Frogs, document suggestions, encourage getting
-involved, etc. Maybe mention GLISS and GOP, if those are happening
-in the near future.
+@divClass{column-center-top}
+@helpusNeed
-frog mailist: @uref{http://frogs.lily.net}
+@divEnd
+@divClass{column-left-top}
+@divClass{keep-bullets}
+@helpusTasks
-@node development
-@unnumberedsec Development
+@divEnd
+@divEnd
+
+@divClass{column-right-top}
+@helpusProjects
+
+@divEnd
+@node Development
+@unnumberedsec Development
+
@divClass{heading-center}
-@heading Development materials for LilyPond @versionDevel{}
+@ifclear web_version
+ @heading Development for LilyPond @version
+@end ifclear
+@ifset web_version
+ @heading Development for LilyPond @versionDevel
+@end ifset
+
@warning{These are @emph{unstable development} versions. If you
have the slightest doubt about how to use or install LilyPond, we
-urge you to use the stable @ref{download}, and read the stable
-@ref{manuals}.}
+urge you to use the stable @ref{Download}, and read the stable
+@ref{Manuals}.}
@divEnd
@divEnd
-@divClass{column-left-bottom}
+@divClass{column-left-top}
@subheading Download
Instructions for git and compiling are in the Contributor's Guide.
@end quotation
+@divEnd
-@subheading Manuals
-
-@help {these need the automatic symlinks or something. Maybe even
-a hard-coded url to lilypond.org/docs/2.13 or something??}
-Learning:
-@uref{lm-html, html}
-@uref{lm-big-html, big html}
-@uref{lm-pdf, pdf}
+@divClass{column-right-top}
+@subheading Contributor's Guide
-Glossary:
-@uref{mg-html, html}
-@uref{mg-big-html, big html}
-@uref{mg-pdf, pdf}
+LilyPond development is a fairly complicated matter. In order to
+help new contributors, and to keep the whole system (mostly)
+stable, we have written a manual for development tasks.
-Essay:
-@uref{essay-html, html}
-@uref{essay-big-html, big html}
-@uref{essay-pdf, pdf}
+@docLinksBare{Contributor's Guide, contributor,
+ @rcontribnamed{Top,Contributor's Guide},
+ @manualDevelContributorSplit,
+ @manualDevelContributorBig, 500 kB,
+ @manualDevelContributorPdf, 2.8 MB}
-Notation:
-@uref{notation-html, html}
-@uref{notation-big-html, big html}
-@uref{notation-pdf, pdf}
+@divEnd
-Usage:
-@uref{usage-html, html}
-@uref{usage-big-html, big html}
-@uref{usage-pdf, pdf}
-Snippets:
-@uref{snippets-html, html}
-@uref{snippets-big-html, big html}
-@uref{snippets-pdf, pdf}
+@divClass{column-center-top}
+@subheading Regression tests
-Changes:
-@uref{changes-html, html}
-@uref{changes-big-html, big html}
-@uref{changes-pdf, pdf}
+@divClass{keep-bullets}
-Internals:
-@uref{internals-html, html}
-@uref{internals-big-html, big html}
-@uref{internals-pdf, pdf}
+@ifclear web_version
-@divEnd
+@itemize
+@item
+@uref{../../input/regression/collated-files.html, Regression tests}:
+This release's regtests.
+(@uref{../../input/regression/collated-files.pdf, pdf version})
+@item
+@uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
+This release's musicXML tests.
+(@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
-@divClass{column-right-top}
-@subheading Contributors' Guide
+@item
+@uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}:
+This release's abc2ly tests.
+(@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version})
-LilyPond development is a fairly complicated matter. LilyPond is
-a large, (mostly) stable project. At any point in time, we have
-between 5 and 25 active contributors. In order to help new
-contributors, and to keep the whole system (mostly) stable, we
-have written a manual for contributors.
+@item
+@uref{../../input/regression/lilypond-book/collated-files.html, lilypond-book tests}:
+This release's lilypond-book tests.
+(@uref{../../input/regression/lilypond-book/collated-files.pdf, pdf version})
+@end itemize
-@divClass{keep-bullets}
-@itemize
+@end ifclear
-@item @uref{../contributor/index.html, Contributor's guide (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
+@ifset web_version
+@subsubheading Development version
-@item @uref{../contributor-big-page.html, Contributor's guide (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
+@itemize
+@item @regtestDevel (@regtestDevelPdf{})
-@item @uref{../contributor.pdf, contributor.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
+@item @regtestDevelXml (@regtestDevelXmlPdf{})
-@c @item @uref{TODO, contributor.info}:
-@c GNU info format for documentation. TODO, link broken.
+@item @regtestDevelAbc (@regtestDevelAbcPdf{})
+@item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{})
@end itemize
-@divEnd
-@divEnd
-@divClass{column-right-bottom}
-@subheading Regression tests
+@subsubheading Stable version
-@divClass{keep-bullets}
@itemize
+@item @regtestStable (@regtestStablePdf{})
-@item @uref{../../input/regression/collated-files.html, Regression tests}:
-This releases' tests. (also in
-@uref{../input/regression/collated-files.pdf, pdf})
+@item @regtestStableXml (@regtestStableXmlPdf{})
-@item @uref{../../input/regression/musicxml/collated-files.html,
-MusicXML Regression tests}:
-This releases' MusicXML tests. (also in
-@uref{../input/regression/musicxml/collated-files.pdf, pdf})
+@item @regtestStableAbc (@regtestStableAbcPdf{})
-@item @uref{http://lilypond.org/test, Archive of regression tests}:
-Comparisons beteween versions.
+@item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{})
+@end itemize
+@end ifset
+
+@subsubheading All versions
+
+@itemize
+@item @uref{http://lilypond.org/test, Archive of regression tests}:
+Comparisons between versions.
@end itemize
+
@divEnd
@divEnd
-@node authors
-@unnumberedsec Authors
-@help{Under construction; this is not an accurate list!}
-combo of:
+@divClass{column-center-bottom}
+@subheading Manuals
+
+@ifclear web_version
+@warning{These manuals are for LilyPond @version{}; the latest
+manuals can be found at @url{http://lilypond.org}}
+@end ifclear
+
+@divClass{normal-table}
+@multitable @columnfractions .3 .3 .3
+@headitem Introduction
+@item
+@docLinkSplit{Learning,learning,@manualDevelLearningSplit}
+@tab
+@docLinkBig{Learning,learning,@manualDevelLearningBig}
+@tab
+@docLinkPdf{Learning,learning,@manualDevelLearningPdf}
+
+@item
+@docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
+@tab
+@docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
+@tab
+@docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
+
+@item
+@docLinkSplit{Essay,essay,@manualDevelEssaySplit}
+@tab
+@docLinkBig{Essay,essay,@manualDevelEssayBig}
+@tab
+@docLinkPdf{Essay,essay,@manualDevelEssayPdf}
+
+@headitem Regular
+
+@item
+@docLinkSplit{Notation,notation,@manualDevelNotationSplit}
+@tab
+@docLinkBig{Notation,notation,@manualDevelNotationBig}
+@tab
+@docLinkPdf{Notation,notation,@manualDevelNotationPdf}
+
+@item
+@docLinkSplit{Usage,usage,@manualDevelUsageSplit}
+@tab
+@docLinkBig{Usage,usage,@manualDevelUsageBig}
+@tab
+@docLinkPdf{Usage,usage,@manualDevelUsagePdf}
+
+@item
+@docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
+@tab
+@docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
+@tab
+@docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
+
+@headitem Infrequent
+
+@item
+@docLinkSplit{Web,web,@manualDevelWebSplit}
+@tab
+@docLinkBig{Web,web,@manualDevelWebBig}
+@tab
+@docLinkPdf{Web,web,@manualDevelWebPdf}
+
+@item
+@docLinkSplit{Changes,changes,@manualDevelChangesSplit}
+@tab
+@docLinkBig{Changes,changes,@manualDevelChangesBig}
+@tab
+@docLinkPdf{Changes,changes,@manualDevelChangesPdf}
+
+@item
+@docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
+@tab
+@docLinkBig{Extending,extending,@manualDevelExtendingBig}
+@tab
+@docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
+
+@item
+@docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
+@tab
+@docLinkBig{Internals,internals,@manualDevelInternalsBig}
+@tab
+@docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
+
+@ifset web_version
+@headitem Downloadable
+
+@item
+@doctarballDevel
+@end ifset
+
+@end multitable
+
+@divEnd
+@divEnd
-http://lilypond.org/web/about/thanks
-Documentation/topdocs/AUTHORS.texi
-and maybe:
-http://lilypond.org/web/switch/
+@node Authors
+@unnumberedsec Authors
@divClass{column-left-top}
@subheading Current Development Team
@divEnd
@divClass{column-right-top}
-@subheading Previous Development Team Positions
+@subheading Previous Development Team
@divClass{keep-bullets}
@developersPrevious
@divEnd
-@divClass{column-center-bottom}
-@subheading Programming contributors
+@divClass{column-center-top}
+@subheading Current Contributors
@divClass{keep-bullets}
-@contributorsCore
+@subsubheading Programming
-@subheading Font contributors
+@coreCurrent
-@contributorsFont
+@subsubheading Font
-@subheading Documentation contributors
+@fontCurrent
-@contributorsDoc
+@subsubheading Documentation
-@subheading Support contributors
+@docCurrent
-@contributorsSupport
+@subsubheading Bug squad
-@subheading Translation contributors
+@bugsquadCurrent
-@contributorsTranslations
+@subsubheading Support
-@divEnd
-@divEnd
-
-
-
-@node publications
-@unnumberedsec Publications
+@supportCurrent
-@divClass{column-center-top}
-@subheading What we wrote
+@subsubheading Translation
-@divClass{keep-bullets}
-@itemize
+@translationsCurrent
-@item
-Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
-the Art of Shipping}. Forum Internacional Software Livre 2006
-(FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
-PDF 1095k})
+@divEnd
+@divEnd
-@item
-Erik Sandberg, @emph{Separating input language and formatter in
-GNU Lilypond}. Master's Thesis, Uppsala University, Department of
-Information Technology March 2006.
-(@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
-PDF 750k})
-@item
-Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
-for automated music engraving}. Proceedings of the XIV Colloquium
-on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
-(@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
+@divClass{column-center-bottom}
+@subheading Previous Contributors
-@end itemize
+@divClass{keep-bullets}
+@subsubheading Programming
-@divEnd
-@divEnd
+@corePrevious
+@subsubheading Font
-@divClass{column-center-bottom}
+@fontPrevious
-@subheading What others wrote
+@subsubheading Documentation
-@divClass{keep-bullets}
-@itemize
+@docPrevious
-@item
-September 2009
+@c uncomment when we have any previous members -gp
+@c @subsubheading Bug squad
-The German LinuxUser magazine wrote an
-@uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
-article about lilypond}.
+@c @bugsquadCurrent
+@subsubheading Support
-@item
-February 2008
+@supportPrevious
-In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
-articles on his personal site}, Andrew Hawryluk compares Finale
-and LilyPond in general terms, and evaluates in detail engraving
-capabilities of both pieces of software. The second article is an
-instructive analysis of Rachmaninoff's Piano Prelude 6 engraving,
-including comparisons with a reference hand-engraved edition.
+@subsubheading Translation
-@item
-December 2005
+@translationsPrevious
-Linux journal cover Linux Journal publishes an article titled
-@uref{http://www.linuxjournal.com/article/8364, Make Stunning
-Schenker Graphs with GNU LilyPond}. It is a in-depth but hands-on
-feature article with crisp LilyPond graphics. Author Kris Shaffer
-remarks “GNU Lilypond generates beautiful graphics that make
-commercial alternatives seem second-rate.”
+@divEnd
+@divEnd
-@item
-August 20, 2005
-The Belgian newspaper De Standaard investigates what drives Free
-Software authors in an article titled
-@uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
-Delen van KENNIS zonder WINSTBEJAG} (Non-profit sharing of
-knowlegde) in its `DS2 bijlage'. LilyPond is used as an example
-and the article is interspersed with quotes from an `email
-interview' with Jan Nieuwenhuizen. This marks LilyPond's first
-appearance in mainstream printed press.
-@item
-June 2005
+@node Publications
+@unnumberedsec Publications
-A French article on the LilyPond 2.6 release appeared on
-@uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
+@divClass{column-center-top}
+@subheading What we wrote about LilyPond
-@item
-October 2004
+@divClass{keep-bullets}
-The editors of Computer!Totaal, a Dutch computer magazine,
-@uref{http://lilypond.org/web/images/computer-totaal.jpeg,
-describe LilyPond} in the October 2004 issue as: @qq{Wonderful
-free (open source) software [..] The sheet music produced by
-LilyPond is exceptionally pretty [..] a very powerful system that
-can do almost anything.}
+@include we-wrote.itexi
-@item
-July, August 2004
+@divEnd
+@divEnd
-Dave Phillips wrote an introductory article for Linux Journal At
-the sounding edge: LilyPond, parts
-@uref{http://www.linuxjournal.com/article/7657, one} and
-@uref{http://www.linuxjournal.com/article/7719, two}.
-@item
-March 2004
+@divClass{column-center-bottom}
-Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
-linuxmusician.com (site now defunct). This interview was also
-reviewed in a
-@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
-slashdot story}.
+@subheading What people did with LilyPond
-@item
-February 2004
-Jazz singer Gail Selkirk writes about
-@uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
-Diving into LilyPond}. @qq{... you can make lead sheets or full
-orchestral parts, and the results can be stunning.}
-@uref{http://www.computermusic.co.uk/, Computer Music Special},
-issue CMS06.
+@divClass{keep-bullets}
-@end itemize
+@include others-did.itexi
@divEnd
@divEnd
-@node old news
+@node Old news
@unnumberedsec Old news
+@include web/news-front.itexi
+
@include web/news.itexi