all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Dave Pawson <dave.pawson@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs documentation.
Date: Sat, 29 Sep 2007 19:42:28 +0000	[thread overview]
Message-ID: <20070929194228.GA1894@muc.de> (raw)
In-Reply-To: <711a73df0709290847m22a30c4uc91ca15cf749cb34@mail.gmail.com>

Hi again, Dave!

>On 29/09/2007, Alan Mackenzie <address@hidden> wrote:

>>> Because XML is more flexible and a more modern standard for
>>> documentation IMHO.

>> Assembler is more flexible than C, but nobody nowadays uses assembler
>> very much.  Being "more modern" has never been a compelling argument for
>> anything in Emacs.  The question to ask is "is it any good?".

>Yes. Look around.

I have.  I once had to hack an XML config file and I've amended some
Docbook source code, though it was some while ago.  They were both
horrible.

What's so good about XML/Docbook as a source format?

>> XML isn't any good as a source format; it's designed to be parseable by
>> programs with minimum effort, and places no value on being readable or
>> writeable.  Using XML/Docbook as a source language would be taking a
>> step back to 1960s technology:

>Rubbish.

:-)

>> (i) There is nothing like Texinfo's "@" or Lisp's/C's "\" for escape
>> purposes; you've got to write "<" as "&lt;", much like you had to
>> write ".lt." in Fortran.  "ü" (German "u umlaut") appears as
>> "&uuml;".  And so on.  Yuck!  That stuff isn't unreadable, but it's
>> uncomfortably close, and it's clumsy enough to condemn XML.

>Go play catchup Alan. You're years behind. About ten.

Oh good!  So please correct my misapprehension and tell me what the
Docbook escape character is.  Next, please tell me how to write a "<"
and a "ü" in a modern Docbook source.  At any stage, you're more than
welcome to attempt to persuade me that writing Docbook source is easy,
pleasant and productive.  Thanks in advance!

>> (ii) Instead of using single character block delimiters like "{}" in
>> C or "()" in Lisp, XML uses long, long keywords, e.g.
>> "<VeryLongUnreadableDelimiter>" to open a block and
>> "</VeryLongUnreadableDelimiter>" to close it.  This harks back to
>> Algol's and Pascal's "BEGIN" and "END".  It also reduces the
>> readability and signal to noise ratio horribly.  Hackers detest
>> prolixity.  ;-)

>It's called semantic markup.

It doesn't matter what it's called.  The important point is that it's
difficult to read and likely difficult to write - much more so than the
Texinfo equivalents.

>> (iii) You can't just comment out a block of XML.

>Wrong.

Oh good!  Please tell me how "just" to comment out a block of XML, with
emphasis on the word "just".  I seem to remember Emacs in SGML mode
going through the region being commented, replacing all the "--"s with
"-/-", and not being able to reverse that transformation.  That's unjust
indeed.

>> Doing so makes the source syntactically incorrect.  In fact, XML
>> comments have a rigid syntactic structure which stops you describing
>> XML constructs in them.  I think this snag, in itself, rules out
>> XML/Docbook as a sensible source format.

>Where have you been?

In XM hell.

[ .... ]

>> > You may be right. I think it is worth challenging though, otherwise
>> > we'll never progress?

>> XML as a source language isn't progress; it's like regressing into the
>> dark ages.

>Go ask around the OSS world what's being used for documentation.

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

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.

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

>-- 
>Dave Pawson

-- 
Alan Mackenzie (Ittersbach, Germany).

  parent reply	other threads:[~2007-09-29 19:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-23 12:37     ` Bastien
2007-09-23 16:26     ` Tom Tromey
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 [this message]
2007-09-29 16:33       ` Eli Zaretskii
     [not found]   ` <mailman.1182.1190547310.18990.help-gnu-emacs@gnu.org>
2007-09-23 12:50     ` Emacs documentation. Was My emacs was upgraded and I am a novice again David Kastrup
2007-09-23 14:55       ` Dave Pawson
     [not found]       ` <mailman.1188.1190559347.18990.help-gnu-emacs@gnu.org>
2007-09-23 15:11         ` David Kastrup
  -- strict thread matches above, loose matches on Subject: below --
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
2007-09-29 21:10 Emacs documentation martin rudalics
     [not found] <mailman.1485.1191094713.18990.help-gnu-emacs@gnu.org>
2007-09-29 20:01 ` David Kastrup
2007-09-29 22:04   ` 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
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=20070929194228.GA1894@muc.de \
    --to=acm@muc.de \
    --cc=dave.pawson@gmail.com \
    --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.