unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: ifinfo vs ifnottex
Date: Thu, 18 May 2006 22:32:48 -0500 (CDT)	[thread overview]
Message-ID: <200605190332.k4J3WmQT012228@jane.dms.auburn.edu> (raw)
In-Reply-To: <200605182029.k4IKTUZ13053@f7.net> (karl@freefriends.org)

This concerns some @ifinfo-> @ifnottex changes I proposed.  Richard
has already asked me to install these changes, but I will wait till
this remaining issue is resolved.

I have the impression that my changes are clearly the right thing for
info and HTML and, as one should be able to use XML to read and
display .info files, most of what is right for info should be right
for XML as well.  _If_ one should also be able to use docbook to read
.info files, then I believe that this pretty much settles the issue,
by the same argument as for XML.

I have the impression that after my changes, the docbook output will
be in acceptable form.  If this is good enough, then this settles the
issue, as treating docbook separately will make things more complex.
If we want the docbook output to look as perfect as possible, assuming
that it should look more like Tex than like any of the other outputs,
then not only my changes, but all other occurrences of @tex vs
@ifnottex in the Emacs and Elisp manual might have to be reconsidered.
(That is a _lot_ more occurrences than just my proposed changes and
hence quite some work.)  If we want the plain text output to look as
close as possible to perfect too, rather than just acceptable, even
more complexity and changes are needed.

There are essentially five types of situations in my patches where
this question arises, all listed below, *but* there are _many_
additional types of situations, some more complex, in other places.

1.  The "@unnumberedsec" and "@heading" vs "@center" issue in the GPL
   doc.  (See my patches to gpl.texi.)  Richard has already asked me to
   install this, but I will wait to allow for counterarguments concerning
   docbook.  The current @iftex vs @ifinfo is clearly wrong as _nothing_
   gets output in any other format except plain text.

2.  One single instance where my changes might not be really the best
    thing for plain text (but does that matter a lot?) and maybe not
    for docbook:

  If you are going to write actual Emacs Lisp programs that go beyond
minor customization, you should read the @cite{Emacs Lisp Reference Manual}.
@ifinfo
@xref{Top, Emacs Lisp, Emacs Lisp, elisp, the Emacs Lisp Reference
Manual}.
@end ifinfo

3.  Situations like:

@ifinfo
(@pxref{Tab Stops}),
@end ifinfo
@iftex
(see next section),
@end iftex

Again, we could try to be more perfect here for plain text and maybe
docbook by making them go with Tex.  Worth the trouble?

4. Situations like:

  This section describes the commands to check the spelling of a single
word or of a portion of a buffer.  These commands work with the spelling
checker programs Aspell and Ispell, which are not part of Emacs.
@ifinfo
@xref{Top, Aspell,, aspell, The Aspell Manual}.
@end ifinfo

I guess the @ifinfo is there to save place in the _published_ Emacs
manual.  The reference is appropriate for plain text and docbook.

5.  Situations like:

@iftex
mode (@pxref{TeX Mode}).
@end iftex
@ifinfo
mode.
@end ifinfo

I do not understand this one and similar ones at all.  Why is there a
reference in the one situation where space is at a premium and none in
all other situations?  (This would remain true even after my changes.
But after my changes "mode." will no longer be missing in many
formats.)

Sincerely,

Luc.

  reply	other threads:[~2006-05-19  3:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  2:53 ifinfo vs ifnottex Luc Teirlinck
2006-05-18  3:39 ` Eli Zaretskii
2006-05-18  4:15   ` Luc Teirlinck
2006-05-18 18:56     ` Eli Zaretskii
2006-05-18 20:29       ` Karl Berry
2006-05-19  3:32         ` Luc Teirlinck [this message]
2006-05-19 11:04           ` Eli Zaretskii
2006-05-20  1:46             ` Luc Teirlinck
2006-05-20  2:40             ` Luc Teirlinck
2006-05-20  8:46               ` Eli Zaretskii
2006-05-20 17:55                 ` Karl Berry
2006-05-20 18:44                   ` Eli Zaretskii
2006-05-21 17:08                     ` Richard Stallman
2006-05-21 18:44                       ` Eli Zaretskii
2006-05-21 21:07                         ` Karl Berry
2006-05-22  3:21                           ` Eli Zaretskii
2006-05-22 22:10                             ` Karl Berry
2006-05-19 18:05           ` Karl Berry
2006-05-19  9:40         ` Eli Zaretskii
2006-05-19 17:43           ` Karl Berry
2006-05-19 18:10             ` Eli Zaretskii
2006-05-20  5:04           ` Richard Stallman
2006-05-21  0:32             ` Luc Teirlinck
2006-05-18  4:47   ` Luc Teirlinck
2006-05-18  4:51   ` Luc Teirlinck
2006-05-19  2:04 ` Richard Stallman
2006-05-19  2:38   ` Luc Teirlinck
  -- strict thread matches above, loose matches on Subject: below --
2006-05-19 11:39 Robert J. Chassell

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=200605190332.k4J3WmQT012228@jane.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).