unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andrew M. Scott" <amscott1@sedona.ch.intel.com>
Subject: Excess spaces in info copyrights; inconsistent @copyright{} usage.
Date: Tue, 7 Mar 2006 10:28:28 -0700	[thread overview]
Message-ID: <17421.49852.21607.776396@chls308.ch.intel.com> (raw)

I noticed two anomalies in the current info/texi files:

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.

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).

Samples:

A. elisp.info snippet:

   This is edition 2.9 of the GNU Emacs Lisp Reference Manual,
corresponding to Emacs version 22.0.50.

   Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998, 1999,
2000,   2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
     ^^^

here is the corresponding snippet from elisp.texi:

Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000,
  2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.

A quick spot-check showed similar excess spaces in the info files for
eshell, woman, and ebrowse, but *not* pcl-cvs or message.

B. The space in url.info appears to be due to hard spaces in the
   url.texi file.

C. The erc.texi file is an example of a file using the @copyright{}
   construct (in constrast to elisp.texi):

This manual is for ERC version 5.1.2.

Copyright @copyright{} 2005, 2006 Free Software Foundation, Inc.


In GNU Emacs 22.0.50.1 (x86_64-unknown-linux-gnu, X toolkit)
 of 2006-03-07 on chls308

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: C
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8
  default-enable-multibyte-characters: t

Andy Scott

             reply	other threads:[~2006-03-07 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 17:28 Andrew M. Scott [this message]
2006-03-09  3:06 ` Excess spaces in info copyrights; inconsistent @copyright{} usage Michael Olson
  -- strict thread matches above, loose matches on Subject: below --
2006-03-25 23:27 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=17421.49852.21607.776396@chls308.ch.intel.com \
    --to=amscott1@sedona.ch.intel.com \
    /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).