> Yes, correct.
>
[quoted text clipped - 24 lines]
> > John Fields
> > Professional Circuit Designer
So whats up with the request to bottom post ..
what is convenient for some is a pain for others
when you have people that insist on posting the whole
post of the previous poster, its a pain to have to
scroll thru the history to get to a one line answer.
bottom posting never did make sense
cbarn24050@aol.com wrote in <1151549381.945040.139300
@i40g2000cwc.googlegroups.com>:
>> Yes, correct.
>>
[quoted text clipped - 26 lines]
>
>A simple capacitor/diode clamp circuit would seem to do
John Fields - 29 Jun 2006 19:47 GMT
>So whats up with the request to bottom post ..
>
[quoted text clipped - 5 lines]
>
>bottom posting never did make sense
---
When you're inconsiderate of others who may come to the thread some
time after it started, then it may not seem to make much sense, even
though it does. You don't read a book backwards, and it's
inconsiderate to force others to read a series of articles
chronologically backwards.
Even Google thinks so.
From:
http://groups.google.com/support/bin/answer.py?answer=12348&topic=250
"Summarize what you're following up.
When you click "Reply" under "show options" to follow up an existing
article, Google Groups includes the full article in quotes, with the
cursor at the top of the article. Tempting though it is to just
start
typing your message, please STOP and do two things first.
Look at the quoted text and remove parts that are irrelevant.
Then, go to the BOTTOM of the article and start typing there.
Doing this makes it much easier for your readers to get through your
post. They'll have a reminder of the relevant text before your
comment, but won't have to re-read the entire article.
And if your reply appears on a site before the original article
does,
they'll get the gist of what you're talking about."
---
BTW, speaking of being considerate, you need to clean up your
punctuation as well as learn to top-post as the Romans do.

Signature
John Fields
Professional Circuit Designer
JeffM - 29 Jun 2006 20:10 GMT
>So whats up with the request to bottom post ..
> Mike_in_SD
It called "When in Rome...".
>what is convenient for some is a pain for others
Stop being selfish--or find a Web-based forum.
>when you have people that insist on
>posting the whole post of the previous poster,
They are (generally speaking) totally wrong and stupid.
>its a pain to have to scroll thru the history
>to get to a one line answer.
That would be DIRECT evidence that the idiot who posted that
doesn't know what he is doing.
If someone does in fact need that much context (see below),
he should probably be middle-posting (as I have done here).
>bottom posting never did make sense
When you see it done wrong, it's easy to ASSuME that.
Do you constantly use
the WORST examples you come across in your daily life as templates
or consider them to be excuses for making up your own rules.
Here's the proper technique on Usenet:
1) TRIM OUT anything that does not
DIRECTLY correspond to your response.
2) Make your addition BELOW that
so that what results will read like a *dialog*
--not an event and a flashback.
jasen - 30 Jun 2006 09:59 GMT
["Followup-To:" header set to sci.electronics.misc.]
> So whats up with the request to bottom post ..
it puts stuff in chronological (or conversation) order.
> when you have people that insist on posting the whole
> post of the previous poster, its a pain to have to
> scroll thru the history to get to a one line answer.
That's what the page-down key is for.
having to scroll to the bottom of the post to see what your talikng
about and then back up to the message is worse.
Bye.
Jasen