| 1 |
Copyright information for the texlive bundle |
| 2 |
|
| 3 |
Table of contents: |
| 4 |
|
| 5 |
1. Copyright and License of the debian-specific adaptions |
| 6 |
2. License of the TeX live distribution as a compilation work |
| 7 |
3. Licenses of individual parts |
| 8 |
3.1 Explanation of the format of the following information |
| 9 |
3.2 Packages with license problems |
| 10 |
3.3 Individual license texts |
| 11 |
3.4 (Incomplete) list of licenses of individual parts |
| 12 |
|
| 13 |
|
| 14 |
1. Copyright and License of the debian-specific adaptions |
| 15 |
|
| 16 |
Debian adaptions for these packages are licensed under the GNU General |
| 17 |
Public License, version 2, and are under Copyright by: |
| 18 |
|
| 19 |
Norbert Preining <[email protected]> (2005-) |
| 20 |
Frank Küster <[email protected]> (2006-) |
| 21 |
|
| 22 |
All code generated for the Debian adaptions is under the GNU General |
| 23 |
Public License. |
| 24 |
|
| 25 |
-------- |
| 26 |
|
| 27 |
2. License of the TeX live distribution as a compilation work |
| 28 |
|
| 29 |
COPYING CONDITIONS FOR TeX Live: |
| 30 |
|
| 31 |
To the best of our knowledge, all software in this distribution is |
| 32 |
freely redistributable (libre, that is, not necessarily gratis), within |
| 33 |
the Free Software Foundation's definition and Debian Free Software |
| 34 |
Guidelines. If you find any non-free files included, please contact us |
| 35 |
(references given below). |
| 36 |
|
| 37 |
That said, TeX Live has neither a single copyright holder nor a single |
| 38 |
license covering its entire contents, since it is a collection of many |
| 39 |
disparate packages. Therefore, you may copy, modify, and/or |
| 40 |
redistribute software from TeX Live only if you comply with the |
| 41 |
requirements placed thereon by the owners of the respective packages. |
| 42 |
|
| 43 |
To most easily learn these requirements, we suggest checking the TeX |
| 44 |
Catalogue at: http://www.ctan.org/tex-archive/help/Catalogue/ (or any |
| 45 |
CTAN mirror). The Catalogue is also included in TeX Live in |
| 46 |
./texmf/doc/html/catalogue/, but the online version will have updates. |
| 47 |
Of course the legal statements within the packages themselves are the |
| 48 |
final authority. |
| 49 |
|
| 50 |
In some cases, TeX Live is distributed with a snapshot of the CTAN |
| 51 |
archive, which is entirely independent of and separable from TeX Live |
| 52 |
itself. (The "live" DVD in the TeX Collection is one example of this.) |
| 53 |
Please be aware that the CTAN snapshot contains many files which are |
| 54 |
*not* freely redistributable; see LICENSE.CTAN for more information. |
| 55 |
|
| 56 |
|
| 57 |
GUIDELINES FOR REDISTRIBUTION: |
| 58 |
|
| 59 |
In general, you may redistribute TeX Live, with or without modification, |
| 60 |
for profit or not, according to the usual free software tenets. Here |
| 61 |
are some general guidelines for doing this: |
| 62 |
|
| 63 |
- If you make any changes to the TeX Live distribution or any |
| 64 |
package it contains, besides complying with any licensing requirements, |
| 65 |
you must prominently mention such changes in your modified distribution |
| 66 |
so that users do not take your work for ours, and know to contact you, |
| 67 |
not us, in case of questions or problems. A new top-level |
| 68 |
README.<yourwork> file is a good place to describe the general situation. |
| 69 |
|
| 70 |
- Especially (but not necessarily) if changes or additions are made, we |
| 71 |
recommend a clearly different title, such as "<your work> demo CD", |
| 72 |
based on TeX Live YYYY demo (with updates)", where YYYY is the year of |
| 73 |
TeX Live you are publishing. This credits both our work and yours. |
| 74 |
|
| 75 |
- You absolutely may *not* place your own copyright on the entire |
| 76 |
distribution, since it is not your work (as stated above, TeX Live is |
| 77 |
not created by any single person or entity). Statements such as "all |
| 78 |
rights reserved" and "may not be reproduced" are especially |
| 79 |
reprehensible, since they are antithetical to the free software |
| 80 |
principles under which TeX Live is produced. |
| 81 |
|
| 82 |
- You may use any cover or media label designs that you wish. Such |
| 83 |
packaging and marketing details are not covered by any TeX Live license. |
| 84 |
|
| 85 |
- Finally, we make the following requests (not legal requirements): |
| 86 |
|
| 87 |
a) Acknowledging that TeX Live is developed as a joint effort by all TeX |
| 88 |
user groups, and encouraging the user/reader to join their user group |
| 89 |
of choice. |
| 90 |
|
| 91 |
The web page http://www.tug.org/usergroups.html may be referenced as |
| 92 |
a list of TeX user groups. We also appreciate your explicitly |
| 93 |
listing all the user groups as given on that page, space permitting. |
| 94 |
|
| 95 |
b) Referencing the TeX Live home page: http://www.tug.org/tex-live/. |
| 96 |
|
| 97 |
c) Crediting the editor of the original TeX Live: Sebastian Rahtz. |
| 98 |
|
| 99 |
Such credits may be placed on the label of your media, your cover, |
| 100 |
and/or in accompanying text (for instance, in the acknowledgements |
| 101 |
section of a book). |
| 102 |
|
| 103 |
Finally, although it is certainly not a requirement, we'd like to invite |
| 104 |
any redistributors to make a donation to the project, whether cash or |
| 105 |
in-kind, for example via https://www.tug.org/donate.html. Thanks. |
| 106 |
|
| 107 |
|
| 108 |
If you have any questions or comments, *please* contact us. In general, |
| 109 |
we appreciate being given the chance to review any TeX Live-related |
| 110 |
material in advance of publication, simply to avoid mistakes. It is |
| 111 |
much better to correct text on a CD label or in a book before thousands |
| 112 |
of copies are made! |
| 113 |
|
| 114 |
We are also happy to keep anyone planning a publication informed as to |
| 115 |
our deadlines and progress. Just let us know. However, you should be |
| 116 |
aware that TeX Live is produced entirely by volunteers, and no dates can |
| 117 |
be guaranteed. |
| 118 |
|
| 119 |
|
| 120 |
LICENSING FOR NEW PACKAGES: |
| 121 |
|
| 122 |
Finally, we are often asked what license to use for new work. To be |
| 123 |
considered for inclusion on TeX Live, a package must use a free software |
| 124 |
license, such as the LaTeX Project Public License, the GNU Public |
| 125 |
License, the X Window System license, the modified BSD license, etc., or |
| 126 |
be put into the public domain. Please see the url's below for more |
| 127 |
discussion of this. |
| 128 |
|
| 129 |
Thanks for your interest in TeX. |
| 130 |
|
| 131 |
- Sebastian Rahtz, editor, for the TeX Live team |
| 132 |
|
| 133 |
|
| 134 |
TeX Live mailing list: [email protected] |
| 135 |
TeX Live home page: http://www.tug.org/tex-live/ |
| 136 |
|
| 137 |
The FSF's free software definition: http://www.gnu.org/philosophy/free-sw.html |
| 138 |
Debian Free Software Guidelines: http://www.debian.org/intro/free |
| 139 |
FSF commentary on existing licenses: |
| 140 |
http://www.gnu.org/licenses/license-list.html |
| 141 |
|
| 142 |
LPPL: http://latex-project.org/lppl.html or texmf/doc/latex/base/lppl.txt |
| 143 |
LPPL rationale: texmf/doc/latex/base/modguide.pdf |
| 144 |
|
| 145 |
------------- |
| 146 |
|
| 147 |
3. Reference to an (incomplete) list of licenses of individual parts |
| 148 |
|
| 149 |
Individual parts of this distribution have their own copyright and |
| 150 |
license. |
| 151 |
|
| 152 |
3.1 Explanation of the format of the following information |
| 153 |
|
| 154 |
Since most packages use standard licenses, we have separated the list |
| 155 |
of license texts and the list of packages and individual files with |
| 156 |
their licenses. In section 3.3 we provide the license texts and their |
| 157 |
abbreviations used in in the file list. The file list itself is |
| 158 |
generated automatically from the TeX Catalogue and can be found, for |
| 159 |
each binary package, in /usr/share/doc/texlive-<name>/Licenses. |
| 160 |
|
| 161 |
The information in the TeX Catalogue is checked by the Debian TeX |
| 162 |
maintainers and the CTAN maintainers. If you find any contradiction |
| 163 |
in the listing with the reality please inform us. |
| 164 |
|
| 165 |
In the case of gpl and lppl, the string without a number means that |
| 166 |
the license statement contains a "or any later version" statement. In |
| 167 |
the list in Licenses, each package has a header line like this: |
| 168 |
|
| 169 |
% ccfonts: lppl (verification data:1.1:1.1:2006-03-14:frank:readme) |
| 170 |
|
| 171 |
indicating that the package ccfonts is under LPPL, exists in version |
| 172 |
1.1, the license has been checked in version 1.1 on 2006-03-14 by |
| 173 |
"frank" (the username among the Catalogue developers, actually Frank |
| 174 |
Küster), and the license information is in a file "readme". After |
| 175 |
that follows the list of files, |
| 176 |
|
| 177 |
tex/latex/ccfonts/t1ccr.fd |
| 178 |
tex/latex/ccfonts/ccfonts.sty |
| 179 |
tex/latex/ccfonts/ts1ccr.fd |
| 180 |
doc/latex/ccfonts/* |
| 181 |
|
| 182 |
where the * indicates that all ordinary files in that directory belong |
| 183 |
to that package (but not necessarily subdirectories and files |
| 184 |
therein). |
| 185 |
|
| 186 |
3.2 TODO: Packages with licensing problems |
| 187 |
|
| 188 |
[ this is copied over from teTeX, and some problems might already be |
| 189 |
solved ] |
| 190 |
|
| 191 |
3.2.1 Serious problems |
| 192 |
|
| 193 |
- euler: LPPL according changelog, but no indication in file. |
| 194 |
|
| 195 |
- adrconv: No license at all for the documentation |
| 196 |
|
| 197 |
- antp: PD according to catalogue, no statement in the files, no |
| 198 |
sources; contacted upstream |
| 199 |
|
| 200 |
- bbm: no license statement at all, bug filed |
| 201 |
|
| 202 |
- cite: chapterbib.sty is missing a license statement in the header |
| 203 |
|
| 204 |
- Problematic files by Donald Arseneau: |
| 205 |
|
| 206 |
* chapterbib.sty: no license information |
| 207 |
* tabls.sty: no license information |
| 208 |
* import.sty: "this software is free of any restrictions" |
| 209 |
* relsize.sty: "public domain", nothing else |
| 210 |
* shapepar.sty: noncommercial |
| 211 |
* version.sty: no license information, not only by D.A. |
| 212 |
* selectp.sty: no license information |
| 213 |
*./source/latex/shapepar/README.shapepar |
| 214 |
./source/latex/shapepar/shapepar.sty |
| 215 |
./source/latex/shapepar/shapepar.ltx |
| 216 |
./source/latex/hyphenat/hyphenat.dtx: no license information |
| 217 |
|
| 218 |
|
| 219 |
- citesort.sty: no license statement |
| 220 |
|
| 221 |
- index.doc: no license statement - probably unused |
| 222 |
|
| 223 |
- dinbrief: lppl 1.1+, but with additional restrictions which are non-free |
| 224 |
|
| 225 |
- eepic: The style files are public domain, but all the documentation |
| 226 |
has no license at all. |
| 227 |
|
| 228 |
- extsizes: extsizes.sty, extarticle.cls and extreport.cls, and the |
| 229 |
size*.clo files have a correct LPPL notice, the others have none. |
| 230 |
The author seems to be active on Wikipedia, tried to contact him |
| 231 |
|
| 232 |
- beamericon*: no license statement. beamerexample-seminar: just like |
| 233 |
seminar, which has not been investigated yet. Filed bug against beamer. |
| 234 |
|
| 235 |
- one file in the psnfss directory with unclear license: |
| 236 |
|
| 237 |
tex/latex/psnfss/8r.sty |
| 238 |
|
| 239 |
3.2.2 Normal :-) problems |
| 240 |
|
| 241 |
- listings: LPPL, plus: |
| 242 |
|
| 243 |
,---- |
| 244 |
| *Modification*advice* |
| 245 |
| |
| 246 |
| Permission is granted to modify the listings package as well as |
| 247 |
| lstdrvrs.dtx. You are not allowed to distribute a modified version of |
| 248 |
| the listings package or lstdrvrs.dtx unless you change the file names |
| 249 |
| and provide the original files. In any case it is better to contact |
| 250 |
| the address below; other users will welcome removed bugs, new |
| 251 |
| features, and additional programming languages. |
| 252 |
|
| 253 |
This is more restrictive than LPPL 1.3 (6.a and 6.d.2). The title is advice... |
| 254 |
|
| 255 |
- ae: Just a formal problem, the GPL is included, but nowhere is it |
| 256 |
explicitly stated that this license applies to the package. |
| 257 |
|
| 258 |
contacted upstream |
| 259 |
|
| 260 |
- antt: gust font license, unclear which files % contacted upstream |
| 261 |
|
| 262 |
|
| 263 |
3.3 Individual license texts |
| 264 |
|
| 265 |
The actual text of the licenses can either be found in |
| 266 |
/usr/share/common-licenses (for artistic,bsd,gpl) or in "3.2 Text of |
| 267 |
the licenses" below. For BSD-like licenses that just exchange the |
| 268 |
name of the copyright holder, we do not list the license text. |
| 269 |
|
| 270 |
A. gpl (GNU General Public License) |
| 271 |
|
| 272 |
The full text of the GPL is given in /usr/share/common-licenses/GPL-3. |
| 273 |
|
| 274 |
B. lppl (LaTeX Project Public License) |
| 275 |
|
| 276 |
The LaTeX Project Public License |
| 277 |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
| 278 |
|
| 279 |
LPPL Version 1.3c 2006-05-20 |
| 280 |
|
| 281 |
Copyright 1999 2002-2006 LaTeX3 Project |
| 282 |
Everyone is allowed to distribute verbatim copies of this |
| 283 |
license document, but modification of it is not allowed. |
| 284 |
|
| 285 |
|
| 286 |
PREAMBLE |
| 287 |
======== |
| 288 |
|
| 289 |
The LaTeX Project Public License (LPPL) is the primary license under |
| 290 |
which the the LaTeX kernel and the base LaTeX packages are distributed. |
| 291 |
|
| 292 |
You may use this license for any work of which you hold the copyright |
| 293 |
and which you wish to distribute. This license may be particularly |
| 294 |
suitable if your work is TeX-related (such as a LaTeX package), but |
| 295 |
it is written in such a way that you can use it even if your work is |
| 296 |
unrelated to TeX. |
| 297 |
|
| 298 |
The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE', |
| 299 |
below, gives instructions, examples, and recommendations for authors |
| 300 |
who are considering distributing their works under this license. |
| 301 |
|
| 302 |
This license gives conditions under which a work may be distributed |
| 303 |
and modified, as well as conditions under which modified versions of |
| 304 |
that work may be distributed. |
| 305 |
|
| 306 |
We, the LaTeX3 Project, believe that the conditions below give you |
| 307 |
the freedom to make and distribute modified versions of your work |
| 308 |
that conform with whatever technical specifications you wish while |
| 309 |
maintaining the availability, integrity, and reliability of |
| 310 |
that work. If you do not see how to achieve your goal while |
| 311 |
meeting these conditions, then read the document `cfgguide.tex' |
| 312 |
and `modguide.tex' in the base LaTeX distribution for suggestions. |
| 313 |
|
| 314 |
|
| 315 |
DEFINITIONS |
| 316 |
=========== |
| 317 |
|
| 318 |
In this license document the following terms are used: |
| 319 |
|
| 320 |
`Work' |
| 321 |
Any work being distributed under this License. |
| 322 |
|
| 323 |
`Derived Work' |
| 324 |
Any work that under any applicable law is derived from the Work. |
| 325 |
|
| 326 |
`Modification' |
| 327 |
Any procedure that produces a Derived Work under any applicable |
| 328 |
law -- for example, the production of a file containing an |
| 329 |
original file associated with the Work or a significant portion of |
| 330 |
such a file, either verbatim or with modifications and/or |
| 331 |
translated into another language. |
| 332 |
|
| 333 |
`Modify' |
| 334 |
To apply any procedure that produces a Derived Work under any |
| 335 |
applicable law. |
| 336 |
|
| 337 |
`Distribution' |
| 338 |
Making copies of the Work available from one person to another, in |
| 339 |
whole or in part. Distribution includes (but is not limited to) |
| 340 |
making any electronic components of the Work accessible by |
| 341 |
file transfer protocols such as FTP or HTTP or by shared file |
| 342 |
systems such as Sun's Network File System (NFS). |
| 343 |
|
| 344 |
`Compiled Work' |
| 345 |
A version of the Work that has been processed into a form where it |
| 346 |
is directly usable on a computer system. This processing may |
| 347 |
include using installation facilities provided by the Work, |
| 348 |
transformations of the Work, copying of components of the Work, or |
| 349 |
other activities. Note that modification of any installation |
| 350 |
facilities provided by the Work constitutes modification of the Work. |
| 351 |
|
| 352 |
`Current Maintainer' |
| 353 |
A person or persons nominated as such within the Work. If there is |
| 354 |
no such explicit nomination then it is the `Copyright Holder' under |
| 355 |
any applicable law. |
| 356 |
|
| 357 |
`Base Interpreter' |
| 358 |
A program or process that is normally needed for running or |
| 359 |
interpreting a part or the whole of the Work. |
| 360 |
|
| 361 |
A Base Interpreter may depend on external components but these |
| 362 |
are not considered part of the Base Interpreter provided that each |
| 363 |
external component clearly identifies itself whenever it is used |
| 364 |
interactively. Unless explicitly specified when applying the |
| 365 |
license to the Work, the only applicable Base Interpreter is a |
| 366 |
`LaTeX-Format' or in the case of files belonging to the |
| 367 |
`LaTeX-format' a program implementing the `TeX language'. |
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
CONDITIONS ON DISTRIBUTION AND MODIFICATION |
| 372 |
=========================================== |
| 373 |
|
| 374 |
1. Activities other than distribution and/or modification of the Work |
| 375 |
are not covered by this license; they are outside its scope. In |
| 376 |
particular, the act of running the Work is not restricted and no |
| 377 |
requirements are made concerning any offers of support for the Work. |
| 378 |
|
| 379 |
2. You may distribute a complete, unmodified copy of the Work as you |
| 380 |
received it. Distribution of only part of the Work is considered |
| 381 |
modification of the Work, and no right to distribute such a Derived |
| 382 |
Work may be assumed under the terms of this clause. |
| 383 |
|
| 384 |
3. You may distribute a Compiled Work that has been generated from a |
| 385 |
complete, unmodified copy of the Work as distributed under Clause 2 |
| 386 |
above, as long as that Compiled Work is distributed in such a way that |
| 387 |
the recipients may install the Compiled Work on their system exactly |
| 388 |
as it would have been installed if they generated a Compiled Work |
| 389 |
directly from the Work. |
| 390 |
|
| 391 |
4. If you are the Current Maintainer of the Work, you may, without |
| 392 |
restriction, modify the Work, thus creating a Derived Work. You may |
| 393 |
also distribute the Derived Work without restriction, including |
| 394 |
Compiled Works generated from the Derived Work. Derived Works |
| 395 |
distributed in this manner by the Current Maintainer are considered to |
| 396 |
be updated versions of the Work. |
| 397 |
|
| 398 |
5. If you are not the Current Maintainer of the Work, you may modify |
| 399 |
your copy of the Work, thus creating a Derived Work based on the Work, |
| 400 |
and compile this Derived Work, thus creating a Compiled Work based on |
| 401 |
the Derived Work. |
| 402 |
|
| 403 |
6. If you are not the Current Maintainer of the Work, you may |
| 404 |
distribute a Derived Work provided the following conditions are met |
| 405 |
for every component of the Work unless that component clearly states |
| 406 |
in the copyright notice that it is exempt from that condition. Only |
| 407 |
the Current Maintainer is allowed to add such statements of exemption |
| 408 |
to a component of the Work. |
| 409 |
|
| 410 |
a. If a component of this Derived Work can be a direct replacement |
| 411 |
for a component of the Work when that component is used with the |
| 412 |
Base Interpreter, then, wherever this component of the Work |
| 413 |
identifies itself to the user when used interactively with that |
| 414 |
Base Interpreter, the replacement component of this Derived Work |
| 415 |
clearly and unambiguously identifies itself as a modified version |
| 416 |
of this component to the user when used interactively with that |
| 417 |
Base Interpreter. |
| 418 |
|
| 419 |
b. Every component of the Derived Work contains prominent notices |
| 420 |
detailing the nature of the changes to that component, or a |
| 421 |
prominent reference to another file that is distributed as part |
| 422 |
of the Derived Work and that contains a complete and accurate log |
| 423 |
of the changes. |
| 424 |
|
| 425 |
c. No information in the Derived Work implies that any persons, |
| 426 |
including (but not limited to) the authors of the original version |
| 427 |
of the Work, provide any support, including (but not limited to) |
| 428 |
the reporting and handling of errors, to recipients of the |
| 429 |
Derived Work unless those persons have stated explicitly that |
| 430 |
they do provide such support for the Derived Work. |
| 431 |
|
| 432 |
d. You distribute at least one of the following with the Derived Work: |
| 433 |
|
| 434 |
1. A complete, unmodified copy of the Work; |
| 435 |
if your distribution of a modified component is made by |
| 436 |
offering access to copy the modified component from a |
| 437 |
designated place, then offering equivalent access to copy |
| 438 |
the Work from the same or some similar place meets this |
| 439 |
condition, even though third parties are not compelled to |
| 440 |
copy the Work along with the modified component; |
| 441 |
|
| 442 |
2. Information that is sufficient to obtain a complete, |
| 443 |
unmodified copy of the Work. |
| 444 |
|
| 445 |
7. If you are not the Current Maintainer of the Work, you may |
| 446 |
distribute a Compiled Work generated from a Derived Work, as long as |
| 447 |
the Derived Work is distributed to all recipients of the Compiled |
| 448 |
Work, and as long as the conditions of Clause 6, above, are met with |
| 449 |
regard to the Derived Work. |
| 450 |
|
| 451 |
8. The conditions above are not intended to prohibit, and hence do not |
| 452 |
apply to, the modification, by any method, of any component so that it |
| 453 |
becomes identical to an updated version of that component of the Work as |
| 454 |
it is distributed by the Current Maintainer under Clause 4, above. |
| 455 |
|
| 456 |
9. Distribution of the Work or any Derived Work in an alternative |
| 457 |
format, where the Work or that Derived Work (in whole or in part) is |
| 458 |
then produced by applying some process to that format, does not relax or |
| 459 |
nullify any sections of this license as they pertain to the results of |
| 460 |
applying that process. |
| 461 |
|
| 462 |
10. a. A Derived Work may be distributed under a different license |
| 463 |
provided that license itself honors the conditions listed in |
| 464 |
Clause 6 above, in regard to the Work, though it does not have |
| 465 |
to honor the rest of the conditions in this license. |
| 466 |
|
| 467 |
b. If a Derived Work is distributed under a different license, that |
| 468 |
Derived Work must provide sufficient documentation as part of |
| 469 |
itself to allow each recipient of that Derived Work to honor the |
| 470 |
restrictions in Clause 6 above, concerning changes from the Work. |
| 471 |
|
| 472 |
11. This license places no restrictions on works that are unrelated to |
| 473 |
the Work, nor does this license place any restrictions on aggregating |
| 474 |
such works with the Work by any means. |
| 475 |
|
| 476 |
12. Nothing in this license is intended to, or may be used to, prevent |
| 477 |
complete compliance by all parties with all applicable laws. |
| 478 |
|
| 479 |
|
| 480 |
NO WARRANTY |
| 481 |
=========== |
| 482 |
|
| 483 |
There is no warranty for the Work. Except when otherwise stated in |
| 484 |
writing, the Copyright Holder provides the Work `as is', without |
| 485 |
warranty of any kind, either expressed or implied, including, but not |
| 486 |
limited to, the implied warranties of merchantability and fitness for a |
| 487 |
particular purpose. The entire risk as to the quality and performance |
| 488 |
of the Work is with you. Should the Work prove defective, you assume |
| 489 |
the cost of all necessary servicing, repair, or correction. |
| 490 |
|
| 491 |
In no event unless required by applicable law or agreed to in writing |
| 492 |
will The Copyright Holder, or any author named in the components of the |
| 493 |
Work, or any other party who may distribute and/or modify the Work as |
| 494 |
permitted above, be liable to you for damages, including any general, |
| 495 |
special, incidental or consequential damages arising out of any use of |
| 496 |
the Work or out of inability to use the Work (including, but not limited |
| 497 |
to, loss of data, data being rendered inaccurate, or losses sustained by |
| 498 |
anyone as a result of any failure of the Work to operate with any other |
| 499 |
programs), even if the Copyright Holder or said author or said other |
| 500 |
party has been advised of the possibility of such damages. |
| 501 |
|
| 502 |
|
| 503 |
MAINTENANCE OF THE WORK |
| 504 |
======================= |
| 505 |
|
| 506 |
The Work has the status `author-maintained' if the Copyright Holder |
| 507 |
explicitly and prominently states near the primary copyright notice in |
| 508 |
the Work that the Work can only be maintained by the Copyright Holder |
| 509 |
or simply that it is `author-maintained'. |
| 510 |
|
| 511 |
The Work has the status `maintained' if there is a Current Maintainer |
| 512 |
who has indicated in the Work that they are willing to receive error |
| 513 |
reports for the Work (for example, by supplying a valid e-mail |
| 514 |
address). It is not required for the Current Maintainer to acknowledge |
| 515 |
or act upon these error reports. |
| 516 |
|
| 517 |
The Work changes from status `maintained' to `unmaintained' if there |
| 518 |
is no Current Maintainer, or the person stated to be Current |
| 519 |
Maintainer of the work cannot be reached through the indicated means |
| 520 |
of communication for a period of six months, and there are no other |
| 521 |
significant signs of active maintenance. |
| 522 |
|
| 523 |
You can become the Current Maintainer of the Work by agreement with |
| 524 |
any existing Current Maintainer to take over this role. |
| 525 |
|
| 526 |
If the Work is unmaintained, you can become the Current Maintainer of |
| 527 |
the Work through the following steps: |
| 528 |
|
| 529 |
1. Make a reasonable attempt to trace the Current Maintainer (and |
| 530 |
the Copyright Holder, if the two differ) through the means of |
| 531 |
an Internet or similar search. |
| 532 |
|
| 533 |
2. If this search is successful, then enquire whether the Work |
| 534 |
is still maintained. |
| 535 |
|
| 536 |
a. If it is being maintained, then ask the Current Maintainer |
| 537 |
to update their communication data within one month. |
| 538 |
|
| 539 |
b. If the search is unsuccessful or no action to resume active |
| 540 |
maintenance is taken by the Current Maintainer, then announce |
| 541 |
within the pertinent community your intention to take over |
| 542 |
maintenance. (If the Work is a LaTeX work, this could be |
| 543 |
done, for example, by posting to comp.text.tex.) |
| 544 |
|
| 545 |
3a. If the Current Maintainer is reachable and agrees to pass |
| 546 |
maintenance of the Work to you, then this takes effect |
| 547 |
immediately upon announcement. |
| 548 |
|
| 549 |
b. If the Current Maintainer is not reachable and the Copyright |
| 550 |
Holder agrees that maintenance of the Work be passed to you, |
| 551 |
then this takes effect immediately upon announcement. |
| 552 |
|
| 553 |
4. If you make an `intention announcement' as described in 2b. above |
| 554 |
and after three months your intention is challenged neither by |
| 555 |
the Current Maintainer nor by the Copyright Holder nor by other |
| 556 |
people, then you may arrange for the Work to be changed so as |
| 557 |
to name you as the (new) Current Maintainer. |
| 558 |
|
| 559 |
5. If the previously unreachable Current Maintainer becomes |
| 560 |
reachable once more within three months of a change completed |
| 561 |
under the terms of 3b) or 4), then that Current Maintainer must |
| 562 |
become or remain the Current Maintainer upon request provided |
| 563 |
they then update their communication data within one month. |
| 564 |
|
| 565 |
A change in the Current Maintainer does not, of itself, alter the fact |
| 566 |
that the Work is distributed under the LPPL license. |
| 567 |
|
| 568 |
If you become the Current Maintainer of the Work, you should |
| 569 |
immediately provide, within the Work, a prominent and unambiguous |
| 570 |
statement of your status as Current Maintainer. You should also |
| 571 |
announce your new status to the same pertinent community as |
| 572 |
in 2b) above. |
| 573 |
|
| 574 |
|
| 575 |
WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE |
| 576 |
====================================================== |
| 577 |
|
| 578 |
This section contains important instructions, examples, and |
| 579 |
recommendations for authors who are considering distributing their |
| 580 |
works under this license. These authors are addressed as `you' in |
| 581 |
this section. |
| 582 |
|
| 583 |
Choosing This License or Another License |
| 584 |
---------------------------------------- |
| 585 |
|
| 586 |
If for any part of your work you want or need to use *distribution* |
| 587 |
conditions that differ significantly from those in this license, then |
| 588 |
do not refer to this license anywhere in your work but, instead, |
| 589 |
distribute your work under a different license. You may use the text |
| 590 |
of this license as a model for your own license, but your license |
| 591 |
should not refer to the LPPL or otherwise give the impression that |
| 592 |
your work is distributed under the LPPL. |
| 593 |
|
| 594 |
The document `modguide.tex' in the base LaTeX distribution explains |
| 595 |
the motivation behind the conditions of this license. It explains, |
| 596 |
for example, why distributing LaTeX under the GNU General Public |
| 597 |
License (GPL) was considered inappropriate. Even if your work is |
| 598 |
unrelated to LaTeX, the discussion in `modguide.tex' may still be |
| 599 |
relevant, and authors intending to distribute their works under any |
| 600 |
license are encouraged to read it. |
| 601 |
|
| 602 |
A Recommendation on Modification Without Distribution |
| 603 |
----------------------------------------------------- |
| 604 |
|
| 605 |
It is wise never to modify a component of the Work, even for your own |
| 606 |
personal use, without also meeting the above conditions for |
| 607 |
distributing the modified component. While you might intend that such |
| 608 |
modifications will never be distributed, often this will happen by |
| 609 |
accident -- you may forget that you have modified that component; or |
| 610 |
it may not occur to you when allowing others to access the modified |
| 611 |
version that you are thus distributing it and violating the conditions |
| 612 |
of this license in ways that could have legal implications and, worse, |
| 613 |
cause problems for the community. It is therefore usually in your |
| 614 |
best interest to keep your copy of the Work identical with the public |
| 615 |
one. Many works provide ways to control the behavior of that work |
| 616 |
without altering any of its licensed components. |
| 617 |
|
| 618 |
How to Use This License |
| 619 |
----------------------- |
| 620 |
|
| 621 |
To use this license, place in each of the components of your work both |
| 622 |
an explicit copyright notice including your name and the year the work |
| 623 |
was authored and/or last substantially modified. Include also a |
| 624 |
statement that the distribution and/or modification of that |
| 625 |
component is constrained by the conditions in this license. |
| 626 |
|
| 627 |
Here is an example of such a notice and statement: |
| 628 |
|
| 629 |
%% pig.dtx |
| 630 |
%% Copyright 2005 M. Y. Name |
| 631 |
% |
| 632 |
% This work may be distributed and/or modified under the |
| 633 |
% conditions of the LaTeX Project Public License, either version 1.3 |
| 634 |
% of this license or (at your option) any later version. |
| 635 |
% The latest version of this license is in |
| 636 |
% http://www.latex-project.org/lppl.txt |
| 637 |
% and version 1.3 or later is part of all distributions of LaTeX |
| 638 |
% version 2005/12/01 or later. |
| 639 |
% |
| 640 |
% This work has the LPPL maintenance status `maintained'. |
| 641 |
% |
| 642 |
% The Current Maintainer of this work is M. Y. Name. |
| 643 |
% |
| 644 |
% This work consists of the files pig.dtx and pig.ins |
| 645 |
% and the derived file pig.sty. |
| 646 |
|
| 647 |
Given such a notice and statement in a file, the conditions |
| 648 |
given in this license document would apply, with the `Work' referring |
| 649 |
to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being |
| 650 |
generated from `pig.dtx' using `pig.ins'), the `Base Interpreter' |
| 651 |
referring to any `LaTeX-Format', and both `Copyright Holder' and |
| 652 |
`Current Maintainer' referring to the person `M. Y. Name'. |
| 653 |
|
| 654 |
If you do not want the Maintenance section of LPPL to apply to your |
| 655 |
Work, change `maintained' above into `author-maintained'. |
| 656 |
However, we recommend that you use `maintained', as the Maintenance |
| 657 |
section was added in order to ensure that your Work remains useful to |
| 658 |
the community even when you can no longer maintain and support it |
| 659 |
yourself. |
| 660 |
|
| 661 |
Derived Works That Are Not Replacements |
| 662 |
--------------------------------------- |
| 663 |
|
| 664 |
Several clauses of the LPPL specify means to provide reliability and |
| 665 |
stability for the user community. They therefore concern themselves |
| 666 |
with the case that a Derived Work is intended to be used as a |
| 667 |
(compatible or incompatible) replacement of the original Work. If |
| 668 |
this is not the case (e.g., if a few lines of code are reused for a |
| 669 |
completely different task), then clauses 6b and 6d shall not apply. |
| 670 |
|
| 671 |
|
| 672 |
Important Recommendations |
| 673 |
------------------------- |
| 674 |
|
| 675 |
Defining What Constitutes the Work |
| 676 |
|
| 677 |
The LPPL requires that distributions of the Work contain all the |
| 678 |
files of the Work. It is therefore important that you provide a |
| 679 |
way for the licensee to determine which files constitute the Work. |
| 680 |
This could, for example, be achieved by explicitly listing all the |
| 681 |
files of the Work near the copyright notice of each file or by |
| 682 |
using a line such as: |
| 683 |
|
| 684 |
% This work consists of all files listed in manifest.txt. |
| 685 |
|
| 686 |
in that place. In the absence of an unequivocal list it might be |
| 687 |
impossible for the licensee to determine what is considered by you |
| 688 |
to comprise the Work and, in such a case, the licensee would be |
| 689 |
entitled to make reasonable conjectures as to which files comprise |
| 690 |
the Work. |
| 691 |
|
| 692 |
|
| 693 |
|
| 694 |
|
| 695 |
C. Artistic |
| 696 |
D. PD (Public domain): |
| 697 |
|
| 698 |
The file or package contains a statement equivalent to |
| 699 |
|
| 700 |
"This file is in the public domain. You may freely use, modify and |
| 701 |
distribute it". |
| 702 |
|
| 703 |
E. Non-standard licenses, by package name: |
| 704 |
|
| 705 |
(1) eepic.sty, eepicemu.sty: |
| 706 |
The macros are in public domain. |
| 707 |
You may distribute or modify it in any ways you like. |
| 708 |
epic.sty: |
| 709 |
You may use this file in whatever way you wish. You are requested to |
| 710 |
leave this notice intact, and report any bugs, enhancements, comments, |
| 711 |
suggestions, etc. to: |
| 712 |
... |
| 713 |
|
| 714 |
(2) The Computer Modern fonts by Donald E. Knuth have a special |
| 715 |
license; essentially, they are public domain, but no modified |
| 716 |
version may use the same name, and the names "TeX" and "MetaFont" |
| 717 |
for the resulting programs, unless they pass the TRIP and TRAP |
| 718 |
tests. The complete license statement can be found in a text at |
| 719 |
http://www.tug.org/TUGboat/Articles/tb11-4/tb30knut.pdf, and the |
| 720 |
relevant parts are: |
| 721 |
|
| 722 |
,---- |
| 723 |
| My work on developing TEX, METAFONT, and Computer |
| 724 |
| Modern has come to an end. I willmake no further |
| 725 |
| changes except to correct extremely serious bugs. |
| 726 |
| |
| 727 |
| I have put these systems into the public domain so that |
| 728 |
| people everywhere can use the ideas freely if they wish. |
| 729 |
| |
| 730 |
| [...] |
| 731 |
| As stated on the copyright pages of Volumes B, D, and |
| 732 |
| E, anybody can make use of my programs in whatever |
| 733 |
| way they wish, as long as they do not use the names |
| 734 |
| TEX, METAFONT, or Computer Modern. In particular, |
| 735 |
| any person or group who wants to produce a program |
| 736 |
| superior to mine is free to do so. However, nobody is |
| 737 |
| allowed to call a system TEX or METAFONT unless that |
| 738 |
| system conforms 100% to my own programs, as I have |
| 739 |
| specified in the manuals for the TRIP and TRAP tests. |
| 740 |
| And nobody is allowed to use the names of the Computer |
| 741 |
| Modern fonts in Volume E for any fonts that do not |
| 742 |
| produce identical tfm files. This prohibition applies to |
| 743 |
| all people or machines, whether appointed by TUG or |
| 744 |
| by any other organization. I do not intend to delegate the |
| 745 |
| responsibility formaintainance of TEX, METAFONT, or |
| 746 |
| Computer Modern to anybody else, ever. |
| 747 |
`---- |
| 748 |
|
| 749 |
For those who believe more in texts written on paper, we reproduce |
| 750 |
here the copyright page of Volume $of "Computers and Typesetting" |
| 751 |
by Donald E. Knuth, which present the commented code for the |
| 752 |
Computer Modern fonts: |
| 753 |
|
| 754 |
,---- |
| 755 |
| The quotations on pages 7 and 351 have been excerpted [...]. |
| 756 |
| |
| 757 |
| METAFONT is a trademark of th Addison Wesley Publishing Company. |
| 758 |
| |
| 759 |
| TeX is a trademark of the American Mathematical Society. |
| 760 |
| |
| 761 |
| The programs for computer Modern are in the public domain, and readers |
| 762 |
| may freely generate and hand-tune their own fonts using the algorithms |
| 763 |
| of this book. However, use of the names is restricted: Any fonts |
| 764 |
| whose names cmr10 or cmbx12 or ... are identical to the standard font |
| 765 |
| names of this book should be fully compatible with the fonts defined |
| 766 |
| here; i.e., fonts with the same names are supposed to have precisely |
| 767 |
| the same character coding schemes and precisely the same font metric |
| 768 |
| files. |
| 769 |
`---- |
| 770 |
|
| 771 |
|
| 772 |
|
| 773 |
***** |
| 774 |
|
| 775 |
F. Individual files, not belonging to any package: |
| 776 |
|
| 777 |
% cahyph.tex: LPPL 1+ |
| 778 |
% gahyph.tex: GPL 2+ |
| 779 |
% icehyph.tex: LPPL 1.2+ |
| 780 |
% ruhyphas.tex: LPPL 1.2+ |
| 781 |
% ruhyphzn.tex: LPPL 1.2+ |
| 782 |
% sehyph.tex: LPPL 1.2+ |
| 783 |
|
| 784 |
|
| 785 |
|
| 786 |
3.4 Reference to an (incomplete) list of licenses of individual parts |
| 787 |
|
| 788 |
The file list for each binary package has the format explained above |
| 789 |
and can be found, for each binary package, in |
| 790 |
|
| 791 |
/usr/share/doc/texlive-<name>/Licenses. |
| 792 |
|