all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs documentation.
Date: Sat, 29 Sep 2007 22:01:40 +0200	[thread overview]
Message-ID: <85ve9t6y1n.fsf@lola.goethe.zz> (raw)
In-Reply-To: mailman.1485.1191094713.18990.help-gnu-emacs@gnu.org

Alan Mackenzie <acm@muc.de> writes:

> Hi again, Dave!
>
>>Go ask around the OSS world what's being used for documentation.
>
> Why?

Because you'll find that any XML-based process would be rather unusual
(at least ouside of the Java world).  Man-pages, hand-written HTML,
plain text files, Texinfo, LaTeX and other stuff are more prevalent.

> The fact that vast numbers of people use or have used Microsoft
> Windows or XML or Cobol or Emacs or VHS videotape or Trabant cars or
> variable length character encodings or Docbook or Fortran has no
> bearing on whether these things are any good, or what they are good
> for.

The long dampeners on Trabant were actually a good complement to the
lousy road quality in the GDR.  Imported cars suffered from a higher
probability of breakdowns because they were less well suited to the
potholes there.

> I'm not sure you've thought this issue through.  Popularity doesn't
> imply quality.  XML-based thingies and Microsoft Word (*.doc) are
> both widely used formats, yet at least half of them are bad formats.
> As a Docbook enthusiast, you should be able to counter my posts by
> arguing the intrinsic merits of Docbook/XML, and why it would be
> superior to Texinfo in the Emacs project.  I haven't seen you doing
> this.

Well, he did personally inform me that he put me in his killfile when
I made a list of detailed problems and tried to elicit comments.  So
that is one way of addressing such points.

>>>  I suspect most Docbook writers actually use special purpose
>>> editors to create their source code, rather than Emacs or vi.
>
>>Emacs has done for me for the last ten years.
>
> Do most Docbook writers use special purpose editors or don't they?

To be fair: people using Emacs _are_ generally using a special purpose
editor (in the form of a good major mode).  Even LaTeX is not
uncommonly written with special purpose editors and modes.

So if you want to get more relevant numbers, you probably should ask
on some vi user group, as that sort of editor can't be tailored as
well to the task.  How many of those would write Texinfo and LaTeX
with their favorite general purpose editor, but revert to special
systems for XML writing?

I suppose still some, but have no hard numbers.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

       reply	other threads:[~2007-09-29 20:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1485.1191094713.18990.help-gnu-emacs@gnu.org>
2007-09-29 20:01 ` David Kastrup [this message]
2007-09-29 22:04   ` Emacs documentation Alan Mackenzie
2007-09-29 22:05     ` Tom Tromey
2007-09-30  2:18       ` Drew Adams
     [not found]   ` <mailman.1488.1191103233.18990.help-gnu-emacs@gnu.org>
2007-09-30  9:19     ` David Kastrup
2008-10-14 19:01 emacs documentation Sean Sieger
2008-10-14 19:15 ` Lennart Borgman (gmail)
2008-10-14 19:25   ` Sean Sieger
2008-10-14 19:19 ` Drew Adams
2008-10-14 23:07   ` Sean Sieger
  -- strict thread matches above, loose matches on Subject: below --
2007-09-29 21:10 Emacs documentation martin rudalics
2007-09-23  9:53 Emacs documentation. Was My emacs was upgraded and I am a novice again Dave Pawson
2007-09-23 11:12 ` Bastien
2007-09-23 11:35   ` Dave Pawson
2007-09-29 15:46     ` Emacs documentation Alan Mackenzie
2007-09-29 15:47       ` Dave Pawson
2007-09-29 16:03         ` Peter Dyballa
2007-09-29 19:42         ` Alan Mackenzie
2007-09-29 16:33       ` Eli Zaretskii
2004-10-22 21:31 emacs documentation Tak Ota
2004-10-23 18:48 ` Richard Stallman
2004-10-23 19:25   ` Eli Zaretskii
2004-10-23 21:34     ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85ve9t6y1n.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.