public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Charles McCathieNevile <charles@w3.org>
To: <blinux-list@redhat.com>
Subject: Re: AFT -- Almost free text.
Date: Fri, 11 Jan 2002 11:37:20 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0201111133170.32074-100000@tux.w3.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0201111019060.7539-100000@dave.private.mielke.cc>

The value of a richer format (Word, for those who have Word, HTML, for those
who have a browser, etc) is that it can include more information. For
example, borwsers can extract the headings from an HTML page and present a
"page outline" (word does a similar thing, and did it first) that should give
a good guide to where the important parts are - a simple table of contents
with some idea of the relative importance. Or can skip over a list of items
easily. Or can extract a list of the links (many JAWS users navigate by this
technique, because they learn it early, although it isn't nearly as powerful
for reading documents as an outline view).

etc.

The worst case is that users still just get plain text. The best case is that
they get a lot more information, that was once only encoded by means of
fairly visually-oriented formatting conventions derived from paper, and have
tools that can do useful things with it.

cheers

Charles McCN

On Fri, 11 Jan 2002, Dave Mielke wrote:

  That doesn't answer my question. A simple text file is no more than a simple
  text file. It has very little inherrent formatting in it. Converting it to rtf,
  html, or even all the way to Word, can't improve on that, so why does it need
  to be done before handing it off to a Word user. What's wrong with giving the
  Windows user the plain old text file and letting Word convert it from plain
  text into its own format?

  What am I missing? Perhaps Word can't read a plain text file. If that's so,
  then I stand corrected? If it can, then why use something else to convert the
  document for it?



-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)




  reply	other threads:[~ UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gil Andre
 ` Dave Mielke
   ` Gil Andre
     ` Dave Mielke
       ` Gil Andre
         ` Dave Mielke
           ` Charles McCathieNevile [this message]
             ` Dave Mielke
       ` Luke Davis
 ` ddunfee
 Martin G. McCormick
 ` Dave Mielke
   ` Charles McCathieNevile
     ` Dave Mielke
       ` Ron Marriage
         ` Dave Mielke
       ` Charles McCathieNevile
 ` Luke Davis
 Ian Blackburn
 ` Luke Davis

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=Pine.LNX.4.30.0201111133170.32074-100000@tux.w3.org \
    --to=charles@w3.org \
    --cc=blinux-list@redhat.com \
    /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.
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).