From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>, 1988@emacsbugs.donarmstrong.com
Cc: 1988@emacsbugs.donarmstrong.com, jessw@netwood.net
Subject: bug#1988: Making the license statement visible in the Emacs Manual
Date: Tue, 27 Jan 2009 00:45:11 +0200 [thread overview]
Message-ID: <ud4e9sn48.fsf@gnu.org> (raw)
In-Reply-To: <g2fxj5kizb.fsf@fencepost.gnu.org>
> Date: Mon, 26 Jan 2009 13:41:44 -0500
> Cc: 1988@emacsbugs.donarmstrong.com
>
> Jesse W wrote:
>
> > There is a specific texinfo @ command, @insertcopying, which is
> > designed to make the @copying information visible. See
> > http://www.gnu.org/software/texinfo/manual/texinfo/html_node/
> > insertcopying.html#insertcopying
>
> This command is already used in the Emacs manual, in what I believe is
> the way texinfo recommends. It only affects the printed titlepage.
It only affects the titlepage because it appears within the @titlepage
block. To make it appear in the HTML output, not as HTML comment
which is not displayed by the browser, you need @insertcopying in the
body of the manual, inside @ifnottex..@end ifnottex.
next prev parent reply other threads:[~2009-01-26 22:45 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 [this message]
2009-01-27 22:59 ` Richard M Stallman
2009-01-28 4:04 ` Eli Zaretskii
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=ud4e9sn48.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1988@emacsbugs.donarmstrong.com \
--cc=jessw@netwood.net \
--cc=rgm@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).