AVK> Mistake #1 on your side: you think plain ASCII is a limitation of some
AVK> (unknown to me) sort, whereas _I_ think ASCII is a _power_, a well-thought
AVK> standard that those guys who invented "soft returns" and things alike (read:
AVK> M$ with its Word and heaps of others) just plain spoiled.
Soft returns and ASCII aren't even like comparing apples to oranges,
more like comparing horses to trees. Soft returns can be poorly
implemented or not, but in the end anyone who thinks any editor of any
power simply has a huge buffer with only text in it representing the
document is kidding themselves.
Not that I know the first thing about writing an editor, but I've
thought about it and can't imagine it's an easy thing to do well.
AVK> Well, it follows that _your_ choice is Word's way of doing
AVK> things, despite your dislike towards M$.
Word didn't invent the soft return, fwiw.
AVK> There's _nothing_ in word- processing world that cannot be done
AVK> (and done _better_) with just plain ASCII. Wanna examples? TeX
AVK> for typesetting...
Am I the only one that remembers that TeX does way more than you
typically need for email? Not to mention it's not exactly "human
readable."
Also, to bring the topic back to where it seems to have started, am I
the only one who remembers that paragraph breaks in TeX are specified
by a blank line?
AVK> I'd prefer the editor NOT to use those soft returns at all. I do not use soft
AVK> returns in my work. I do not use Word and wordprocessors alike. And I'm still
AVK> alive, and my health is perfect;-)
If you are using auto-format, you're using soft returns. There's no
two ways about it.
AVK> Did you read what I had written? Was my English unclear? I said that this is a
AVK> matter of the quantities of programming work needed to implement it this or
AVK> that way.
There are better editors available for less money. What's the (your)
point?
>> Simple. The block which is a paragraph is the one defined with a hard CR
>> and the one that is not is defined with a soft CR. How TB! defines those is
>> up to the internal logic which is, as I demonstrated, not limited to the logic
>> of the transmit medium.
AVK> Then algorithms are necessary that convert one form to another and vice
AVK> versa. The implementation of the "soft-hard" way of editing from the ground
AVK> up. In short, you want the editor to be rewritten...
No "algorithms" any more powerful than are already part of the "build
the SMTP stream" are needed. See a "soft CR" tag, send "CR". See a
"hard CR" tag, send a "CR". A lot easier than, say, implementing an
autoformat mode that causes users all sorts of irritation.
So yeah, technically that's an algorithm, but I tend to not think of
"if/then" logic as particularly algorithmic simply because they're so
easy to understand and implement.
-tom!
--
Hopin' this said *something* useful, [EMAIL PROTECTED] out.
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
