unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 8900@debbugs.gnu.org
Subject: bug#8900: 24.0.50; please index mentioned coding systems in Emacs manual
Date: Fri, 01 Jul 2011 22:49:11 +0300	[thread overview]
Message-ID: <83liwhrdc8.fsf@gnu.org> (raw)
In-Reply-To: <9BB5F2A7090B4F2585512C563D1717B3@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <larsi@gnus.org>, <8900@debbugs.gnu.org>
> Date: Fri, 1 Jul 2011 11:17:23 -0700
> 
> > > I disagree.  These are real, implementation, user-visible, 
> > > runtime names.  This is just like indexing command names
> > > or variable names or package names.  The exact name should
> > > appear in the index.
> > 
> > Not true, at least not until we have a detailed documentation of each
> > encoding there.  The absolute majority of coding-systems is not
> > documented in the manual, so there's no real place to put the index
> > entries.  I'm not sure there's something intelligent to tell about
> > these encodings in the manual, either.
> 
> Doesn't matter that we don't have detailed doc about these.  Certainly doesn't
> matter that we don't have detailed doc about *each* coding system.

Well, in that case, we will have to disagree.  Having index entries
about something that isn't described is a Bad Thing.

> The fact is that the manual provides some information about these particular
> coding systems.  They should be indexed so users can easily find that
> information.

But there's no information to find.

> An index does not refer only to "detailed documentation" about terms.  It refers
> to terms that we think a user is likely to look for in the book.  It is often
> the case that a term is indexed that is only mentioned in the book.

Not in my book.





  reply	other threads:[~2011-07-01 19:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 15:24 bug#8900: 24.0.50; please index mentioned coding systems in Emacs manual Drew Adams
2011-07-01 14:28 ` Lars Magne Ingebrigtsen
2011-07-01 15:00   ` Drew Adams
2011-07-01 15:39     ` Lars Magne Ingebrigtsen
2011-07-01 15:54       ` Drew Adams
2011-07-01 17:52         ` Eli Zaretskii
2011-07-01 18:17           ` Drew Adams
2011-07-01 19:49             ` Eli Zaretskii [this message]
2011-07-01 21:00               ` Drew Adams
2011-07-02  6:11                 ` Eli Zaretskii
2011-07-02 14:37                   ` Drew Adams
2011-07-02 15:27                     ` Eli Zaretskii
2011-07-01 17:45   ` Eli Zaretskii
2011-07-01 19:46     ` Eli Zaretskii
2011-07-02 12:38       ` Lars Magne Ingebrigtsen

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=83liwhrdc8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=8900@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.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).