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}
@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://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}
@subsubheading Grand LilyPond Input Syntax Standardization
-Website and mailist: TODO
+Website: @uref{http://lilypond.org/~graham/gliss}
GLISS will stabilize the (non-tweak) input syntax for the upcoming
LilyPond 3.0. After updating to 3.0, the input syntax for
@subheading Manuals
-@help {these need the automatic symlinks or something. Maybe even
-a hard-coded url to lilypond.org/docs/2.13 or something??}
-
-Commented out pending a real fix
-@ignore
+@divClass{keep-bullets}
+@itemize
+@item
Learning:
-@uref{lm-html, html}
-@uref{lm-big-html, big html}
-@uref{lm-pdf, pdf}
+@manualDevelLearningSplit
+@* @manualDevelLearningBig
+@* @manualDevelLearningPdf
+
+@item
Glossary:
-@uref{mg-html, html}
-@uref{mg-big-html, big html}
-@uref{mg-pdf, pdf}
+@manualDevelGlossarySplit
+@* @manualDevelGlossaryBig
+@* @manualDevelGlossaryPdf
+
+@item
Essay:
-@uref{essay-html, html}
-@uref{essay-big-html, big html}
-@uref{essay-pdf, pdf}
+@manualDevelEssaySplit
+@* @manualDevelEssayBig
+@* @manualDevelEssayPdf
+
+@c separate introduction, regular, infrequent manuals
+@smallspace
+
+@item
Notation:
-@uref{notation-html, html}
-@uref{notation-big-html, big html}
-@uref{notation-pdf, pdf}
+@manualDevelNotationSplit
+@* @manualDevelNotationBig
+@* @manualDevelNotationPdf
+
+@item
Usage:
-@uref{usage-html, html}
-@uref{usage-big-html, big html}
-@uref{usage-pdf, pdf}
+@manualDevelUsageSplit
+@* @manualDevelUsageBig
+@* @manualDevelUsagePdf
+
+@item
Snippets:
-@uref{snippets-html, html}
-@uref{snippets-big-html, big html}
-@uref{snippets-pdf, pdf}
+@manualDevelSnippetsSplit
+@* @manualDevelSnippetsBig
+@* @manualDevelSnippetsPdf
+
+@c separate introduction, regular, infrequent manuals
+@smallspace
+
+@item
+Web:
+
+@manualDevelWebSplit
+@* @manualDevelWebBig
+@* @manualDevelWebPdf
+
+@item
Changes:
-@uref{changes-html, html}
-@uref{changes-big-html, big html}
-@uref{changes-pdf, pdf}
+@manualDevelChangesSplit
+@* @manualDevelChangesBig
+@* @manualDevelChangesPdf
+
+@item
+Extend:
+
+@manualDevelExtendingSplit
+@* @manualDevelExtendingBig
+@* @manualDevelExtendingPdf
+
+@item
Internals:
-@uref{internals-html, html}
-@uref{internals-big-html, big html}
-@uref{internals-pdf, pdf}
-@end ignore
+@manualDevelInternalsSplit
+@* @manualDevelInternalsBig
+@* @manualDevelInternalsPdf
+@end itemize
+@divEnd
@divEnd
contributors, and to keep the whole system (mostly) stable, we
have written a manual for contributors.
-This manual is not intended to be read sequentially; new contributors
-should only read the sections which are relevant to them. For more
-information about different jobs, see @ref{Help us}.
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../contributor/index.html, Contributor's guide (split HTML)}:
-the manual is split between many HTML pages.
-@*@ @ @emph{(small download for each page)}
-
-@item @uref{../contributor-big-page.html, Contributor's guide (big HTML)}:
-read this manual as one huge HTML page.
-@*@ @ @emph{(large single download, 500 kb)}
-
-@item @uref{../contributor.pdf, contributor.pdf}:
-download as a PDF file.
-@*@ @ @emph{(large single download, 2.8 Mb)}
+@warning{This manual is not intended to be read sequentially; new
+contributors should only read the sections which are relevant to
+them. For more information about different jobs, see
+@ref{Help us}.}
-@c @item @uref{TODO, contributor.info}:
-@c GNU info format for documentation. TODO, link broken.
+@docLinks{Contributor's Guide, contributor,
+ @rcontribnamed{Top,Contributor's Guide},
+ @manualDevelContributorSplit,
+ @manualDevelContributorBig, 500 kB,
+ @manualDevelContributorPdf, 2.8 MB}
-@end itemize
-@divEnd
@divEnd
@divEnd
@divClass{column-right-top}
-@subheading Previous Development Team Positions
+@subheading Previous Development Team
@divClass{keep-bullets}
@developersPrevious
The German LinuxUser magazine wrote an
@uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
-article about lilypond}.
+article about LilyPond}.
@item
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.
+and LilyPond in general terms, and evaluates engraving
+capabilities of both pieces of software in detail. The second
+article is an instructive analysis of engraving issues in
+Rachmaninoff's Piano Prelude No. 6, including comparisons with a
+hand-engraved reference edition.
+
+@item
+June 2006
+
+@uref{http://distrowatch.com,DistroWatch} awards LilyPond and
+@uref{http://distrowatch.com/weekly.php?issue=20060605,writes}
+@qq{Ladies and Gentleman, we are pleased to announce that, based
+on readers' requests, the DistroWatch May 2006 donation has been
+awarded to LilyPond (@euro{}190.00) and Lua (US$250.00).}
@item
December 2005
-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.”
+@uref{http://linuxjournal.com,Linux Journal} publishes an article
+titled @uref{http://www.linuxjournal.com/article/8364, Make
+Stunning Schenker Graphs with GNU LilyPond}. It is an in-depth
+but hands-on feature article with crisp LilyPond graphics. Author
+Kris Shaffer remarks @qq{GNU Lilypond generates beautiful graphics
+that make commercial alternatives seem second-rate.}
@item
August 20, 2005
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
+knowlegde) in its @q{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
@item
July, August 2004
-Dave Phillips wrote an introductory article for Linux Journal At
+Dave Phillips wrote an introductory article for
+@uref{http://linuxjournal.com,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
-Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
-linuxmusician.com (site now defunct). This interview was also
-reviewed in a
+Chris Cannam
+@uref{http://www.all-day-breakfast.com/cannam/linux-musician/lilypond.html,interviewed}
+Han-Wen Nienhuys and Jan Nieuwenhuizen on linuxmusician.com
+(original site defunct). This interview was also reviewed in a
@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
slashdot story}.
@node Old news
@unnumberedsec Old news
+@include web/news-front.itexi
+
@include web/news.itexi
+
+
projects / lilypond.git / blobdiff