|| On Tue, 15 Apr 2003 10:37:57 -0400 || bts@alum.mit.edu (Brian T. Sniffen) wrote: bts> You've heard all this before, but I haven't seen you answer it. bts> Why does the GFDL prohibit me from making an emacs reference bts> card from the manual? Sure, I could make a one-sided card where bts> the other side is the Manifesto, but that wastes half my space. That is most likely a special case. Technical tables are not Copyrightable per se. Their special formatting or composition might be, but generally the table itself is not. This will probably also apply to such reference cards, which is a table mapping key presses to functions of a program. So it should be perfectly fine if you took the content of that reference card and printed it as long as you took care to not include things like special formatting or logos. bts> In addition, how does the FSF expect anybody other than itself bts> to distribute a GPL'd emacs with a GFDL manual? As far as I can bts> see, they cannot be distributed together. Why would that be? Documents and software are different domains by law. Just putting them together -- even if one "links" to the other -- does not constitute one assembled work. In fact it is probable that not even hard-linking them by compiling a document into a program would legally form one work. For a somewhat definitive answer to that we'd need to have a study performed; but it is the estimation of a lawyer specialized on Copyright that I have run this through. Regards, Georg -- Georg C. F. Greve <greve@gnu.org> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org)
Attachment:
pgpHHEU7RyfAX.pgp
Description: PGP signature