unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Cc: fx@gnu.org, bug-texinfo@gnu.org, emacs-devel@gnu.org
Subject: Re: inforef
Date: Tue, 14 Dec 2004 12:21:16 -0500	[thread overview]
Message-ID: <200412141721.iBEHLG327759@f7.net> (raw)
In-Reply-To: <200412140345.iBE3jw402325@raven.dms.auburn.edu>

    I personally interpret it as meaning that @inforef is meant
    to be used when no _published_ manual is available, even though the
    user can produce printed output himself using texi2dvi.  

I don't think this was ever the intent.  Whether a manual was ever
published, i.e., available in a bookstore somewhere, seems unimportant
to me as far as cross references go.

    Others interpret it as meaning that no printed output can be
    produced because, for instance, the info file was not produced from
    Texinfo source.

That was its original purpose.  Eli's example of citing conditional text
is another good possibility.

    (texinfo)inforef' itself uses info.texi as an example, 

Originally, the Info manual was written directly in Info, and no Texinfo
source existed.  I expect that's where the example (and perhaps the
command) came from.

    In the HTML output, @inforef produces a hyperlink to an HTML manual,
    which could not be produced (or so I believe) if the
    Info file was not produced from Texinfo source.  

There's no particular reason why an HTML file could not be produced by
other means.

I agree that it's not completely logical for the HTML output to have a
link for @inforef, but it could be useful, and it's been that way since
the HTML support was written, so I'm loath to change it now.

    But could you please clarify this?

I fiddled with the inforef node in texinfo.txi to try to explain a
little better.

Thanks,
karl

  parent reply	other threads:[~2004-12-14 17:21 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 ` Karl Berry [this message]
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       ` inforef Luc Teirlinck
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=200412141721.iBEHLG327759@f7.net \
    --to=karl@freefriends.org \
    --cc=bug-texinfo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fx@gnu.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).