From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: karl@freefriends.org, bug-texinfo@gnu.org, emacs-devel@gnu.org
Subject: Re: inforef
Date: Wed, 15 Dec 2004 21:14:01 -0600 (CST) [thread overview]
Message-ID: <200412160314.iBG3E1N17147@raven.dms.auburn.edu> (raw)
In-Reply-To: <rzqy8fzyu42.fsf@loveshack> (message from Dave Love on Thu, 16 Dec 2004 00:17:17 +0000)
Karl Berry wrote:
> Consider a beginning user reading the published version of the Emacs
> manual and seeing a reference to the "Emacs MIME Manual". How is that
> user to know that this refers to a .texi file to be found and printed
> off by the user himself? There is not the slightest indication of
> that.
If that's a significant problem you could, for instance, explain it in
the introduction, make a texinfo.tex option for setting an alternative
Info reference as a footnote/endnote. I'd guess that would only be
relevant when actually producing copy for publication.
I believe that it would at the very least be relevant when producing
copy for publication of the Emacs manual and maybe some other GNU
manuals. Obviously, it would not be necessary for the Texinfo manual,
since that one explains the stuff anyway.
Sincerely,
Luc.
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
bug-texinfo@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-texinfo
next prev parent reply other threads:[~2004-12-16 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 3:45 inforef Luc Teirlinck
2004-12-14 5:10 ` inforef Eli Zaretskii
2004-12-14 19:12 ` inforef Dave Love
2004-12-14 17:21 ` inforef Karl Berry
2004-12-15 5:15 ` inforef Luc Teirlinck
2004-12-15 20:22 ` inforef Eli Zaretskii
2004-12-16 0:17 ` inforef Dave Love
2004-12-16 3:14 ` Luc Teirlinck [this message]
2004-12-16 3:19 ` inforef Luc Teirlinck
2004-12-16 0:02 ` inforef Dave Love
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=200412160314.iBG3E1N17147@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=bug-texinfo@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=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).