From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: jessw@netwood.net, karl@gnu.org, 1988@emacsbugs.donarmstrong.com
Subject: bug#1988: Making the license statement visible in the Emacs Manual
Date: Wed, 28 Jan 2009 06:04:41 +0200 [thread overview]
Message-ID: <u7i4grs86.fsf@gnu.org> (raw)
In-Reply-To: <E1LRwtl-0003kw-04@fencepost.gnu.org>
> From: Richard M Stallman <rms@gnu.org>
> CC: rgm@gnu.org, jessw@netwood.net
> cc: karl@gnu.org
> Date: Tue, 27 Jan 2009 17:59:13 -0500
>
> I suggest talking with the Texinfo maintainer, karl@gnu.org, about this.
> If the Texinfo manual doesn't give clear and specific advice which settles
> your question, then I think some should be added there.
The Texinfo manual _does_ give clear and specific advice about this:
We also strongly recommend using `@insertcopying' in the Top node of
your manual (*note The Top Node::), although it is not required
legally. Here's why:
The `@copying' command itself causes the permissions text to appear
in an Info file _before_ the first node. The text is also copied into
the beginning of each split Info output file, as is legally necessary.
This location implies a human reading the manual using Info does _not_
see this text (except when using the advanced Info command `g *').
Therefore, an explicit `@insertcopying' in the Top node makes it
apparent to readers that the manual is free.
Similarly, the `@copying' text is automatically included at the
beginning of each HTML output file, as an HTML comment. Again, this
text is not visible (unless the reader views the HTML source). And
therefore again, the `@insertcopying' in the Top node is valuable
because it makes the copying permissions visible and thus promotes
freedom.
next prev parent reply other threads:[~2009-01-28 4:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 8:16 bug#1988: Making the license statement visible in the Emacs Manual Jesse W
2009-01-26 7:38 ` Glenn Morris
2009-01-26 18:33 ` Jesse W
2009-01-26 18:41 ` Glenn Morris
2009-01-26 21:28 ` Jesse W
2009-01-26 22:45 ` Eli Zaretskii
2009-01-27 22:59 ` Richard M Stallman
2009-01-28 4:04 ` Eli Zaretskii [this message]
2009-01-28 23:38 ` Karl Berry
2009-01-29 0:25 ` Jesse W
2009-02-01 14:37 ` Karl Berry
2009-02-05 9:29 ` Jesse W
2009-02-06 0:05 ` Karl Berry
2009-02-06 19:03 ` Jesse W
2009-02-06 23:02 ` Karl Berry
2009-02-08 19:38 ` Jesse W
2009-02-16 17:50 ` Karl Berry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u7i4grs86.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1988@emacsbugs.donarmstrong.com \
--cc=jessw@netwood.net \
--cc=karl@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).