all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: Proof-reading manuals (was Re: Rmail mbox-format branch)
Date: Sat, 18 Sep 2004 17:06:52 -0500 (CDT)	[thread overview]
Message-ID: <200409182206.i8IM6qd06407@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1C7uI6-0000TT-9V@fencepost.gnu.org> (message from Richard Stallman on Thu, 16 Sep 2004 07:19:06 -0400)

Richard Stallman wrote:

       For lispref this way of organizing things may be reasonable, but for
       man it makes no sense.  It might be nice to have things like
       man/cl.texi updated, but such things are a luxury right now.  What we
       worry about now is the Emacs and Elisp manual and info.texi.

   I agree.  Could you remove the other files from the `man' list, keeping
   only info.texi and those that are part of the Emacs manual?
   Also, remove gfdl.texi and gpl.texi if they are included.

Done.

I removed man/faq.texi, because it has nothing to do with the Emacs manual.
Should we add man/faq.texi as something that should be updated?

I removed man/ack.texi, because it is already listed separately.

I still have to take care of some problems in some of the chapters I
read and marked with LT.  I have not yet sent my suggested changes for
man/text.texi.

The original aim was to have everything proofread by at
least two persons.  For the Elisp manual, that seems unrealistic now.

For the Emacs manual, it might be better if we kept that standard, if
possible.  For instance, I did read man/mule.texi, but I am not a
heavy user of that stuff.  Thus it might be better if somebody using
it more heavily would double check it.  There are other instances like
that.

The Emacs manual could easily be checked by somebody not knowing
Texinfo.  The way we have organized things now (referring to the .texi
files) might not be very understandable to such a person.

Sincerely,

Luc.

  reply	other threads:[~2004-09-18 22:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09  4:02 Rmail mbox-format branch Richard Stallman
2004-09-09 14:13 ` Stefan
2004-09-09 14:44   ` Paul Michael Reilly
2004-09-09 15:25     ` Stefan
2004-09-09 18:56     ` Eli Zaretskii
2004-09-09 22:19       ` Miles Bader
2004-09-10  7:36         ` Kim F. Storm
2004-09-10  9:18           ` Eli Zaretskii
2004-09-10  9:38             ` Miles Bader
2004-09-10 10:41               ` Kim F. Storm
2004-09-10 11:44                 ` Eli Zaretskii
2004-09-10 11:36               ` Eli Zaretskii
2004-09-10 10:39             ` Kim F. Storm
2004-09-10 11:42               ` Eli Zaretskii
2004-09-10 12:38                 ` Kim F. Storm
2004-09-10 16:17                   ` Eli Zaretskii
2004-09-11 23:19                     ` Kim F. Storm
2004-09-11 10:52                   ` Richard Stallman
2004-09-11 11:17                     ` Eli Zaretskii
2004-09-11 16:45                     ` Kim F. Storm
2004-09-11  2:49           ` Luc Teirlinck
2004-09-11 18:46             ` Proof-reading manuals (was Re: Rmail mbox-format branch) Kim F. Storm
2004-09-15  1:12               ` Luc Teirlinck
2004-09-16 11:19                 ` Richard Stallman
2004-09-18 22:06                   ` Luc Teirlinck [this message]
2004-09-19 11:00                     ` Richard Stallman
2004-09-19 16:29                       ` Proof-reading manuals Kim F. Storm
2004-09-11 10:50       ` Rmail mbox-format branch Richard Stallman
2004-09-11 11:22         ` Eli Zaretskii
2004-09-11 16:57           ` Stefan
2004-09-13  6:59           ` Richard Stallman
2004-09-15 10:25             ` Thien-Thi Nguyen
2004-09-11 13:50         ` Robert J. Chassell
2004-09-13 23:04           ` Richard Stallman
2004-09-10 17:41   ` Richard Stallman
2004-09-10 20:27     ` Alex Schroeder
2004-09-12  9:09       ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200409182206.i8IM6qd06407@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.