unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: gmorris@ast.cam.ac.uk, emacs-devel@gnu.org
Subject: Re: Advanced calendar usage in emacs-xtra.texi
Date: Sat, 26 Mar 2005 15:21:50 -0600 (CST)	[thread overview]
Message-ID: <200503262121.j2QLLoJ17010@raven.dms.auburn.edu> (raw)
In-Reply-To: <01c53236$Blat.v2.4$287360c0@zahav.net.il> (eliz@gnu.org)

This leaves us with the question of what constitutes appropriate use
of @inforef.  (The one reference to emacs-xtra from the Emacs manual
which I put in a lot earlier also uses @inforef.)

I originally proposed that @inforef should refer to any manual for
which there is no _published_ rather than printable version available
or planned.  This was rejected.  Instead `(texinfo)inforef' says that
it is only appropriate to refer to text inside @info or to old Info
that did not have a corresponding .texi file and for which printed
text can not be produced.

I would say that it should be considered appropriate when used inside
a manual, such as the Emacs manual, for which a published version is
available and widely used, to refer to a manual without published
version.  Otherwise, the result could indeed be very confusing to a
reader of the published version who is not familiar with Texinfo.

Sincerely,

Luc.

  parent reply	other threads:[~2005-03-26 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DFFm4-0005xm-DR@monty-python.gnu.org>
2005-03-26 19:00 ` Advanced calendar usage in emacs-xtra.texi Eli Zaretskii
2005-03-26 20:00   ` Luc Teirlinck
2005-03-26 22:06     ` Eli Zaretskii
2005-03-26 22:32       ` Luc Teirlinck
2005-03-26 20:14   ` Glenn Morris
2005-03-26 21:21   ` Luc Teirlinck [this message]
2005-03-28 16:25     ` 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

  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=200503262121.j2QLLoJ17010@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=gmorris@ast.cam.ac.uk \
    /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).