all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: David Kastrup <dak@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs documentation.
Date: Sat, 29 Sep 2007 22:04:26 +0000	[thread overview]
Message-ID: <20070929220426.GB1894@muc.de> (raw)
In-Reply-To: <85ve9t6y1n.fsf@lola.goethe.zz>

'nAbend, David!

On Sat, Sep 29, 2007 at 10:01:40PM +0200, David Kastrup wrote:
>looked at Alan Mackenzie <acm@muc.de> writes:

> >>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.

That's what I would've thought.  Given the existence of, in particular,
TeX and LaTeX, I really don't understand what the point of Docbook is.
(That's NOT a rhetorical comment.)

What has irritated me about David P.'s posts is he seems to assume that
Docbook doesn't need justification - it is the Right Thing for any
documentation application, and it is somehow not done to ask questions
about it.  I'm still hoping he'll come back with some answers.

[ .... ]

> 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.

How things have changed since 1989!

[ .... ]

> >>>  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.

I didn't express myself very well.  I think what I meant by "special
purpose editor" was one that interprets the XML data structure and hides
it from the user, much like Open Office does with ODF.  I contrast this
with an editor where you actually see and edit the raw XML file, possibly
with the help of a good major mode.  I suppose it's analogous to the
difference between editing Elisp source files and hacking through the
internal form created by the Lisp reader.

I don't think that Emacs developers would be willing to learn such a
special purpose editor, just to write Info-MkII documents with.

> 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.

Nor me.

> David Kastrup, Kriemhildstr. 15, 44793 Bochum

-- 
Alan Mackenzie (Ittersbach, Germany).

  reply	other threads:[~2007-09-29 22:04 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 ` Emacs documentation David Kastrup
2007-09-29 22:04   ` Alan Mackenzie [this message]
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=20070929220426.GB1894@muc.de \
    --to=acm@muc.de \
    --cc=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.