From: Ron Marriage <marriage@seidata.com>
To: blinux-list@redhat.com
Subject: Re: AFT -- Almost free text.
Date: Fri, 11 Jan 2002 16:52:50 -0500 [thread overview]
Message-ID: <3C3F5EB2.82700E99@seidata.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0201111507000.7539-100000@dave.private.mielke.cc>
I often have to supply documents or reports to a group or
committee of sighted people.
In almost all cases, I'm the computer guy and most of them
can reach the level of reading their email and either can't
or don't want to go further.
They expect these reports to carry a company logo at the
top, have a title centered and in a large font, the want
lists indented and like that little thingie in front of them
so they know it really is a list. They want important stuff
in red or someother color.
They might want charts and they always want a summary or
index on the first page.
While ascii is my most used format, I am forced to use HTML
or some other formating technique so that they can see what
they want or expect.
It isn't that ascii isn't recognized by word, it's that I
want my documents to look professional, that I want them to
look like my boss or a committe of sighted members expect
them to be.
It's not that they wouldn't accept straight ascii text from
me. They would be happy to do so, they'd just assume that
it was the best the blind guy could do.
Ron
Dave Mielke wrote:
>
> [quoted lines by Charles McCathieNevile on January 11, 2002, at 12:42]
>
> >Aaah. The value of this tool (which I am imagining through my experience of a
> >tool called txt2html) is that it recognises common text formatting
> >conventions (which can vary from page to page) and converts them into markup
> >which is richer and more explicit. If it is a reasonably good tool, and
> >txt2html certainly is, so I imagine it will be, it is useful.
>
> I understand that, but am still perplexed. Isn't Word smart enough to do that
> for itself? I still don't understand the need to use a clever common format
> detecter to prepare the plain text file before it's passed on to the Word user.
> I'd understand if the original user intended to maintain the document in its
> new format from then on, but that, at least to me, didn't appear to be the
> case.
>
> --
> Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the
> Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me
> EMail: dave@mielke.cc | Canada K2A 1H7 | if you're concerned about Hell.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
--
Ron Marriage
Homepage http://www.seidata.com/~marriage/
Email mailto:marriage@seidata.com
Linux User Group http://www.seidata.com/~seilug/
Blind Links http://www.seidata.com/~marriage/rblind.html
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin G. McCormick
` Dave Mielke
` Charles McCathieNevile
` Dave Mielke
` Ron Marriage [this message]
` Dave Mielke
` Charles McCathieNevile
` Luke Davis
-- strict thread matches above, loose matches on Subject: below --
Ian Blackburn
` Luke Davis
Gil Andre
` Dave Mielke
` Gil Andre
` Dave Mielke
` Gil Andre
` Dave Mielke
` Charles McCathieNevile
` Dave Mielke
` Luke Davis
` ddunfee
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=3C3F5EB2.82700E99@seidata.com \
--to=marriage@seidata.com \
--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).