CTAN Comprehensive TeX Archive Network

The Project Public Li­cense (lppl)

LPPL Ver­sion 1.0 1999-03-01

Copy­right 1999 3 Project

Every­one is per­mit­ted to copy and dis­tribute ver­ba­tim copies of this li­cense doc­u­ment, but mod­i­fi­ca­tion is not al­lowed.


The Project Public Li­cense (LPPL) is the li­cense un­der which the base dis­tri­bu­tion is dis­tributed. As de­scribed be­low you may use this li­cence for any soft­ware that you wish to dis­tribute.

It may be par­tic­u­larly suit­able if your soft­ware is re­lated (such as a pack­age file) but it may be used for any soft­ware, even if it is un­re­lated to .

To use this li­cense, the files of your dis­tri­bu­tion should have an ex­plicit copy­right no­tice giv­ing your name and the year, to­gether with a ref­er­ence to this li­cense.

A typ­i­cal ex­am­ple would be

   %% pig.sty
   %% Copyright 2001 M. Y. Name

   % This program can redistributed and/or modified under the terms
   % of the LaTeX Project Public License Distributed from CTAN
   % archives in directory macros/latex/base/lppl.txt; either
   % version 1 of the License, or (at your option) any later version.

Given such a no­tice in the file, the con­di­tions of this doc­u­ment would ap­ply, with:

  • “The Pro­gram” re­fer­ring to the soft­ware “pig.sty” and
  • “The Copy­right Holder” re­fer­ring to the per­son “M. Y. Name”.

To see a real ex­am­ple, see the file le­gal.txt which car­ries the copy­right no­tice for the base la­tex dis­tri­bu­tion.

This li­cense gives terms un­der which files of The Pro­gram may be dis­tributed and mod­i­fied. In­di­vid­ual files may have spe­cific fur­ther con­straints on mod­i­fi­ca­tion, but no file should have re­stric­tions on dis­tri­bu­tion other than those spec­i­fied be­low. This is to en­sure that a dis­trib­u­tor wish­ing to dis­tribute a com­plete un­mod­i­fied copy of The Pro­gram need only check the con­di­tions in this file, and does not need to check ev­ery file in The Pro­gram for ex­tra re­stric­tions. If you do need to mod­ify the dis­tri­bu­tion terms of some files, do not re­fer to this li­cense, in­stead dis­tribute The Pro­gram un­der a dif­fer­ent li­cense. You may use the parts of the text of LPPL as a model for your own li­cense, but your li­cense should not di­rectly re­fer to the LPPL or oth­er­wise give the im­pres­sion that The Pro­gram is dis­tributed un­der the LPPL.


There is no war­ranty for The Pro­gram, to the ex­tent per­mit­ted by ap­pli­ca­ble law. Ex­cept when oth­er­wise stated in writ­ing, The Copy­right Holder pro­vides The Pro­gram “as is” with­out war­ranty of any kind, ei­ther ex­pressed or im­plied, in­clud­ing, but not lim­ited to, the im­plied war­ranties of mer­chantabil­ity and fit­ness for a par­tic­u­lar pur­pose. The en­tire risk as to the qual­ity and per­for­mance of the pro­gram is with you. Should The Pro­gram prove de­fec­tive, you as­sume the cost of all nec­es­sary ser­vic­ing, re­pair or cor­rec­tion.

In no event un­less re­quired by ap­pli­ca­ble law or agreed to in writ­ing will The Copy­right Holder, or any of the in­di­vid­ual au­thors named in the source for The Pro­gram, be li­able to you for dam­ages, in­clud­ing any gen­eral, spe­cial, in­ci­den­tal or con­se­quen­tial dam­ages aris­ing out of any use of The Pro­gram or out of in­abil­ity to use The Pro­gram (in­clud­ing but not lim­ited to loss of data or data be­ing ren­dered in­ac­cu­rate or losses sus­tained by you or by third par­ties as a re­sult of a fail­ure of The Pro­gram to op­er­ate with any other pro­grams), even if such holder or other party has been ad­vised of the pos­si­bil­ity of such dam­ages.


Redis­tri­bu­tion of un­changed files is al­lowed pro­vided that all files that make up the dis­tri­bu­tion of The Pro­gram are dis­tributed. In par­tic­u­lar this means that The Pro­gram has to be dis­tributed in­clud­ing its doc­u­men­ta­tion if doc­u­men­ta­tion was part of the orig­i­nal dis­tri­bu­tion.

The dis­tri­bu­tion of The Pro­gram will con­tain a promi­nent file list­ing all the files cov­ered by this li­cense.

If you re­ceive only some of these files from some­one, com­plain!

