-This package was Debianized by Anthony Fok <foka@debian.org> on
-Wed, 6 Aug 1997 04:30:28 -0600
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: lilypond
+Upstream-Contact: lilypond-devel@gnu.org
+Source: http://www.lilypond.org/
-The development branch, lilypond1.3, is packaged separately
-on Tue, 9 Nov 1999 22:30:32 -0700
+Files: *
+Copyright: 1993--2012, Han-Wen Nienhuys <hanwen@lilypond.org>
+ 1996--2012, Jan Nieuwenhuizen <janneke@gnu.org>
+License: GPL-3+
-It was downloaded from
- ftp://ftp.lilypond.org/pub/LilyPond/v1.3/lilypond-1.3.45.tar.gz
+Files: debian/*
+Copyright: 2009-2014 Don Armstrong <don@debian.org>
+ 2005-2008 Thomas Bushnell, BSG <tb@debian.org>
+ 2016 Dr. Tobias Quathamer <toddy@debian.org>
+ 1997-2004, 2017 Anthony Fok <foka@debian.org>
+License: GPL-2+
-It is also available at:
- ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/v1.3/lilypond-1.3.45.tar.gz
+Files: Documentation/*
+Copyright: Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
+License: GFDL-1.3+
-For more information about GNU LilyPond, please visit:
- http://www.cs.uu.nl/~hanwen/lilypond/
- or http://www.xs4all.nl/~jantien/
- or http://www.lilypond.org/
- or http://sca.uwaterloo.ca/lilypond/
+Files: Documentation/snippet
+Copyright: Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
+License: GFDL-1.3+
-Authors:
- Han-Wen Nienhuys <hanwen@cs.uu.nl>
- Jan Nieuwenhuizen <janneke@gnu.org>
-
-Copyright:
+Files: input/regression/musicxml/*
+Copyright: 2008-2010, Reinhold Kainhofer
+License: MIT
- GNU LilyPond is Copyright (C) 1996-2000
- Jan Nieuwenhuizen & Han-Wen Nienhuys
+Files: mf/*
+Copyright: 1996--2014, The LilyPond authors (lilypond.org)
+License: OFL-1.1
+Comment: with Reserved Font Name "Emmentaler" and "Feta".
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
+Files: flower/include/matrix.hh
+ lily/constrained-breaking.cc
+ lily/include/constrained-breaking.hh
+ lily/include/one-line-page-breaking.hh
+ lily/include/optimal-page-breaking.hh
+ lily/include/page-breaking.hh
+ lily/include/page-layout-problem.hh
+ lily/include/page-spacing.hh
+ lily/include/page-turn-page-breaking.hh
+ lily/include/skyline.hh
+ lily/include/staff-grouper-interface.hh
+ lily/keep-alive-together-engraver.cc
+ lily/one-line-page-breaking.cc
+ lily/optimal-page-breaking.cc
+ lily/page-breaking-scheme.cc
+ lily/page-breaking.cc
+ lily/page-layout-problem-scheme.cc
+ lily/page-layout-problem.cc
+ lily/page-spacing.cc
+ lily/page-turn-engraver.cc
+ lily/page-turn-page-breaking.cc
+ lily/skyline.cc
+ lily/spacing-interface.cc
+ lily/spring.cc
+ lily/staff-grouper-interface.cc
+Copyright: 2006--2012, Joe Neeman <joeneeman@gmail.com>
+ 2007--2012, Joe Neeman <joeneeman@gmail.com>
+ 2009--2012, Joe Neeman <joeneeman@gmail.com>
+ 2010--2012, Joe Neeman <joeneeman@gmail.com>
+ 2011--2012, Joe Neeman <joeneeman@gmail.com>
+ 2012, Joe Neeman <joeneeman@gmail.com>
+License: GPL-3+
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+Files: lily/ambitus-engraver.cc
+ lily/cluster-engraver.cc
+ lily/cluster.cc
+ lily/coherent-ligature-engraver.cc
+ lily/custos-engraver.cc
+ lily/custos.cc
+ lily/gregorian-ligature-engraver.cc
+ lily/include/cluster.hh
+ lily/include/coherent-ligature-engraver.hh
+ lily/include/custos.hh
+ lily/include/gregorian-ligature-engraver.hh
+ lily/include/gregorian-ligature.hh
+ lily/include/ligature-engraver.hh
+ lily/include/mensural-ligature.hh
+ lily/include/vaticana-ligature.hh
+ lily/ligature-bracket-engraver.cc
+ lily/ligature-engraver.cc
+ lily/mensural-ligature-engraver.cc
+ lily/mensural-ligature.cc
+ lily/vaticana-ligature-engraver.cc
+ lily/vaticana-ligature.cc
+Copyright: 2000--2012, Juergen Reuter <reuter@ipd.uka.de>
+ 2002--2012, Juergen Reuter <reuter@ipd.uka.de>
+ 2003--2012, Juergen Reuter <reuter@ipd.uka.de>
+License: GPL-3+
- *** NOTE
+Files: lily/beam-collision-engraver.cc
+ lily/concurrent-hairpin-engraver.cc
+ lily/footnote-engraver.cc
+ lily/include/interval-minefield.hh
+ lily/include/pure-from-neighbor-interface.hh
+ lily/include/rhythmic-music-iterator.hh
+ lily/interval-minefield.cc
+ lily/pure-from-neighbor-engraver.cc
+ lily/pure-from-neighbor-interface.cc
+ lily/rhythmic-music-iterator.cc
+ lily/span-bar-stub-engraver.cc
+ lily/unpure-pure-container.cc
+Copyright: 2011--2012, Mike Solomon <mike@apollinemike.com>
+ 2012, Mike Solomon <mike@apollinemike.com>
+License: GPL-3+
- This license applies to all files except the included example
- input files (which are in the subdirectory input/ and mutopia/ )
+Files: lily/dispatcher-scheme.cc
+ lily/dispatcher.cc
+ lily/include/dispatcher.hh
+ lily/include/listener.hh
+ lily/include/scheme-listener.hh
+ lily/include/stream-event.hh
+ lily/listener.cc
+ lily/scheme-listener-scheme.cc
+ lily/scheme-listener.cc
+ lily/stream-event-scheme.cc
+ lily/stream-event.cc
+Copyright: 2005, Erik Sandberg <mandolaerik@gmail.com>
+ 2005--2012, Erik Sandberg <mandolaerik@gmail.com>
+ 2006--2012, Erik Sandberg <mandolaerik@gmail.com>
+License: GPL-3+
- *** END NOTE
+Files: lily/include/minimal-page-breaking.hh
+ lily/include/page-marker.hh
+ lily/minimal-page-breaking.cc
+ lily/note-column-scheme.cc
+ lily/page-marker-scheme.cc
+ lily/page-marker.cc
+Copyright: 2007--2012, Nicolas Sceaux <nicolas.sceaux@free.fr>
+ 2010--2012, Nicolas Sceaux <nicolas.sceaux@free.fr>
+License: GPL-3+
+Files: scripts/abc2ly.py
+ scripts/auxiliar/check_translation.py
+ scripts/auxiliar/fixcc.py
+ scripts/etf2ly.py
+ scripts/lilypond-book.py
+Copyright: *No copyright*
+License: GPL-3+
-All the other scripts and control files for building and installing
-GNU LilyPond under Debian GNU/Linux are also under the GNU General
-Public License (GPL) version 2 or later.
+Files: tex/txi-en.tex
+ tex/txi-fr.tex
+ tex/txi-it.tex
+ tex/txi-nl.tex
+ tex/txi-de.tex
+ tex/txi-hu.tex
+Copyright: 1999, 2007-2008, Free Software Foundation
+License: GPL-3+
-On Debian GNU/Linux systems, the complete text of the GNU General
-Public License can be found in `/usr/share/common-licenses/GPL'.
+Files: lily/extender-engraver.cc
+ lily/hyphen-engraver.cc
+ lily/include/lyric-hyphen.hh
+Copyright: 1999--2012, Glen Prideaux <glenprideaux@iname.com>
+License: GPL-3+
+
+Files: lily/double-percent-repeat-engraver.cc
+ lily/episema-engraver.cc
+ lily/partial-iterator.cc
+Copyright: 2010--2012, Neil Puttock <n.puttock@gmail.com>
+ 2011--2012, Neil Puttock <n.puttock@gmail.com>
+License: GPL-3+
+
+Files: lily/context-mod.cc
+ lily/include/context-mod.hh
+ lily/pdf-scheme.cc
+Copyright: 2010--2012, Reinhold Kainhofer <reinhold@kainhofer.com>
+License: GPL-3+
+
+Files: lily/out/parser.cc
+ lily/out/parser.hh
+Copyright: 1984, 1989-1990, 2000-2006 Free Software Foundation
+License: GPL-2+
+
+Files: scripts/lilymidi.py
+ scripts/lilysong.py
+Copyright: 2006--2012, Brailcom, o.p.s
+License: GPL-3+
+
+Files: lily/articulations.cc
+ lily/include/articulations.hh
+Copyright: 2010--2012, Carl Sorensen <c_sorensen@byu.edu>
+License: GPL-3+
+
+Files: elisp/lilypond-mode.el
+ lily/include/lyric-extender.hh
+Copyright: 1998--2012, Jan Nieuwenhuizen <janneke@gnu.org>
+ 1999--2012, Jan Nieuwenhuizen <janneke@gnu.org>
+License: GPL-3+
+
+Files: flower/include/yaffut.hh
+Copyright: 2006, Rutger E.W. van Beusekom
+License: BSL-1.0
+
+Files: scripts/build/help2man.pl
+Copyright: 1997-2002, Free Software
+ 1997-2002, Free Software Foundation, Inc
+License: GPL-2+
+
+Files: tex/texinfo.tex
+Copyright: 1985-1986, 1988, 1990-1995
+License: GPL-3+
+
+Files: scripts/convert-ly.py
+Copyright: 1998--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>
+ = ('Jan Nieuwenhuizen <janneke@gnu.org>'
+License: GPL-3+
+
+Files: tex/txi-es.tex
+Copyright: 1999, 2007-2008, Adrian Perez Jorge
+License: GPL-3+
+
+Files: lily/tab-tie-follow-engraver.cc
+Copyright: 2010--2012, Carl D. Sorensen
+License: GPL-3+
+
+Files: scripts/build/yyout2grammar.py
+Copyright: 2005, Carl D. Sorensen <c_sorensen@byu.edu>
+License: GPL-3+
+
+Files: lily/cue-clef-engraver.cc
+Copyright: 1997--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>
+ 2010--2012, Reinhold Kainhofer <reinhold@kainhofer.com>
+License: GPL-3+
+
+Files: lily/slash-repeat-engraver.cc
+Copyright: 2000--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>, Erik Sandberg <mandolaerik@gmail.com>
+License: GPL-3+
+
+Files: lily/percent-repeat-engraver.cc
+Copyright: 2000--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>, Erik Sandberg <mandolaerik@gmail.com>
+License: GPL-3+
+
+Files: lily/stanza-number-engraver.cc
+Copyright: 2000--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>, Glen Prideaux <glenprideaux@iname.com>
+License: GPL-3+
+
+Files: flower/getopt-long.cc
+Copyright: 1996--2012, Han-Wen Nienhuys, <hanwen@xs4all.nl>
+License: GPL-3+
+
+Files: lily/tab-note-heads-engraver.cc
+Copyright: 2002--2012, Han-Wen Nienhuys, Jean-Baptiste Lamy <jiba@tuxfamily.org>
+License: GPL-3+
+
+Files: lily/breathing-sign.cc
+Copyright: 1999--2012, Michael Krause
+ 2003--2012, Juergen Reuter
+License: GPL-3+
+
+Files: lily/breathing-sign-engraver.cc
+Copyright: 1999--2012, Michael Krause
+License: GPL-3+
+
+Files: lily/forbid-break-engraver.cc
+Copyright: 2002--_2005 Han-Wen Nienhuys <hanwen@xs4all.nl>
+License: GPL-3+
+
+Files: scripts/auxiliar/makelsr.py
+Copyright: *No copyright*
+License: GPL-3+
+
+Files: elisp/lilypond-font-lock.el
+Copyright: 1997: Han-Wen Nienhuys, 1995-1996 Barry A. Warsaw,1992-1994 Tim Peters
+License: GPL-3+
+
+Files: elisp/lilypond-song.el
+Copyright: 2006, Brailcom, o.p.s
+License: GPL-3+
+
+Files: lily/include/breathing-sign.hh
+Copyright: 1999--2012, Michael Krause
+License: GPL-3+
+
+Files: scripts/build/mf2pt1.pl
+Copyright: 2012, Scott Pakin
+License: LPPL-1.3c+
+
+Files: scripts/build/website_post.py
+Copyright: UNKNOWN
+License: GPL-3+
+
+
+License: BSL-1.0
+ Boost Software License - Version 1.0 - August 17th, 2003
+ .
+ Permission is hereby granted, free of charge, to any person or organization
+ obtaining a copy of the software and accompanying documentation covered by
+ this license (the "Software") to use, reproduce, display, distribute,
+ execute, and transmit the Software, and to prepare derivative works of the
+ Software, and to permit third-parties to whom the Software is furnished to
+ do so, all subject to the following:
+ .
+ The copyright notices in the Software and this entire statement, including
+ the above license grant, this restriction and the following disclaimer,
+ must be included in all copies of the Software, in whole or in part, and
+ all derivative works of the Software, unless such copies or derivative
+ works are solely in the form of machine-executable object code generated by
+ a source language processor.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
+ SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
+ FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
+ ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.
+
+License: GFDL-1.3+
+ Permission is granted to copy, distribute and/or modify the
+ documentation for GNU LilyPond under the terms of the GNU Free
+ Documentation License as published by the Free Software Foundation,
+ either version 1.3, or (at your option) any later version; with no
+ Invariant Sections, no Front-Cover Texts and no Back-Cover Texts.
+ .
+ On Debian systems, the complete text of version 1.3 of the GNU Free
+ Documenation License can be found in
+ `/usr/share/common-licenses/GFDL-1.3'.
+
+
+License: GPL-3+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+ .
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+ .
+ On Debian systems, the complete text of version 3 of the GNU General
+ Public License can be found in `/usr/share/common-licenses/GPL-3'.
+
+License: GPL-2+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 2 of the License, or
+ (at your option) any later version.
+ .
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ .
+ On Debian systems, the complete text of version 2 of the GNU General
+ Public License can be found in `/usr/share/common-licenses/GPL-2'.
+
+
+License: LPPL-1.3c+
+ The LaTeX Project Public License
+ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+ .
+ LPPL Version 1.3c 2008-05-04
+ .
+ Copyright 1999 2002-2008 LaTeX3 Project
+ Everyone is allowed to distribute verbatim copies of this
+ license document, but modification of it is not allowed.
+ .
+ .
+ PREAMBLE
+ ========
+ .
+ The LaTeX Project Public License (LPPL) is the primary license under
+ which the LaTeX kernel and the base LaTeX packages are distributed.
+ .
+ You may use this license for any work of which you hold the copyright
+ and which you wish to distribute. This license may be particularly
+ suitable if your work is TeX-related (such as a LaTeX package), but
+ it is written in such a way that you can use it even if your work is
+ unrelated to TeX.
+ .
+ The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+ below, gives instructions, examples, and recommendations for authors
+ who are considering distributing their works under this license.
+ .
+ This license gives conditions under which a work may be distributed
+ and modified, as well as conditions under which modified versions of
+ that work may be distributed.
+ .
+ We, the LaTeX3 Project, believe that the conditions below give you
+ the freedom to make and distribute modified versions of your work
+ that conform with whatever technical specifications you wish while
+ maintaining the availability, integrity, and reliability of
+ that work. If you do not see how to achieve your goal while
+ meeting these conditions, then read the document `cfgguide.tex'
+ and `modguide.tex' in the base LaTeX distribution for suggestions.
+ .
+ .
+ DEFINITIONS
+ ===========
+ .
+ In this license document the following terms are used:
+ .
+ `Work'
+ Any work being distributed under this License.
+ . `Derived Work'
+ Any work that under any applicable law is derived from the Work.
+ .
+ `Modification'
+ Any procedure that produces a Derived Work under any applicable
+ law -- for example, the production of a file containing an
+ original file associated with the Work or a significant portion of
+ such a file, either verbatim or with modifications and/or
+ translated into another language.
+ .
+ `Modify'
+ To apply any procedure that produces a Derived Work under any
+ applicable law.
+ . `Distribution'
+ Making copies of the Work available from one person to another, in
+ whole or in part. Distribution includes (but is not limited to)
+ making any electronic components of the Work accessible by
+ file transfer protocols such as FTP or HTTP or by shared file
+ systems such as Sun's Network File System (NFS).
+ .
+ `Compiled Work'
+ A version of the Work that has been processed into a form where it
+ is directly usable on a computer system. This processing may
+ include using installation facilities provided by the Work,
+ transformations of the Work, copying of components of the Work, or
+ other activities. Note that modification of any installation
+ facilities provided by the Work constitutes modification of the Work.
+ .
+ `Current Maintainer'
+ A person or persons nominated as such within the Work. If there is
+ no such explicit nomination then it is the `Copyright Holder' under
+ any applicable law.
+ .
+ `Base Interpreter'
+ A program or process that is normally needed for running or
+ interpreting a part or the whole of the Work.
+ .
+ A Base Interpreter may depend on external components but these
+ are not considered part of the Base Interpreter provided that each
+ external component clearly identifies itself whenever it is used
+ interactively. Unless explicitly specified when applying the
+ license to the Work, the only applicable Base Interpreter is a
+ `LaTeX-Format' or in the case of files belonging to the
+ `LaTeX-format' a program implementing the `TeX language'.
+ .
+ .
+ .
+ CONDITIONS ON DISTRIBUTION AND MODIFICATION
+ ===========================================
+ .
+ 1. Activities other than distribution and/or modification of the Work
+ are not covered by this license; they are outside its scope. In
+ particular, the act of running the Work is not restricted and no
+ requirements are made concerning any offers of support for the Work.
+ .
+ 2. You may distribute a complete, unmodified copy of the Work as you
+ received it. Distribution of only part of the Work is considered
+ modification of the Work, and no right to distribute such a Derived
+ Work may be assumed under the terms of this clause.
+ .
+ 3. You may distribute a Compiled Work that has been generated from a
+ complete, unmodified copy of the Work as distributed under Clause 2
+ above, as long as that Compiled Work is distributed in such a way that
+ the recipients may install the Compiled Work on their system exactly
+ as it would have been installed if they generated a Compiled Work
+ directly from the Work.
+ .
+ 4. If you are the Current Maintainer of the Work, you may, without
+ restriction, modify the Work, thus creating a Derived Work. You may
+ also distribute the Derived Work without restriction, including
+ Compiled Works generated from the Derived Work. Derived Works
+ distributed in this manner by the Current Maintainer are considered to
+ be updated versions of the Work.
+ .
+ 5. If you are not the Current Maintainer of the Work, you may modify
+ your copy of the Work, thus creating a Derived Work based on the Work,
+ and compile this Derived Work, thus creating a Compiled Work based on
+ the Derived Work.
+ .
+ 6. If you are not the Current Maintainer of the Work, you may
+ distribute a Derived Work provided the following conditions are met
+ for every component of the Work unless that component clearly states
+ in the copyright notice that it is exempt from that condition. Only
+ the Current Maintainer is allowed to add such statements of exemption
+ to a component of the Work.
+ .
+ a. If a component of this Derived Work can be a direct replacement
+ for a component of the Work when that component is used with the
+ Base Interpreter, then, wherever this component of the Work
+ identifies itself to the user when used interactively with that
+ Base Interpreter, the replacement component of this Derived Work
+ clearly and unambiguously identifies itself as a modified version
+ of this component to the user when used interactively with that
+ Base Interpreter.
+ . b. Every component of the Derived Work contains prominent notices
+ detailing the nature of the changes to that component, or a
+ prominent reference to another file that is distributed as part
+ of the Derived Work and that contains a complete and accurate log
+ of the changes.
+ . c. No information in the Derived Work implies that any persons,
+ including (but not limited to) the authors of the original version
+ of the Work, provide any support, including (but not limited to)
+ the reporting and handling of errors, to recipients of the
+ Derived Work unless those persons have stated explicitly that
+ they do provide such support for the Derived Work.
+ .
+ d. You distribute at least one of the following with the Derived Work:
+ .
+ 1. A complete, unmodified copy of the Work;
+ if your distribution of a modified component is made by
+ offering access to copy the modified component from a
+ designated place, then offering equivalent access to copy
+ the Work from the same or some similar place meets this
+ condition, even though third parties are not compelled to
+ copy the Work along with the modified component;
+ .
+ 2. Information that is sufficient to obtain a complete,
+ unmodified copy of the Work.
+ .
+ 7. If you are not the Current Maintainer of the Work, you may
+ distribute a Compiled Work generated from a Derived Work, as long as
+ the Derived Work is distributed to all recipients of the Compiled
+ Work, and as long as the conditions of Clause 6, above, are met with
+ regard to the Derived Work.
+ .
+ 8. The conditions above are not intended to prohibit, and hence do not
+ apply to, the modification, by any method, of any component so that it
+ becomes identical to an updated version of that component of the Work as
+ it is distributed by the Current Maintainer under Clause 4, above.
+ .
+ 9. Distribution of the Work or any Derived Work in an alternative
+ format, where the Work or that Derived Work (in whole or in part) is
+ then produced by applying some process to that format, does not relax or
+ nullify any sections of this license as they pertain to the results of
+ applying that process.
+ . 10. a. A Derived Work may be distributed under a different license
+ provided that license itself honors the conditions listed in
+ Clause 6 above, in regard to the Work, though it does not have
+ to honor the rest of the conditions in this license.
+ . b. If a Derived Work is distributed under a different license, that
+ Derived Work must provide sufficient documentation as part of
+ itself to allow each recipient of that Derived Work to honor the
+ restrictions in Clause 6 above, concerning changes from the Work.
+ .
+ 11. This license places no restrictions on works that are unrelated to
+ the Work, nor does this license place any restrictions on aggregating
+ such works with the Work by any means.
+ .
+ 12. Nothing in this license is intended to, or may be used to, prevent
+ complete compliance by all parties with all applicable laws.
+ .
+ .
+ NO WARRANTY
+ ===========
+ .
+ There is no warranty for the Work. Except when otherwise stated in
+ writing, the Copyright Holder provides the Work `as is', without
+ warranty of any kind, either expressed or implied, including, but not
+ limited to, the implied warranties of merchantability and fitness for a
+ particular purpose. The entire risk as to the quality and performance
+ of the Work is with you. Should the Work prove defective, you assume
+ the cost of all necessary servicing, repair, or correction.
+ .
+ In no event unless required by applicable law or agreed to in writing
+ will The Copyright Holder, or any author named in the components of the
+ Work, or any other party who may distribute and/or modify the Work as
+ permitted above, be liable to you for damages, including any general,
+ special, incidental or consequential damages arising out of any use of
+ the Work or out of inability to use the Work (including, but not limited
+ to, loss of data, data being rendered inaccurate, or losses sustained by
+ anyone as a result of any failure of the Work to operate with any other
+ programs), even if the Copyright Holder or said author or said other
+ party has been advised of the possibility of such damages.
+ .
+ .
+ MAINTENANCE OF THE WORK
+ =======================
+ .
+ The Work has the status `author-maintained' if the Copyright Holder
+ explicitly and prominently states near the primary copyright notice in
+ the Work that the Work can only be maintained by the Copyright Holder
+ or simply that it is `author-maintained'.
+ .
+ The Work has the status `maintained' if there is a Current Maintainer
+ who has indicated in the Work that they are willing to receive error
+ reports for the Work (for example, by supplying a valid e-mail
+ address). It is not required for the Current Maintainer to acknowledge
+ or act upon these error reports.
+ .
+ The Work changes from status `maintained' to `unmaintained' if there
+ is no Current Maintainer, or the person stated to be Current
+ Maintainer of the work cannot be reached through the indicated means
+ of communication for a period of six months, and there are no other
+ significant signs of active maintenance.
+ .
+ You can become the Current Maintainer of the Work by agreement with
+ any existing Current Maintainer to take over this role.
+ .
+ If the Work is unmaintained, you can become the Current Maintainer of
+ the Work through the following steps:
+ .
+ 1. Make a reasonable attempt to trace the Current Maintainer (and
+ the Copyright Holder, if the two differ) through the means of
+ an Internet or similar search.
+ .
+ 2. If this search is successful, then enquire whether the Work
+ is still maintained.
+ .
+ a. If it is being maintained, then ask the Current Maintainer
+ to update their communication data within one month.
+ . b. If the search is unsuccessful or no action to resume active
+ maintenance is taken by the Current Maintainer, then announce
+ within the pertinent community your intention to take over
+ maintenance. (If the Work is a LaTeX work, this could be
+ done, for example, by posting to comp.text.tex.)
+ .
+ 3a. If the Current Maintainer is reachable and agrees to pass
+ maintenance of the Work to you, then this takes effect
+ immediately upon announcement.
+ .
+ b. If the Current Maintainer is not reachable and the Copyright
+ Holder agrees that maintenance of the Work be passed to you,
+ then this takes effect immediately upon announcement.
+ .
+ 4. If you make an `intention announcement' as described in 2b. above
+ and after three months your intention is challenged neither by
+ the Current Maintainer nor by the Copyright Holder nor by other
+ people, then you may arrange for the Work to be changed so as
+ to name you as the (new) Current Maintainer.
+ .
+ 5. If the previously unreachable Current Maintainer becomes
+ reachable once more within three months of a change completed
+ under the terms of 3b) or 4), then that Current Maintainer must
+ become or remain the Current Maintainer upon request provided
+ they then update their communication data within one month.
+ .
+ A change in the Current Maintainer does not, of itself, alter the fact
+ that the Work is distributed under the LPPL license.
+ .
+ If you become the Current Maintainer of the Work, you should
+ immediately provide, within the Work, a prominent and unambiguous
+ statement of your status as Current Maintainer. You should also
+ announce your new status to the same pertinent community as
+ in 2b) above.
+ .
+ .
+ WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+ ======================================================
+ .
+ This section contains important instructions, examples, and
+ recommendations for authors who are considering distributing their
+ works under this license. These authors are addressed as `you' in
+ this section.
+ .
+ Choosing This License or Another License
+ ----------------------------------------
+ .
+ If for any part of your work you want or need to use *distribution*
+ conditions that differ significantly from those in this license, then
+ do not refer to this license anywhere in your work but, instead,
+ distribute your work under a different license. You may use the text
+ of this license as a model for your own license, but your license
+ should not refer to the LPPL or otherwise give the impression that
+ your work is distributed under the LPPL.
+ .
+ The document `modguide.tex' in the base LaTeX distribution explains
+ the motivation behind the conditions of this license. It explains,
+ for example, why distributing LaTeX under the GNU General Public
+ License (GPL) was considered inappropriate. Even if your work is
+ unrelated to LaTeX, the discussion in `modguide.tex' may still be
+ relevant, and authors intending to distribute their works under any
+ license are encouraged to read it.
+ .
+ A Recommendation on Modification Without Distribution
+ -----------------------------------------------------
+ .
+ It is wise never to modify a component of the Work, even for your own
+ personal use, without also meeting the above conditions for
+ distributing the modified component. While you might intend that such
+ modifications will never be distributed, often this will happen by
+ accident -- you may forget that you have modified that component; or
+ it may not occur to you when allowing others to access the modified
+ version that you are thus distributing it and violating the conditions
+ of this license in ways that could have legal implications and, worse,
+ cause problems for the community. It is therefore usually in your
+ best interest to keep your copy of the Work identical with the public
+ one. Many works provide ways to control the behavior of that work
+ without altering any of its licensed components.
+ .
+ How to Use This License
+ -----------------------
+ .
+ To use this license, place in each of the components of your work both
+ an explicit copyright notice including your name and the year the work
+ was authored and/or last substantially modified. Include also a
+ statement that the distribution and/or modification of that
+ component is constrained by the conditions in this license.
+ .
+ Here is an example of such a notice and statement:
+ .
+ %% pig.dtx
+ %% Copyright 2005 M. Y. Name
+ %
+ % This work may be distributed and/or modified under the
+ % conditions of the LaTeX Project Public License, either version 1.3
+ % of this license or (at your option) any later version.
+ % The latest version of this license is in
+ % http://www.latex-project.org/lppl.txt
+ % and version 1.3 or later is part of all distributions of LaTeX
+ % version 2005/12/01 or later.
+ %
+ % This work has the LPPL maintenance status `maintained'.
+ %
+ % The Current Maintainer of this work is M. Y. Name.
+ %
+ % This work consists of the files pig.dtx and pig.ins
+ % and the derived file pig.sty.
+ .
+ Given such a notice and statement in a file, the conditions
+ given in this license document would apply, with the `Work' referring
+ to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+ generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+ referring to any `LaTeX-Format', and both `Copyright Holder' and
+ `Current Maintainer' referring to the person `M. Y. Name'.
+ .
+ If you do not want the Maintenance section of LPPL to apply to your
+ Work, change `maintained' above into `author-maintained'.
+ However, we recommend that you use `maintained', as the Maintenance
+ section was added in order to ensure that your Work remains useful to
+ the community even when you can no longer maintain and support it
+ yourself.
+ .
+ Derived Works That Are Not Replacements
+ ---------------------------------------
+ .
+ Several clauses of the LPPL specify means to provide reliability and
+ stability for the user community. They therefore concern themselves
+ with the case that a Derived Work is intended to be used as a
+ (compatible or incompatible) replacement of the original Work. If
+ this is not the case (e.g., if a few lines of code are reused for a
+ completely different task), then clauses 6b and 6d shall not apply.
+ .
+ .
+ Important Recommendations
+ -------------------------
+ .
+ Defining What Constitutes the Work
+ .
+ The LPPL requires that distributions of the Work contain all the
+ files of the Work. It is therefore important that you provide a
+ way for the licensee to determine which files constitute the Work.
+ This could, for example, be achieved by explicitly listing all the
+ files of the Work near the copyright notice of each file or by
+ using a line such as:
+ .
+ % This work consists of all files listed in manifest.txt.
+ .
+ in that place. In the absence of an unequivocal list it might be
+ impossible for the licensee to determine what is considered by you
+ to comprise the Work and, in such a case, the licensee would be
+ entitled to make reasonable conjectures as to which files comprise
+ the Work.
+
+
+License: MIT
+ Permission is hereby granted, free of charge, to any person obtaining a copy
+ of this software and associated documentation files (the "Software"), to deal
+ in the Software without restriction, including without limitation the rights
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+ copies of the Software, and to permit persons to whom the Software is
+ furnished to do so, subject to the following conditions:
+ .
+ The above copyright notice and this permission notice shall be included in
+ all copies or substantial portions of the Software.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+ THE SOFTWARE.
+
+License: OFL-1.1
+ This Font Software is licensed under the SIL Open Font License, Version 1.1.
+ .
+ This license is copied below, and is also available with a FAQ at:
+ http://scripts.sil.org/OFL
+ .
+ SIL OPEN FONT LICENSE
+ .
+ Version 1.1 - 26 February 2007
+ .
+ PREAMBLE
+ The goals of the Open Font License (OFL) are to stimulate worldwide
+ development of collaborative font projects, to support the font creation
+ efforts of academic and linguistic communities, and to provide a free and
+ open framework in which fonts may be shared and improved in partnership
+ with others.
+ .
+ The OFL allows the licensed fonts to be used, studied, modified and
+ redistributed freely as long as they are not sold by themselves. The
+ fonts, including any derivative works, can be bundled, embedded,
+ redistributed and/or sold with any software provided that any reserved
+ names are not used by derivative works. The fonts and derivatives,
+ however, cannot be released under any other type of license. The
+ requirement for fonts to remain under this license does not apply
+ to any document created using the fonts or their derivatives.
+ .
+ DEFINITIONS
+ "Font Software" refers to the set of files released by the Copyright
+ Holder(s) under this license and clearly marked as such. This may
+ include source files, build scripts and documentation.
+ .
+ "Reserved Font Name" refers to any names specified as such after the
+ copyright statement(s).
+ .
+ "Original Version" refers to the collection of Font Software components as
+ distributed by the Copyright Holder(s).
+ .
+ "Modified Version" refers to any derivative made by adding to, deleting,
+ or substituting -- in part or in whole -- any of the components of the
+ Original Version, by changing formats or by porting the Font Software to a
+ new environment.
+ .
+ "Author" refers to any designer, engineer, programmer, technical
+ writer or other person who contributed to the Font Software.
+ .
+ PERMISSION & CONDITIONS
+ Permission is hereby granted, free of charge, to any person obtaining
+ a copy of the Font Software, to use, study, copy, merge, embed, modify,
+ redistribute, and sell modified and unmodified copies of the Font
+ Software, subject to the following conditions:
+ .
+ 1) Neither the Font Software nor any of its individual components,
+ in Original or Modified Versions, may be sold by itself.
+ .
+ 2) Original or Modified Versions of the Font Software may be bundled,
+ redistributed and/or sold with any software, provided that each copy
+ contains the above copyright notice and this license. These can be
+ included either as stand-alone text files, human-readable headers or
+ in the appropriate machine-readable metadata fields within text or
+ binary files as long as those fields can be easily viewed by the user.
+ .
+ 3) No Modified Version of the Font Software may use the Reserved Font
+ Name(s) unless explicit written permission is granted by the corresponding
+ Copyright Holder. This restriction only applies to the primary font name as
+ presented to the users.
+ .
+ 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+ Software shall not be used to promote, endorse or advertise any
+ Modified Version, except to acknowledge the contribution(s) of the
+ Copyright Holder(s) and the Author(s) or with their explicit written
+ permission.
+ .
+ 5) The Font Software, modified or unmodified, in part or in whole,
+ must be distributed entirely under this license, and must not be
+ distributed under any other license. The requirement for fonts to
+ remain under this license does not apply to any document created
+ using the Font Software.
+ .
+ TERMINATION
+ This license becomes null and void if any of the above conditions are
+ not met.
+ .
+ DISCLAIMER
+ THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+ OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+ COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+ DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+ OTHER DEALINGS IN THE FONT SOFTWARE.
projects / lilypond.git / blobdiff