Only to the bug, just to sort things out:

"T. V. Raman" <[EMAIL PROTECTED]> wrote:

> The references to DEC and Adobe are legcy.
>
> Each lisp file clearly states it's not part of Emacs but the same
> licensing rules apply --as far as I am concerned that's GPL.

Not in fact each lisp file.

$ export ltext=";;; This file is not part of GNU Emacs, but the same 
permissions apply."
$ for file in `find emacspeak-21.0/ -name "*.el" `; do grep "$ltext" $file 
>/dev/null || echo "statement missing in $file"; done
statement missing in emacspeak-21.0/lisp/emacspeak-finder-inf.el
statement missing in emacspeak-21.0/lisp/emacspeak-w3m.el
statement missing in emacspeak-21.0/lisp/html-outline.el
statement missing in emacspeak-21.0/lisp/tapestry.el
statement missing in emacspeak-21.0/lisp/xml-parse.el
statement missing in emacspeak-21.0/sounds/default-8k/define-theme.el

emacspeak-finder-inf.el: This claims to be a generated file, so should
                         be no problem

emacspeak-w3m.el:        Correct GPL statement, Copyright (C) 2001,2002  
Dimitri V. Paduchih

html-outline.el:         Author: T. V. Raman, no license statement

tapestry.el:             Correct GPL statement, Copyright (C) 1991, 1993, 1994, 
1995, 1997 Kyle E. Jones

xml-parse.el:            Correct GPL statement, Copyright (C) 2001 John Wiegley

define-theme.el:         A three-liner, probably not copyrightable.

There's one .c file, with the usual "same as Emacs" statement.

************************************

The info manual doesn't allow modification currently.

The Installing Emacspeak HOWTO and the Emacspeak User's Guide are
Copyright © 2001 IBM and under the GFDL.

Several files in /etc don't have a license statement, some might not
need one.

The xml files in lisp/xml-forms don't have a copyright or license
statement, but I doubt they are copyrightable.

sawfish/sawfishrc is missing a license statement, but it is very short
and perhaps not copyrightable.

Regards, Frank

-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer


Reply via email to