Re: Why documentation and programs should not be treated alike

2003-09-26 Thread Wouter Verhelst
On Tue, Sep 23, 2003 at 07:13:13PM -0400, Richard Stallman wrote: In the compiled form of a manual, as long as there is no DRM to stop you from reading it, everything that matters is plain to see. You see the contents, and you even see the fonts and indentation that were selected by the

Re: Why documentation and programs should not be treated alike

2003-09-26 Thread Edmund GRIMLEY EVANS
Richard Stallman [EMAIL PROTECTED]: This is why the GFDL does not require complete corresponding source code for a published manual. It's easier to change the manual if you have this, but no disaster if you don't: you just have to write your own mark-up, which is pretty straightforward. The

Re: Why documentation and programs should not be treated alike

2003-09-26 Thread Thomas Bushnell, BSG
Richard Stallman [EMAIL PROTECTED] writes: I think that nontechnical invariant comments do not make a program non-free, but not for those reasons. The reason is that this is a packaging requirement that doesn't really restrict you from making the program substantively behave as you want it

Why documentation and programs should not be treated alike

2003-09-25 Thread Richard Stallman
The main difference between a program and documentation is that a program does something, while documentation is passive; By this argument, source code to a program (of the sort which must be compiled to run) is not a program. That's a pedantic approach to the issue. I'd say a

Re: Why documentation and programs should not be treated alike

2003-09-25 Thread Nathanael Nerode
Richard Stallman wrote: The main difference between a program and documentation is that a program does something, while documentation is passive; By this argument, source code to a program (of the sort which must be compiled to run) is not a program. That's a pedantic