| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Trojan 55808 |
From: "Rich"
This is a multi-part message in MIME format.
------=_NextPart_000_041B_01C33780.174E87F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Strange. I can't remember the last time I read some published =
material that did not use fonts, formatting, and more, even color, to = get
enhanced expressiveness and readability. Maybe you've can find = something
published in the last few decades too if you look around.
The quote from the article is not the quoted text of the replied to =
message. You're aversion to formatting appears to limit your =
imagination. As for text from the replied to message, the vertical bar =
is more efficient in space. In size it may or may not depending on what =
is quoted. It is also clearer which makes it more efficient where it =
matters.
If KNode is not wrapping lines correctly than it does have a =
standards compliance problem. You should take them up with them.
As for "plain text is more efficient", if you believe that blanket =
statement than you are being silly or even foolish. You don't identify =
the criteria you use to judge efficiency. I'm sure you can find one for =
which this is true. I don't know about you but to me the efficiency for =
the human being operating the computer as a tool is more important than =
the efficiency of the computer. Then again maybe you take Adam = Flinton's
position that leads him to type "b4" instead of
"before". It = may be that he is more concerned with the number
of key presses for him = than he is with the readability to others of what
he posts. Is this the = kind of efficiency which you are promoting? It is
fewer bytes.
MIME compliant means to comply with the MIME RFCs only one small =
aspect of which is the Content-Transfer-Encoding. The bug in KNode you =
described in having to scroll to the right is a problem with the KNode =
implementation of RFC 2045.
Rich
"Brian Hall" wrote in message =
news:3ef3cb10{at}w3.nls.net...
Rich wrote:
> I use HTML for some of the same reasons that the web is primarily =
HTML.
> It's expressive. I used it to indent the quoted text in my first
> message.
This is not the web. Plain text is expressive if you say what you =
mean.=20
HTML decorations add nothing to the discussion.
I can indent too and I didn't need to use HTML to do it. There =
is a key
on most keyboard labeled "Tab" that can be used to indent =
plain text.
My newsreader inserts a little symbol called a "greater than sign" to=20
denote the quoted text. It seems to work well without adding bloat.
> Are you having problems because your newsreader, KNode, is
> not standards compliant and displays the raw text of the message
> instead of just the text part?
I have it set to display the plain text part and show anything else as =
an=20
attachment. Your posts do not word wrap correctly and I have to scroll =
to=20
the right to read them. I only have a problem with messages from =
people who=20
use HTML. The majority of people here are intelligent enough to =
realize=20
that plain text is more efficient.
> In the messages you post KNode claims
> to be MIME compliant. Maybe it doesn't know how to display the =
more
> expressive HTML part.
MIME compliant means it can decode/uncompress MIME compressed data and =
produce/encode MIME compressed data for an attached binary, not that =
it=20
will surround my text with a bunch of useless markup.
Brian
------=_NextPart_000_041B_01C33780.174E87F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Strange. I can't =
remember the=20
last time I read some published material that did not use fonts, = formatting, and=20
more, even color, to get enhanced expressiveness and readability.
= Maybe=20
you've can find something published in the last few decades too if you = look=20
around.
The quote
from the article =
is not the=20
quoted text of the replied to message. You're aversion to = formatting=20
appears to limit your imagination. As for text from the replied to =
message, the vertical bar is more efficient in space. In size it
= may or=20
may not depending on what is quoted. It is also clearer
which = makes=20
it more efficient where it matters.
If KNode
is not wrapping =
lines=20
correctly than it does have a standards compliance =
problem. You=20
should take them up with them.
As
for "plain text is =
more=20
efficient", if you believe that blanket statement than you
are = being silly=20
or even foolish. You don't identify the =
criteria you=20
use to judge efficiency. I'm sure you can find one for
which = this is=20
true. I don't know about you but to me the efficiency for the =
human being=20
operating the computer as a tool is more important than the efficiency = of the=20
computer. Then again maybe you take Adam Flinton's position that
= leads him=20
to type "b4" instead of "before". It may be
that he is more = concerned with=20
the number of key presses for him than he is with the readability to = others of=20
what he posts. Is this the kind of efficiency which you are=20
promoting? It is fewer bytes.
MIME
compliant means to =
comply with=20
the MIME RFCs only one small aspect of which is the=20
Content-Transfer-Encoding. The bug in KNode you described in =
having to=20
scroll to the right is a problem with the KNode implementation of RFC=20
2045.
Rich
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 270 @PATH: 379/45 1 106/1 2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.