From: karl@freefriends.org (Karl Berry)
Subject: Re: Excess spaces in info copyrights; inconsistent @copyright{} usage.
Date: Sat, 25 Mar 2006 17:27:51 -0600 [thread overview]
Message-ID: <200603252327.k2PNRpv02232@f7.net> (raw)
Hi Andrew and all,
1. There are excess spaces in the generated Copyright lines in many
but not all info files; I'm using makeinfo 4.8. This seems to occur
for files with more than one line of copyright dates.
In general, makeinfo (unlike TeX) does not ignore spaces at the
beginning of a line. Most multiple-line copyrights were indeed indented
in the source:
Copyright ...
2000, 2001 ...
The two spaces in the input are preserved in the makeinfo output, a
"feature" of makeinfo since inception. (Probably inherited from
texinfo-format-buffer, I expect.)
Anyway, I removed all such indentations I could find in the Emacs manual
sources, and added an admonition about it in the Texinfo manual.
2. Some of the *.texi files use the @copyright{} construct in their
copyright lines (e.g. erc.texi), and some don't (e.g. elisp.texi).
@copyright{} should be used within an @copying block or similar. Again,
I changed all the occurrences I could find. (The exception are the @c
copyrights in the subsidiary .texi files; since that text is never
typeset, (C) is preferred there.)
A few manuals still used @ifinfo and the like instead of @copying (also,
@ifnottex should be used around the Top node). If someone else could
systematically check for and fix that problem, I would be grateful.
Thanks for the report,
Karl
next reply other threads:[~2006-03-25 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 23:27 Karl Berry [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-07 17:28 Excess spaces in info copyrights; inconsistent @copyright{} usage Andrew M. Scott
2006-03-09 3:06 ` Michael Olson
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=200603252327.k2PNRpv02232@f7.net \
--to=karl@freefriends.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).