Re: license copyright patch to MELT for dual GPLv3+ GFDL1.2+

2010-06-09 Thread Basile Starynkevitch
On Wed, Jun 09, 2010 at 12:11:01PM -0700, Mark Mitchell wrote: I think that literate programming approaches (whether the full Knuth version, or the more mild JavaDoc version, or auto-extraction of command-line options or whatever) are valuable. RMS, based on my communications with him, is

Re: license copyright patch to MELT for dual GPLv3+ GFDL1.2+

2010-06-09 Thread Mark Mitchell
Basile Starynkevitch wrote: Meanwhile, I think we should try to make use of the fact that RMS is permitting auto-generated reference documentation (which I have been instructed not to call a manual) using JavaDoc/Doxygen tools. If we use those tools, and demonstrate their value, we're then

Re: license copyright patch to MELT for dual GPLv3+ GFDL1.2+

2010-06-09 Thread Basile Starynkevitch
On Wed, Jun 09, 2010 at 10:46:26PM +0200, Basile Starynkevitch wrote: Please also explain who should I contact, and how? Please also explain how the GNU Emacs is generated. I guess it is by a software of the GNU emacs package. Sorry for the typo, I mean how the GNU emacs documentation is

Re: license copyright patch to MELT for dual GPLv3+ GFDL1.2+

2010-06-09 Thread Basile Starynkevitch
On Wed, Jun 09, 2010 at 01:57:03PM -0700, Mark Mitchell wrote: Basile Starynkevitch wrote: Meanwhile, I think we should try to make use of the fact that RMS is permitting auto-generated reference documentation (which I have been instructed not to call a manual) using JavaDoc/Doxygen

Re: license copyright patch to MELT for dual GPLv3+ GFDL1.2+

2010-06-09 Thread Mark Mitchell
Basile Starynkevitch wrote: So I still don't understand why generating cross-reference documentation with Doxygen for C++ code is permitted, while generating cross-reference documentation witb ÂMELT for MELT code is prohibited. As far as I know, nobody said that.