The dis­tri­bu­tion of changed ver­sions of cer­tain files in­cluded in the The Pro­gram, and the reuse of code from The Pro­gram, are al­lowed un­der the fol­low­ing re­stric­tions:

  • It is al­lowed only if the le­gal no­tice in the file does not ex­pressly for­bid it. See note be­low, un­der “Con­di­tions on in­di­vid­ual files&lrquo;.
  • You re­name the file be­fore you make any changes to it, un­less the file ex­plic­itly says that re­nam­ing is not re­quired. Any such changed files must be dis­tributed un­der a li­cense that for­bids dis­tri­bu­tion of those files, and any files de­rived from them, un­der the names used by the orig­i­nal files in the dis­tri­bu­tion of The Pro­gram.
  • You change any “iden­ti­fi­ca­tion string” in The Pro­gram to clearly in­di­cate that the file is not part of the stan­dard sys­tem.
  • If The Pro­gram in­cludes an “er­ror re­port ad­dress” so that er­rors may be re­ported to The Copy­right Holder, or other spec­i­fied ad­dresses, this ad­dress must be changed in any mod­i­fied ver­sions of The Pro­gram, so that re­ports for files not main­tained by the orig­i­nal pro­gram main­tain­ers are di­rected to the main­tain­ers of the changed files.
  • You ac­knowl­edge the source and au­thor­ship of the orig­i­nal ver­sion in the mod­i­fied file.
  • You also dis­tribute the un­mod­i­fied ver­sion of the file or al­ter­na­tively pro­vide suf­fi­cient in­for­ma­tion so that the user of your mod­i­fied file can be rea­son­ably ex­pected to be able to ob­tain an orig­i­nal, un­mod­i­fied copy of The Pro­gram. For ex­am­ple, you may spec­ify a URL to a site that you ex­pect will freely pro­vide the user with a copy of The Pro­gram (ei­ther the ver­sion on which your mod­i­fi­ca­tion is based, or per­haps a later ver­sion).
  • If The Pro­gram is in­tended to be used with, or is based on, , then files with the fol­low­ing file ex­ten­sions which have spe­cial mean­ing in Soft­ware, have spe­cial mod­i­fi­ca­tion rules un­der the li­cense:
    • Files with ex­ten­sion “.ins” (in­stal­la­tion files): these files may not be mod­i­fied at all be­cause they con­tain the le­gal no­tices that are placed in the gen­er­ated files.
    • Files with ex­ten­sion “.fd” ( font def­i­ni­tions files): these files are al­lowed to be mod­i­fied with­out chang­ing the name, but only to en­able use of all avail­able fonts and to pre­vent at­tempts to ac­cess un­avail­able fonts. How­ever, mod­i­fied files are not al­lowed to be dis­tributed in place of orig­i­nal files.
    • Files with ex­ten­sion “.cfg” (con­fig­u­ra­tion files): these files can be cre­ated or mod­i­fied to en­able easy con­fig­u­ra­tion of the sys­tem. The doc­u­men­ta­tion in cfg­guide.tex in the base dis­tri­bu­tion de­scribes when it makes sense to mod­ify or gen­er­ate such files.

The above re­stric­tions are not in­tended to pro­hibit, and hence do not ap­ply to, the up­dat­ing, by any method, of a file so that it be­comes iden­ti­cal to the lat­est ver­sion of that file in The Pro­gram.


We be­lieve that these re­quire­ments give you the free­dom you to make mod­i­fi­ca­tions that con­form with what­ever tech­ni­cal spec­i­fi­ca­tions you wish, whilst main­tain­ing the avail­abil­ity, in­tegrity and re­li­a­bil­ity of The Pro­gram. If you do not see how to achieve your goal whilst ad­her­ing to these re­quire­ments then read the doc­u­ment cfg­guide.tex in the base dis­tri­bu­tion for sug­ges­tions.

Be­cause of the porta­bil­ity and ex­change­abil­ity as­pects of sys­tems like , The 3 Project dep­re­cates the dis­tri­bu­tion of non-stan­dard ver­sions of com­po­nents of or of gen­er­ally avail­able con­tributed code for them but such dis­tri­bu­tions are per­mit­ted un­der the above re­stric­tions.

The doc­u­ment mod­guide.tex in the base dis­tri­bu­tion de­tails the rea­sons for the le­gal re­quire­ments de­tailed above. Even if The Pro­gram is un­re­lated to , the ar­gu­ment in mod­guide.tex may still ap­ply, and should be read be­fore a mod­i­fied ver­sion of The Pro­gram is dis­tributed.

Con­di­tions on in­di­vid­ual files

The in­di­vid­ual files may bear ad­di­tional con­di­tions which su­per­sede the gen­eral con­di­tions on dis­tri­bu­tion and mod­i­fi­ca­tion con­tained in this file. If there are any such files, the dis­tri­bu­tion of The Pro­gram will con­tain a promi­nent file that lists all the ex­cep­tional files.

Typ­i­cal ex­am­ples of files with more re­stric­tive mod­i­fi­ca­tion con­di­tions would be files that con­tain the text of copy­right no­tices.

  • The con­di­tions on in­di­vid­ual files dif­fer only in the ex­tent of mod­i­fi­ca­tion that is al­lowed.
  • The con­di­tions on dis­tri­bu­tion are the same for all the files. Thus a (re)dis­trib­u­tor of a com­plete, un­changed copy of The Pro­gram need meet only the con­di­tions in this file; it is not nec­es­sary to check the header of ev­ery file in the dis­tri­bu­tion to check that a dis­tri­bu­tion meets these re­quire­ments.




Attention Please check the soft­ware's li­cense be­fore us­ing the soft­ware.

Guest Book Sitemap Contact Contact Author