From: Dave Mielke <dave@mielke.cc>
To: <blinux-list@redhat.com>
Subject: Re: AFT -- Almost free text.
Date: Fri, 11 Jan 2002 15:10:24 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.30.0201111507000.7539-100000@dave.private.mielke.cc> (raw)
In-Reply-To: <Pine.LNX.4.30.0201111240240.32074-100000@tux.w3.org>
[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.
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 [this message]
` Ron Marriage
` 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=Pine.LNX.4.30.0201111507000.7539-100000@dave.private.mielke.cc \
--to=dave@mielke.cc \
--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).