From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: eliz@is.elta.co.il, monnier+gnu/emacs@rum.cs.yale.edu,
ttn@glug.org, karl@freefriends.org, emacs-devel@gnu.org,
bob@rattlesnake.com
Subject: Re: Enhancements to options menu (was Re: Reveal mode)
Date: Wed, 8 May 2002 16:31:55 +0000 (UTC) [thread overview]
Message-ID: <m175UM7-000If6C@localhost> (raw)
In-Reply-To: <ilu1ycmhd6j.fsf@extundo.com> (message from Simon Josefsson on Wed, 08 May 2002 17:28:04 +0200)
... Perhaps HTML isn't the best format, ...
As a documentation format, HTML is broken intrinsically. HTML does
not distinguish between references to another document somewhere else
on the Internet and references to another part of the same document.
This means that you cannot design a program to search conveniently
through an HTML document that consists of more than one Web page.
Info, on the other hand, lets you navigate very conveniently through
a document using a regexp search. It is still, after more than 15
years, the single most efficient on-line documentation format in
existence, surprising as that is, and all because you can undertake a
regexp search within the document.
You could design a special format for writing an HTML document that
enables you to navigate conveniently through a document. This would be
an add-on to HTML.
HTML's built-in failure was designed as a feature: it was based on
the assumption that you would never create a document more than one
Web page long; and that that document should be able to link to any
other document on the World Wide Web.
But what about DocBook?
You can create Info documents from DocBook; thus you gain efficient
navigation, which you lose when you convert the same document to HTML.
However, people who write in DocBook often fail to consider the
various output formats that are available. For example, they may not
consider writing for a person who is driving a car and listening to
their work. The authors tend to write as if every reader will *look*
at the page. This is not a problem of the format, but of the
sociology of the document writing process.
A very good rule of thumb: write your document so that a blind person
can follow it easily. Then, even if no blind person ever reads it,
the document will be easily followed by a sighted person who is
looking at the document. (Incidentally, this rule of thumb also
applies to Web page design.)
When you figure out how to show images in an Emacs session running
over a fast local network with a windowing system, please also, at the
same time, figure out how to show the same document to someone running
in a character-only mode over a slow network (my recent experience has
taken me below 300 baud), and at the same time, figure out how to
present the same document to someone who is `situationally blind'
while driving a car, or permanently blind.
--
Robert J. Chassell bob@rattlesnake.com
Rattlesnake Enterprises http://www.rattlesnake.com
next prev parent reply other threads:[~2002-05-08 16:31 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 21:19 Reveal mode Richard Stallman
2002-05-01 20:30 ` Pavel Janík
2002-05-01 23:34 ` Enhancements to options menu (was Re: Reveal mode) Kim F. Storm
2002-05-02 5:16 ` Enhancements to options menu Karl Eichwalder
2002-05-02 11:39 ` Per Abrahamsen
2002-05-02 20:20 ` Kim F. Storm
2002-05-02 23:48 ` Karl Eichwalder
2002-05-03 18:25 ` Enhancements to options menu (was Re: Reveal mode) Richard Stallman
2002-05-03 23:54 ` Kim F. Storm
2002-05-04 0:39 ` Thien-Thi Nguyen
2002-05-04 8:58 ` Pavel Janík
2002-05-05 23:15 ` Stefan Monnier
2002-05-07 15:38 ` Pavel Janík
2002-05-07 16:33 ` Simon Josefsson
2002-05-07 18:24 ` Eli Zaretskii
2002-05-07 19:11 ` Simon Josefsson
2002-05-08 0:27 ` Miles Bader
2002-05-08 2:51 ` Colin Walters
2002-05-08 3:06 ` Stefan Monnier
2002-05-08 16:10 ` Miles Bader
2002-05-08 4:50 ` Eli Zaretskii
2002-05-08 11:24 ` Per Abrahamsen
2002-05-08 13:33 ` Eli Zaretskii
2002-05-08 13:43 ` Stefan Monnier
2002-05-08 13:57 ` Eli Zaretskii
2002-05-08 14:05 ` Stefan Monnier
2002-05-08 14:15 ` Eli Zaretskii
2002-05-08 15:28 ` Simon Josefsson
2002-05-08 15:43 ` Alan Shutko
2002-05-12 5:26 ` Karl Eichwalder
2002-05-12 5:35 ` Eli Zaretskii
2002-05-08 15:46 ` Miles Bader
2002-05-08 16:31 ` Robert J. Chassell [this message]
2002-05-08 18:51 ` Eli Zaretskii
2002-05-08 15:27 ` Karl Eichwalder
2002-05-08 16:30 ` Stefan Monnier
2002-05-09 14:59 ` Richard Stallman
2002-05-09 16:53 ` Karl Eichwalder
2002-05-09 17:59 ` Eli Zaretskii
2002-05-09 18:26 ` Karl Eichwalder
2002-05-09 18:59 ` Eli Zaretskii
2002-05-08 14:02 ` Kai Großjohann
2002-05-08 15:31 ` Simon Josefsson
2002-05-08 15:55 ` Kai Großjohann
2002-05-07 23:59 ` Stefan Monnier
2002-05-08 6:03 ` Thien-Thi Nguyen
2002-05-08 13:37 ` Stefan Monnier
2002-05-08 13:59 ` Richard Stallman
2002-05-04 9:32 ` Alex Schroeder
2002-05-04 15:01 ` Richard Stallman
2002-05-04 18:44 ` Kim F. Storm
2002-05-05 17:45 ` Richard Stallman
2002-05-05 22:24 ` Kim F. Storm
2002-05-06 4:48 ` Eli Zaretskii
2002-05-06 6:30 ` Miles Bader
2002-05-06 9:17 ` Kim F. Storm
2002-05-06 19:32 ` Richard Stallman
2002-05-06 19:32 ` Richard Stallman
2002-05-06 23:12 ` Kim F. Storm
2002-05-07 20:07 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 18:30 Karl Berry
2002-05-07 19:22 ` Eli Zaretskii
2002-05-08 17:11 Karl Berry
2002-05-08 17:19 ` Alan Shutko
2002-05-08 17:27 Karl Berry
2002-05-08 17:40 ` Miles Bader
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=m175UM7-000If6C@localhost \
--to=bob@rattlesnake.com \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=karl@freefriends.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=ttn@glug.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).