Phred wrote:
| In article <
[email protected]>,
||
|| And, please, I still don't know what the hell you're talking
|| about. Perhaps someone would be willing to clarify?
|
| It seemed clear enough to me, provided you take note of the
| conventional USENET "attrributions" symbols.
|
| Spelled out: He and others are saying PT should tell us what
| the hell his stuff is about, at least in summary, rather than
| simply posting an URL (or is that "a U R L"
.
|
| Cheers, Phred.
Phred,
Here is the content of the message in question. This is the post
that immediately followed the first cryptic one.
"On 19 Feb 2004 15:24:20 -0800, in alt.comp.freeware,
(e-mail address removed) (*
ProteanThread *), wondering whence the lambs & piglets, bleated &
squealed:
|
http://www.wieringsoftware.nl/utils/
--
What portion of [the] below did you fail to comprehend?
-
On Thu, 19 Feb 2004 22:37:14 -0000, in alt.comp.freeware, "Steven
Burn"
<
[email protected]>, wondering whence the lambs & piglets,
bleated &
squealed:
| ||
http://www.alstonlabs.com/
|
| ProteanThread,
| Will you please start posting descriptions (even
if they're
| just basic one's) instead of URL's on their own.
-
Message-Id:
[email protected]"
How am I supposed to make sense of this? Please explain.
It appears that there may have been something missing or that
netiquette order has been skewed. Or there's just too much
"potatoes" between the "meats."
From your explanation, it begins to dawn on me that Vrodok and I
have been in agreement! This was not obvious to me from the
content and the order of the content, and especially all the
clutter.
(Aside: to answer your question, "...or is that 'a U R L,'" In
essence, the sounds of speech often govern written text. "A
universal...." and "a URL" or "a U.R.L" are all correct. This can
get really complicated, so I'll quickly nip the grammer lesson
here.)
I say that things on usenet and emails would be easier to follow
if we all snipped clutter from our responses. However, I allow
that adding additional clutter to posts, especially when
repetitive, is something I don't like. I'm a fan of clear,
concise communication. I'll admit that the "pigs and sheep" stuff
gets to me; it gets to me fast, and it gets to me really really
fast when I see it for the second time, especially when it is
repeated in a quote. It just is not cute the second time: it is
annoying (to me, anyway).
This is one bit of feedback about how stuff like this is
received, at least, by some readers. Please everyone, don't add
irrelevant "entertainment," especially the automated variety, to
your posts! If you look at this post, you'll see lots of
clutter: quoted posters' addresses, article IDs, and, yes, the
pigs and sheep. To further confuse, many posters use one "handle"
for posting, and another name to sign their post. Somtimes this
is done for fun, sometimes to try to prevent spam. Added up, it
makes my head spin.
-----------------------------------------------------------------
------
There are built-in problems with "plain text" posting. The ASCII
character set and conventions that we all follow on usenet are,
in fact, very old. They evolved from the telegraph conventions
that superseded morse code. (we're probably going back to the
1930s here). Those conventions, with some enhancements, were
carried into the teletype systems used both by telegraph
companies and the news wire services. Those enhancements were
carried whole into IBM's "Extended ASCII Character Set," of the
first IBM PCs. For example, the symbol "BEL" means "Bell," a
physical bell in the teletype machine that went "Ding Ding Ding."
This is how the typist alerted the recipients of an important
breaking news story. The more "dings," the more important the
story. The teletype machines, essentially robust electric
typewriters, could not print underlines and bold without
backspacing. They could not backspace reliably and maintain text
synchronization. They had one font, in one size, like any other
typewriter. Therefore, text enhancements were never part of the
teletype tradition. You used ALL CAPS for enhancement, and that
was that. You rang the bell for attention.
What I've explained is the origins of the limited character set
that we use for standard usenet posting and email. The lack of
text enhancements cause confusion in comprehension. The type
conventions of Macintosh and Windows give us a lot more in the
way of comprehending text: here we can view italics, underline,
bold, fonts, font sizes, and other formatting, all of which
improve communication. These did not evolve from telegraph
origins, but from the printing and publishing trades. Quite a
difference.
Having said that, I believe in plain text, even though it is
often hard to sort out.
Why? Because it is universal! Plain text is standard among all
the platforms that I have ever known. (Please pardon me if you
are from a part of the world for which what I'm saying is
foreign; many special systems were incorporated, such as the "Al
Arabi" conversions, for adapting the PC for a different language
and region). Windows introduced us to enhanced text attributes in
their proprietary "Outlook" integrated office system, in turn
carried into "Outlook Express" for the peasants. But these text
enhancements are not standard: initially, no computer other than
a Windows machine, could render them on the screen. The internet
was already established when Windows 3.0 took flight. Well, we're
on the internet, so we can't use that stuff. OK.
BRINGING THIS ALL HOME
If we are going to read each others' posts on every possible
platform, we've got to send it out in plain text. In other words,
for sanity, one should switch the settings in Outlook Express to
"plain text" in both directions. One should also obey the
standard conventions of netiquette for the same reason. However,
as I've explained above, in doing so, we sacrifice reading
clarity to universality. This means that the system that we use
gets quickly confusing to the reader when the posts are complex.
More so when we try to improve things by top posting and snipping
stuff (I am as guilty as anyone else, I guess). We futz around
and it "sort-of works;" (and often doesn't).
So, I'm requesting that we all remove anything that adds clutter
or obfuscation. Let's start by eliminating all slogans and
phrases from the beginnings and endings of our posts (the pigs
and lambs have got to go). This includes the little nasties that
Yahoo tacks on to out posts: if you have a choice, please send
from your paid "real" internet account if there's no way to get
Yahoo to behave themselves.
I admit that I've given a long speech here about how we do
things. I figured that it might be nice to have given a context
and a history about why we post the way that we do, and how it
relates to clarity problems we still are stuck with. I hope that
this has been successful and that we can all get along with it.
Richard