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. For details, see the Contributors'
7 Guide, node Updating translation committishes..
10 @include included/acknowledge.itexi
11 @include included/authors.itexi
12 @include included/gsoc.itexi
13 @include included/helpus.itexi
18 @divClass{link-headings}
20 @divClass{column-center-top}
21 @subheading Interacting with the community
26 @ref{Contact}: get help, discuss, and keep in touch!
29 @ref{Tiny examples}: these are @emph{highly} recommended when
33 @ref{Bug reports}: something went wrong.
38 @divClass{column-left-bottom}
39 @subheading Making LilyPond better
44 @ref{Help us}: your assistance is requested.
47 @ref{Sponsoring}: financial contributions.
50 @ref{Development}: for contributors and testers.
53 @ref{Google Summer of Code}: ideas for Google Summer of Code (GSoC).
56 @ref{Authors}: the people who made LilyPond what it is today.
59 @ref{Acknowledgements}: projects and institutions that support LilyPond
64 @divClass{column-right-bottom}
65 @subheading Miscellaneous
70 @ref{Publications}: what we wrote, and have had written about us.
73 @ref{News}: news from the LilyPond project.
76 @ref{Attic}: announcements and changelogs from past versions,
92 * Google Summer of Code::
103 @unnumberedsec Contact
106 @divClass{column-left-bottom}
107 @subheading User Discussions and Help
109 @subsubheading User mailing list: @code{lilypond-user@@gnu.org}
111 This mailing list is the main place for users to discuss and help
115 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,
116 lilypond-user subscribe and info}
118 @uref{http://lists.gnu.org/archive/html/lilypond-user/,
120 @uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
122 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
125 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
126 send to lilypond-user with gmane}
129 @warning{When asking questions, please use @ref{Tiny examples}!}
131 @subsubheading LilyPond Snippet Repository
133 The LilyPond Snippet Repository is a large collection of
134 user-submitted examples, which can freely be copied and used
135 in your own works. See what other people have written,
139 @uref{http://lsr.di.unimi.it}
142 Particularly instructive examples from LSR are included in our
143 official documentation, in @ref{Snippets}.
148 Some level of support is provided on our IRC channel,
151 @uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
154 This channel has no public archive, so any question that may
155 be useful for others would better be posted to one of the mailing lists.
158 <form action="http://webchat.freenode.net"
162 <input name="nick" type="text" size="15" value="">
164 <input name="channels" type="hidden" value="lilypond">
165 <input type="submit" value="Join #lilypond IRC Chat">
168 <script language="JavaScript" type="text/javascript">
169 var username = "web";
170 var lang = window.navigator.userLanguage ? window.navigator.userLanguage
171 : window.navigator.language;
172 username += '-' + lang.substr(0, 2);
173 username += '-' + navigator.appName.substr(0, 2);
174 username += navigator.appCodeName.replace (" ", "").substr(0, 2);
175 username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
176 document.forms["f_lily_irc"].nick.value = username;
180 @subsubheading Other languages
183 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
186 @uref{http://www.lilypondforum.de/,
189 @uref{http://groups.google.com/group/lilypond-brasil,
192 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-es,
193 Spanish mailing list}
198 @divClass{column-right-top}
199 @subheading The LilyPond Blog
201 Read our community blog, @q{Scores of Beauty}:
204 @uref{http://lilypondblog.org}
207 @subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
209 This mailing list is a low-volume, read-only list which receives
210 notifications of new releases.
213 @uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
214 info-lilypond subscribe and info}
216 @uref{http://lists.gnu.org/archive/html/info-lilypond/,
218 @uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
220 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
223 @c don't include gmane posting here. -gp
230 @divClass{column-right-bottom}
231 @subheading Developer Discussions and Translations
233 @subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
235 Developer discussions take place on this list. Patches can also be sent
239 @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel,
240 lilypond-devel subscribe and info}
242 @uref{http://lists.gnu.org/archive/html/lilypond-devel/,
244 @uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
246 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
249 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
250 send to lilypond-devel with gmane}
254 @subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
256 Bug reports and discussions should be sent here. Do not send patches
260 @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,
261 bug-lilypond subscribe and info}
263 @uref{http://lists.gnu.org/archive/html/bug-lilypond/,
265 @uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
267 @uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
270 @c don't include gmane posting here. -gp
273 @warning{Before sending a message to the bug list, please read our
274 guidelines for @ref{Bug reports}.}
277 @subsubheading Translation mailing list: @code{translations@@lilynet.org}
279 All discussions about translating LilyPond manuals should be sent here.
280 Do not send patches to this list.
283 @uref{http://lilypond-translations.3384276.n2.nabble.com/,
284 Translation mailing list archive}
291 @unnumberedsec Tiny examples
293 @divClass{column-center-top}
294 @subheading What are @qq{Tiny examples}?
296 A tiny example is an example from which @strong{nothing} can be removed.
299 @divClass{column-left-bottom}
300 @subheading Why create them?
302 @divClass{keep-bullets}
306 The simpler the example is, the quicker potential helpers can
307 understand it and help you.
310 A tiny example demonstrates that you have put effort towards
311 solving the problem yourself. When people send huge portions of
312 input, it looks like they don't care if we help them or not.
315 Creating a tiny example helps you to understand what is
316 happening. Many false problem reports can be avoided by
317 attempting to create a tiny example; if you cannot replicate a
318 @qq{bug} in a tiny example, then the problem was probably an
319 insufficient understanding of LilyPond, not an actual bug!
327 @divClass{column-right-bottom}
328 @subheading How to create them?
330 @divClass{keep-bullets}
334 Include the @code{\version} number.
337 Make it small! Examples about spacing or page layout might
338 require many bars of music, but most issues can be reproduced
339 using less than a single measure.
342 When trying to create an example, try commenting out @w{(@code{%}
343 or @code{%@{ @dots{} %@}})} sections of your file. If you
344 can comment something while still demonstrating the main idea,
345 then remove the commented-material.
348 Avoid using complicated notes, keys or time signatures, unless
349 the bug is about the behavior of those items.
352 Do not use @code{\override} or @code{\set} commands unless the bug
353 is about those specific commands.
356 Optionally, attach an image showing the desired graphical output.
363 @divClass{column-center-bottom}
364 @subheading How tiny should they be?
366 Is the code below a minimal example?
370 \include "english.ly"
375 \numericTimeSignature
377 <cs' d'' b''>16 <cs' d'' b''>8.
378 %% Here: the tie on the D's looks funny
379 %% Too tall? Left-hand endpoint is not aligned with the B tie?
381 <cs' d'' b''>8 [ <b d'' a''> ]
386 Well, it is not very big, but a truly minimal example is here:
391 % middle tie looks funny here:
392 <c' d'' b''>8. ~ <c' d'' b''>8
396 Very few tiny examples exceed 10 lines of code -
397 quite often 4 lines are enough to demonstrate the problem!
403 @unnumberedsec Bug reports
406 @divClass{heading-center}
407 If you have input that results in a crash or wrong output,
411 @divClass{column-center-top}
412 @subheading Step 1: Known bugs
414 We may already know about this bug. Check here:
417 @uref{http://sourceforge.net/p/testlilyissues/issues/}
420 @warning{Please @strong{DO NOT} add bug reports directly to the
421 bug tracker. Once an issue has been added to the tracker, feel
422 free to add more information to that report.}
427 @divClass{column-left-bottom}
428 @subheading Step 2: Creating a bug report
430 If you have discovered a bug which is not listed,
431 please help us by creating a bug report.
433 @warning{We only accept reports in the form of
434 @ref{Tiny examples}. We have very limited resources,
435 so any non-minimal example will be rejected. Almost
436 every bug can be demonstrated in four notes or less!}
438 Here is an example of a good bug report:
441 % Accidentals should be printed for only
442 % the first note in a tie, but this version
443 % prints flats on both notes.
454 @divClass{column-right-bottom}
455 @subheading Step 3: Sending a bug report
457 Once you have verified that the issue is not already known and
458 created a bug report, please send it to us!
460 @divClass{keep-bullets}
464 If you are subscribed to the @uref{mailto:bug-lilypond@@gnu.org,
465 bug-lilypond@@gnu.org} mailing list, send an email like normal.
468 If you are not subscribed, you can still post a bug report with
470 @uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
471 gmane lilypond.bugs web interface}.
473 However, there is a strict @qq{no top-posting} check on the gmane
474 interface, which is often incorrectly triggered by lilypond files.
475 To avoid this, please add:
478 > I'm not top posting.
482 (you @emph{must} include the @code{>} ) to the top of your bug
489 @divClass{column-center-bottom}
490 @subheading Step 4: Wait for a response
492 Once your bug report has been sent to the list, our Bug Squad will
493 examine it; they may ask you for more information. You will be notified
494 when the report will be added to the bug tracker. Please allow up to 4
495 days, as we have a limited number of volunteers for this task.
497 Once a bug has been added to the tracker, you can comment it to add
498 more information about it.
499 In order to be automatically notified about any activity on the
500 tracker issue, you may subscribe by clicking the envelope
501 symbol next to the issue title.
502 Commenting and subscribing require being logged in with a sourceforge account.
505 @divClass{column-center-bottom}
506 @subheading Optional help: show the desired behavior
508 Once an issue has been added to the tracker, it can be very
509 helpful if we can see the desired output. Feel free to add input
510 code and/or images (possibly created with other tools) which
511 demonstrate what you think it should look like!
518 @unnumberedsec Help us
520 @divClass{column-center-top}
525 @divClass{column-left-top}
526 @divClass{keep-bullets}
532 @divClass{column-right-top}
539 @unnumberedsec Sponsoring
541 @divClass{keep-bullets}
542 @divClass{column-left-top}
548 @item some users have paid for new features
549 @item some developers have added new features for hire
552 The LilyPond project does not organize such efforts; we neither
553 endorse nor discourage such agreements. Any contracts between
554 private individuals is the business of those individuals, not
559 @divClass{column-right-top}
560 @subheading Guidelines
562 Any user wanting to offer money in exchange for work should bear
563 in mind the following points:
567 LilyPond developers may advertise their services on the lilypond
568 email lists from time to time.
571 Any agreements between private individuals should include the
572 normal precautions when conducting business: who pays, how much do
573 they pay, with what method of payment, and upon what set of
574 conditions. We suggest that any ambiguity or uncertainty in these
575 questions should be resolved before any work begins.
581 @divClass{column-center-bottom}
582 @subheading Interested developers
584 Here is a list of people who have expressed an interest in
585 bounties. Note that the amount of work done by individuals varies
586 quite a bit throughout the years. We do not guarantee that this
587 list is up-to-date, nor do we guarantee that the people listed
588 here have any ability. The only criteria is "XYZ asked to be
589 listed on this page".
591 Looking at the git history is a good way to determine who the most
592 active and experienced developers are. Statistics up to version
595 @multitable @columnfractions .3 .3 .3
596 @item @uref{http://lilypond.org/~graham/gitstats-all/, overall history}
597 @tab @uref{http://lilypond.org/~graham/gitstats-1year/, past year}
598 @tab @uref{http://lilypond.org/~graham/gitstats-3months/, past three months}
601 Interested developers:
603 @item @email{lilypond-devel@@gnu.org, LilyPond developer list}
604 Since no developer currently is listed for commercial development,
605 your best bet is asking on the developer list.
608 @c @item @email{name@@adress.domain, Name}
609 @c area of interest (256 chars max)
618 @unnumberedsec Development
620 @divClass{heading-center}
622 @heading Development for LilyPond @version
625 @heading Development for LilyPond @versionDevel
629 @c we normally don't allow named references, but in this case
630 @c it's good to emphasize the "stable" part. -gp
631 @warning{These are @emph{unstable development} versions. If you
632 have the slightest doubt about how to use or install LilyPond, we
633 urge you to use the @ref{Download, stable Download}, and read the
634 @ref{Manuals, stable Manuals}.}
638 @divClass{column-center-top}
639 @subheading Release numbers
641 There are two sets of releases for LilyPond: stable releases, and
642 unstable development releases. Stable versions have an
643 even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
644 Development versions have an odd-numbered @q{minor} version number
645 (e.g., 2.7, 2.9, 2.11).
650 @divClass{column-left-top}
653 Instructions for git and compiling are in the Contributor's Guide.
656 @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
659 Documentation writers and testers will generally want to download
664 @downloadDevelLinuxNormal
666 @downloadDevelLinuxBig
668 @downloadDevelLinuxPPC
670 @downloadDevelFreeBSDNormal
672 @downloadDevelFreeBSDBig
674 @downloadDevelDarwinNormal
676 @downloadDevelDarwinPPC
678 @downloadDevelWindows
687 @divClass{column-right-top}
688 @subheading Contributor's Guide
690 LilyPond development is a fairly complicated matter. In order to
691 help new contributors, and to keep the whole system (mostly)
692 stable, we have written a manual for development tasks.
694 @docLinksBare{Contributor's Guide, contributor,
695 @rcontribnamed{Top,Contributor's Guide},
696 @manualDevelContributorSplit,
697 @manualDevelContributorBig, 500 kB,
698 @manualDevelContributorPdf, 2.8 MB}
703 @divClass{column-center-top}
704 @subheading Regression tests
706 @divClass{keep-bullets}
712 @uref{../../input/regression/collated-files.html, Regression tests}:
713 This release's regtests.
714 (@uref{../../input/regression/collated-files.pdf, pdf version})
717 @uref{../../input/regression/musicxml/collated-files.html, MusicXML tests}:
718 This release's musicXML tests.
719 (@uref{../../input/regression/musicxml/collated-files.pdf, pdf version})
722 @uref{../../input/regression/abc2ly/collated-files.html, abc2ly tests}:
723 This release's abc2ly tests.
724 (@uref{../../input/regression/abc2ly/collated-files.pdf, pdf version})
727 @uref{../../input/regression/lilypond-book/collated-files.html, lilypond-book tests}:
728 This release's lilypond-book tests.
729 (@uref{../../input/regression/lilypond-book/collated-files.pdf, pdf version})
735 @subsubheading Development version
738 @item @regtestDevel (@regtestDevelPdf{})
740 @item @regtestDevelXml (@regtestDevelXmlPdf{})
742 @item @regtestDevelAbc (@regtestDevelAbcPdf{})
744 @item @regtestDevelLilypondBook (@regtestDevelLilypondBookPdf{})
747 @subsubheading Stable version
750 @item @regtestStable (@regtestStablePdf{})
752 @item @regtestStableXml (@regtestStableXmlPdf{})
754 @item @regtestStableAbc (@regtestStableAbcPdf{})
756 @item @regtestStableLilypondBook (@regtestStableLilypondBookPdf{})
761 @subsubheading All versions
764 @item @uref{http://lilypond.org/test, Comparisons between regression tests}
766 @item @uref{http://lilypond.org/downloads/binaries/test-output/,
767 Archive of all regression tests}
776 @divClass{column-center-bottom}
780 @warning{These manuals are for LilyPond @version{}; the latest
781 manuals can be found at @url{http://lilypond.org}}
784 @divClass{normal-table}
785 @multitable @columnfractions .3 .3 .3
786 @headitem Introduction
789 @docLinkSplit{Learning,learning,@manualDevelLearningSplit}
791 @docLinkBig{Learning,learning,@manualDevelLearningBig}
793 @docLinkPdf{Learning,learning,@manualDevelLearningPdf}
796 @docLinkSplit{Glossary,music-glossary,@manualDevelGlossarySplit}
798 @docLinkBig{Glossary,music-glossary,@manualDevelGlossaryBig}
800 @docLinkPdf{Glossary,music-glossary,@manualDevelGlossaryPdf}
803 @docLinkSplit{Essay,essay,@manualDevelEssaySplit}
805 @docLinkBig{Essay,essay,@manualDevelEssayBig}
807 @docLinkPdf{Essay,essay,@manualDevelEssayPdf}
810 @multitable @columnfractions .3 .3 .3
814 @docLinkSplit{Notation,notation,@manualDevelNotationSplit}
816 @docLinkBig{Notation,notation,@manualDevelNotationBig}
818 @docLinkPdf{Notation,notation,@manualDevelNotationPdf}
821 @docLinkSplit{Usage,usage,@manualDevelUsageSplit}
823 @docLinkBig{Usage,usage,@manualDevelUsageBig}
825 @docLinkPdf{Usage,usage,@manualDevelUsagePdf}
828 @docLinkSplit{Snippets,snippets,@manualDevelSnippetsSplit}
830 @docLinkBig{Snippets,snippets,@manualDevelSnippetsBig}
832 @docLinkPdf{Snippets,snippets,@manualDevelSnippetsPdf}
835 @multitable @columnfractions .3 .3 .3
839 @docLinkSplit{Web,web,@manualDevelWebSplit}
841 @docLinkBig{Web,web,@manualDevelWebBig}
843 @docLinkPdf{Web,web,@manualDevelWebPdf}
846 @docLinkSplit{Changes,changes,@manualDevelChangesSplit}
848 @docLinkBig{Changes,changes,@manualDevelChangesBig}
850 @docLinkPdf{Changes,changes,@manualDevelChangesPdf}
853 @docLinkSplit{Extending,extending,@manualDevelExtendingSplit}
855 @docLinkBig{Extending,extending,@manualDevelExtendingBig}
857 @docLinkPdf{Extending,extending,@manualDevelExtendingPdf}
860 @docLinkSplit{Internals,internals,@manualDevelInternalsSplit}
862 @docLinkBig{Internals,internals,@manualDevelInternalsBig}
864 @docLinkPdf{Internals,internals,@manualDevelInternalsPdf}
868 @multitable @columnfractions .3
869 @headitem Downloadable
883 @node Google Summer of Code
884 @unnumberedsec Google Summer of Code
890 @unnumberedsec Authors
892 @divClass{column-left-top}
893 @subheading Current Development Team
895 @divClass{keep-bullets}
900 @divClass{column-right-top}
901 @subheading Previous Development Team
903 @divClass{keep-bullets}
909 @divClass{column-center-top}
910 @subheading Current Contributors
912 @divClass{keep-bullets}
913 @subsubheading Programming
921 @subsubheading Documentation
925 @subsubheading Bug squad
929 @subsubheading Support
933 @subsubheading Translation
941 @divClass{column-center-bottom}
942 @subheading Previous Contributors
944 @divClass{keep-bullets}
945 @subsubheading Programming
953 @subsubheading Documentation
957 @c uncomment when we have any previous members -gp
958 @c @subsubheading Bug squad
962 @subsubheading Support
966 @subsubheading Translation
968 @translationsPrevious
973 @node Acknowledgements
974 @unnumberedsec Acknowledgements
976 @divClass{column-center-top}
977 @subheading Acknowledgements
979 @divClass{keep-bullets}
980 @acknowledgementsCurrent
986 @unnumberedsec Publications
988 @divClass{column-center-top}
989 @subheading What we wrote about LilyPond
991 @divClass{keep-bullets}
993 @include we-wrote.itexi
998 @divClass{column-center-bottom}
999 @subheading What people did with LilyPond
1001 @divClass{keep-bullets}
1003 @include others-did.itexi
1008 @contactUsAbout{academic papers}
1014 @include web/news-new.itexi
1016 @divClass{column-center-bottom}
1017 @subheading Old News
1018 Older news can be found in the @ref{Attic}, along with older
1019 announcements and changelogs
1023 @unnumberedsec Attic
1025 @divClass{column-center-top}
1026 @subheading Announcements
1028 Announcements and news by version:
1029 @uref{http://lilypond.org/doc/v2.16/Documentation/web/index#Lilypond-2_002e16_002e0-released_0021-August-24_002c-2012-1,v2.16},
1030 @uref{http://lilypond.org/doc/v2.14/Documentation/web/index#LilyPond-2_002e14_002e0-released_0021-June-6_002c-2011,v2.14},
1031 @miscLink{announce-v2.12,v2.12},
1032 @miscLink{announce-v2.10,v2.10},
1033 @miscLink{announce-v2.8,v2.8},
1034 @miscLink{announce-v2.6,v2.6},
1035 @miscLink{announce-v2.4,v2.4},
1036 @miscLink{announce-v2.2,v2.2},
1037 @miscLink{announce-v2.0,v2.0},
1038 @miscLink{ANNOUNCE-1.2,v1.2},
1039 @miscLink{ANNOUNCE-1.0,v1.0},
1040 @miscLink{ANNOUNCE-0.1,v0.1}
1042 Descriptive list of changes by version:
1043 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/index.html,v2.16},
1044 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/index.html,v2.14},
1045 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS,v2.12},
1046 @uref{http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS,v2.10},
1047 @uref{http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS,v2.8},
1048 @uref{http://lilypond.org/doc/v2.6/Documentation/topdocs/NEWS,v2.6},
1049 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS,v2.4},
1050 @uref{http://lilypond.org/doc/v2.2/Documentation/topdocs/out-www/NEWS,v2.2},
1051 @uref{http://lilypond.org/doc/v2.0/Documentation/topdocs/out-www/NEWS,v2.0},
1052 @uref{http://lilypond.org/doc/v1.8/Documentation/topdocs/out-www/NEWS,v1.8},
1053 @uref{http://lilypond.org/doc/v1.6/Documentation/out-www/NEWS,v1.6},
1054 @miscLink{NEWS-1.4,v1.4},
1055 @miscLink{NEWS-1.2,v1.2}
1059 @divClass{column-center-middle-color3}
1062 Thanks to developers, contributors, bug hunters and suggestions for
1063 @miscLink{THANKS-2.16,v2.16},
1064 @miscLink{THANKS-2.14,v2.14},
1065 @miscLink{THANKS-2.12,v2.12},
1066 @miscLink{THANKS-2.10,v2.10},
1067 @miscLink{THANKS-2.8,v2.8},
1068 @miscLink{THANKS-2.6,v2.6},
1069 @miscLink{THANKS-2.4,v2.4},
1070 @miscLink{THANKS-2.2,v2.2},
1071 @miscLink{THANKS-2.0,v2.0},
1072 @miscLink{THANKS-1.8,v1.8}
1076 @divClass{column-center-middle-color3}
1077 @subheading Changelogs
1079 Developers' changelogs by version:
1080 @miscLink{ChangeLog-2.10,v2.10},
1081 @miscLink{ChangeLog-2.3,v2.3},
1082 @miscLink{ChangeLog-2.1,v2.1},
1083 @miscLink{ChangeLog-1.5,v1.5 (1)},
1084 @miscLink{CHANGES-1.5,v1.5 (2)},
1085 @miscLink{CHANGES-1.4,v1.4},
1086 @miscLink{CHANGES-1.3,v1.3},
1087 @miscLink{CHANGES-1.2,v1.2},
1088 @miscLink{CHANGES-1.1,v1.1},
1089 @miscLink{CHANGES-1.0,v1.0},
1090 @miscLink{CHANGES-0.1,v0.1},
1091 @miscLink{CHANGES-0.0,v0.0}
1095 @divClass{column-center-middle-color2 bigger-subsubheadings}
1099 @divClass{column-center-middle-color2}
1100 @subheading Old News
1102 Older news items dating back to July 2003. Newer news can be found on
1103 the @ref{News} page.
1106 @include web/news-old.itexi