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
@unnumbered Community
+@divClass{link-headings}
@divClass{column-center-top}
@subheading Interacting with the community
@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
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}
@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}
If you have discovered a bug which is not listed, please help us
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 bug
-reports, so any non-minimal example will be rejected. Almost
+@warning{We only accept bug reports in the form of
+@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!}
Here is an example of a good bug report:
@example
-%% the octavation command doesn't
-%% change the output at all!
-
-\version "2.10.0"
-\paper@{ ragged-right=##t @}
-\relative c''' @{
- c1
- #(set-octavation 1)
- c1
+% Accidentals should be printed for only
+% the first note in a tie, but this version
+% prints flats on both notes.
+\version "2.10.1"
+
+\relative c'' @{
+ bes1 ~
+ bes1
@}
@end example
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
-
-@example
-> I'm not top posting.
-@end example
-
-@noindent
-(you 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}.
-
-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.
-
-You may mark the bug so that you automatically receive emails when
-any activity on the bug occurs. This requires you have a google
-account.
-@divEnd
-
-
-@node Help us
-@unnumberedsec Help us
-
- TODO: talk about the Frogs, document suggestions, encourage getting
-@divClass{heading-center}
-@heading We need you!
-
-The LilyPond development team is quite small; we really want to
-get more people involved. Please consider helping us, even with
-small tasks -- anything that you do will allow an experienced
-developer to work on advanced tasks.
-
-@divEnd
-
-
-@divClass{column-left-top}
-@subheading Ways of contributing
-
-Many users ask @qq{I can't program; how can I help?}
-
@divClass{keep-bullets}
-@subsubheading No source, no programming
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-@sourceimage{logo-macosx,,,}
-@sourceimage{logo-windows,,,}
-
-@itemize
-@item
-Mailist support: we have many users asking for him.
-
-@item
-LilyPond Snippet Repository (LSR): create and fix snippets. See
-@rcontrib{Adding and editing snippets}.
-
-@item
-Bug reporting: our infrastructure for organizing bug reports only
-requires a web browser. Please do not add bugs directly unless
-you have learned how we like to handle such reports. See
-@rcontrib{Issues}.
-
-@item
-Discussions, reviews, and testing: the developers often ask for
-feedback about new documentation, potential syntax changes, and
-testing new features. We rarely receive as much feedback as we
-would like; please consider responding to these requests! (even
-if your only contribution is @qq{wow, looks great!})
-
-@end itemize
-
-@subsubheading With source, no programming
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-@sourceimage{logo-macosx,,,}
-@sourceimage{logo-windows,,,}
-
-To get the source code, see @rcontrib{Starting with git}.
-
@itemize
-@item
-Documentation:
-@rcontrib{Building documentation without compiling LilyPond}.
@item
-Website: the website is built from the normal documentation
-source. See the info about documentation, and also
-@rcontrib{Website work}.
+If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org,
+bug-lilypond@@gnu.org} mailing list, send an email like normal.
@item
-Translations: see @rcontrib{Translating the documentation}, and
-@rcontrib{Translating the website}.
-
-@end itemize
-
-@subsubheading Programming
+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}.
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-@sourceimage{logo-macosx,,,}
+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:
-To the best of our knowledge, nobody has compiled LilyPond on
-Windows. We have therefore created @emph{lilybuntu}, a custom
-@emph{Ubuntu} variant configured for LilyPond development. This
-runs inside a virtual machine, without disturbing the Windows
-operating system. For more information, see
-@rcontrib{Using a Virtual Machine to Compile LilyPond}.
+@example
+> I'm not top posting.
+@end example
-@itemize
-@item
-Bugfixes, new features: the best way to begin is to join the
-Frogs.
+@noindent
+(you @emph{must} include the @code{>} ) to the top of your bug
+report.
@end itemize
-
@divEnd
@divEnd
+@divClass{column-center-bottom}
+@subheading Step 4: Wait for a response
-@divClass{column-right-top}
-@subheading Projects
-
-@subsubheading Frogs
-
-Website and mailist: @uref{http://frogs.lilynet.net}
-
-The Frogs are simple LilyPond users who have chosen to get
-involved in their favorite software's development. Fixing bugs,
-implementing new features, documenting the source code: there's a
-lot to be done, but most importantly: this is a chance for
-everyone to learn more about LilyPond, about Free Software, about
-programming... and to have fun. If you're curious about any of
-it, then the word is: @emph{Join the Frogs!}
-
-
+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.
-@help{not active yet; either comment out or begin these projects
-before 2.14}
+You may mark the bug so that you automatically receive emails when
+any activity on the bug occurs. This requires you have a google
+account.
+@divEnd
-@subsubheading Grand LilyPond Input Syntax Standardization
+@divClass{column-center-bottom}
+@subheading Optional help: show the desired behavior
-Website and mailist: TODO
+Once an issue has been added to the tracker, it can be very
+helpful if we can see the desired output. Feel free to add input
+code and/or images (possibly created with other tools) which
+demonstrate what you think it should look like!
-GLISS will stabilize the (non-tweak) input syntax for the upcoming
-LilyPond 3.0. After updating to 3.0, the input syntax for
-untweaked music will remain stable for the foreseeable future.
+@divEnd
-We will have an extensive discussion period to determine the final
-input specification.
-@subsubheading Grand Organizing Project
-Website and mailist: TODO
+@node Help us
+@unnumberedsec Help us
-GOP is our big recruiting drive for new contributors.
+@divClass{column-center-top}
+@helpusNeed
@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-
-@divClass{legal}
-All logos and product images are copyright and trademark
-acknowledged.
-
-@logoLegalLinux
-
-@logoLegalFreeBSD
+@divClass{column-left-top}
+@divClass{keep-bullets}
+@helpusTasks
-@logoLegalMacOSX
+@divEnd
+@divEnd
-@logoLegalWindows
+@divClass{column-right-top}
+@helpusProjects
@divEnd
-@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
+
+@c we normally don't allow named references, but in this case
+@c it's good to emphasize the "stable" part. -gp
@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 @ref{Download, stable Download}, and read the
+@ref{Manuals, stable 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 @regtestStableXml (@regtestStableXmlPdf{})
-@item @uref{../../input/regression/collated-files.html, Regression tests}:
-This releases' tests. (also in
-@uref{../input/regression/collated-files.pdf, pdf})
+@item @regtestStableAbc (@regtestStableAbcPdf{})
+
+@item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{})
+@end itemize
+@end ifset
-@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 @uref{http://lilypond.org/test, Archive of regression tests}:
-Comparisons beteween versions.
+@subsubheading All versions
+
+@itemize
+@item @uref{http://lilypond.org/test, Comparisons between regression tests}
+
+@item @uref{http://lilypond.org/download/binaries/test-output/,
+Archive of all regression tests}
@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
-
-@subheading Font contributors
-
-@contributorsFont
+@subsubheading Programming
-@subheading Documentation contributors
+@coreCurrent
-@contributorsDoc
+@subsubheading Font
-@subheading Support contributors
+@fontCurrent
-@contributorsSupport
+@subsubheading Documentation
-@subheading Translation contributors
+@docCurrent
-@contributorsTranslations
+@subsubheading Bug squad
-@divEnd
-@divEnd
+@bugsquadCurrent
+@subsubheading Support
+@supportCurrent
-@node Publications
-@unnumberedsec Publications
+@subsubheading Translation
-@divClass{column-center-top}
-@subheading What we wrote
-
-@divClass{keep-bullets}
-@itemize
-
-@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})
-
-@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})
-
-@end itemize
+@translationsCurrent
@divEnd
@divEnd
@divClass{column-center-bottom}
-
-@subheading What others wrote
+@subheading Previous Contributors
@divClass{keep-bullets}
-@itemize
+@subsubheading Programming
-@item
-September 2009
+@corePrevious
-The German LinuxUser magazine wrote an
-@uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
-article about lilypond}.
+@subsubheading Font
+@fontPrevious
-@item
-February 2008
+@subsubheading Documentation
-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.
+@docPrevious
-@item
-December 2005
+@c uncomment when we have any previous members -gp
+@c @subsubheading Bug squad
-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.”
+@c @bugsquadCurrent
-@item
-August 20, 2005
+@subsubheading Support
-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.
+@supportPrevious
-@item
-June 2005
+@subsubheading Translation
-A French article on the LilyPond 2.6 release appeared on
-@uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
+@translationsPrevious
-@item
-October 2004
+@divEnd
+@divEnd
-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.}
-@item
-July, August 2004
-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}.
+@node Publications
+@unnumberedsec Publications
-@item
-March 2004
+@divClass{column-center-top}
+@subheading What we wrote about LilyPond
-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}.
+@divClass{keep-bullets}
-@item
-February 2004
+@include we-wrote.itexi
-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.
+@divEnd
+@divEnd
-@end itemize
+@divClass{column-center-bottom}
+
+@subheading What people did with LilyPond
+
+
+@divClass{keep-bullets}
+
+@include others-did.itexi
@divEnd
@divEnd
+@contactUsAbout{academic papers}
+
@node Old news
@unnumberedsec Old news
+@include web/news-front.itexi
+
@include web/news.itexi