Roger Long wrote:
:"Matt O'Toole" wrote

:Also, sorry to be a pain, but your last two wonderful messages were
:almost unreadable with a text-only newsreader. There were no line breaks,
:so I had to scroll horizontally. Outlook Express is famous for such
:problems. I recommend turning HTML off and posting text-only, plus maybe
:using an add-on like OE-Quotefix. Or changing newsreaders.



:Sorry, I didn't realize, and wonder why, anyone would still be using a plain
:text only reader. Seems like those who want to cling to the Gutenburg age
:should perhaps make the adjustement instead of everyone else posing to the
:lowest technology denominator.

USENET is a text-only medium. Keeping it so keeps it efficient; using
a text-only newsreader, I can keep up with groups with much less work
and expenditure of time.

If you want flashy crap, go somewhere else. There are plenty of
mostly worthless web fora that will allow you to have flashing text
and animated smileys.


:I appreciate being able to click on links
rovided in these posts and you can't do that in plain text. Isn't there
:something you can click to force word wrap?

Being able to click on links is a function of the newsreader software,
or perhaps the terminal emulator software.

"David Scheidt" wrote

If you want flashy crap, go somewhere else.

Wraping lines of text is flashy?

-- Roger Long

Roger Long wrote:
:This is a multi-part message in MIME format.

:------=_NextPart_000_000A_01C71209.4488F360
:Content-Type: text/plain;
: charset="iso-8859-1"
:Content-Transfer-Encoding: quoted-printable

: "David Scheidt" wrote=20

: If you want flashy crap, go somewhere else. =20

:Wraping lines of text is flashy?

The html bloat is certainly crap. I've left intact the text/html
section of your response. For your 32 character response, the html
and mime requires 1331 bytes.

:-- Roger Long

:------=_NextPart_000_000A_01C71209.4488F360
:Content-Type: text/html;
: charset="iso-8859-1"
:Content-Transfer-Encoding: quoted-printable

:!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
:HTMLHEAD
:META http-equiv=3DContent-Type content=3D"text/html; =
:charset=3Diso-8859-1"
:META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR
:STYLE/STYLE
:/HEAD
:BODY bgColor=3D#ffffff
:DIVFONT face=3DArial
:BLOCKQUOTE=20
:style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
:BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"
: DIV>"David Scheidt" <A=20
: "dscheidt@panix. com/A> wrote =
:/DIV
: DIV /DIV
: DIV>If you want flashy crap, go somewhere else.  /DIV
: DIV /DIV/BLOCKQUOTE/FONT/DIV
:DIVFONT face=3DArialWraping lines of text is =
:flashy?/FONTBRBR-- Roger=20
:Long/DIV
:BLOCKQUOTE=20
:style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
:BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"FONT=20
: face=3DArial/FONT /BLOCKQUOTE/BODY/HTML

:------=_NextPart_000_000A_01C71209.4488F360--

That's very interesting and it certainly does seem inelegant and wasteful
although I can't imagine bandwith is really a problem with all the video's
being sent around.

I agree that attachements, embedded pictures, animated signatures, etc. have
no place here. It's odd though that the only complaint I've gotten about
posting since signing up as the twelth internet user in Maine (outside of
educational institutions, anyway) was for my line feeds producing broken up
text. The concensus then was, "leave the line wraps to the reader".

I recently had to reinstall Windows and OE. I don't know at this point what
format I was posting in previously. I've set it back to plain text to see
how it works. I'm curious though how it handles links like this one:

http://home.maine.rr.com/rlma

-- Roger Long

So, plain text works with the links. I'm sure now that I was using plain
text before and that my settings defaulted back to html with the reinstall.

Thanks for pointing it out. I'll sleep a little better knowing I'm saving a
few bytes to make room for all the porn videos and spam the net has to
carry

Happy now?

--
Roger Long

"Roger Long" skrev i en meddelelse
news
So, plain text works with the links. I'm sure now that I was using
plain text before and that my settings defaulted back to html with the
reinstall.

Thanks for pointing it out. I'll sleep a little better knowing I'm
saving a few bytes to make room for all the porn videos and spam the
net has to carry

Happy now?

--
Roger Long

Hello Roger,

I'm reading this newsgroup on a daily basis with great interest -
without really contributing ...but learning ... not least from your many
projects ... and illustrations on your homepage ...

For a while, however, I have really missed your contributions to this
newsgroup, and was wandering if you had left the group ...
Maybe that has something to do with your settings? ... I could however
see someone respondig to some of your remarks, but they did not appear
on my screen as coming from you, but just imbedded in other comments ...
Good to "see you again" ... Keep your settings as of now please!

Best regards
Flemming Torp
Denmark

Thanks. I've been very busy and was also completely off line for nearly a
week upgrading to a new computer after a crash. Here's something else to
pass on: When you are cleaning the dust out of your computer, take a close
look between the fins of the CPU cooler. My machine looked clean but the
cooler fins under the fan were completely choked with dust. The CPU thus
overheated.

It sounds like you might have a security or other setting set to not show
html postings. I'll post plain text from here on (Thanks, Dave) but you
might want to read what other bandwidth wasters have to say about boats.

-- Roger Long

On Mon, 27 Nov 2006 15:29:38 +0000, Roger Long wrote:

That's very interesting and it certainly does seem inelegant and wasteful
although I can't imagine bandwith is really a problem with all the video's
being sent around.

I agree that attachements, embedded pictures, animated signatures, etc. have
no place here. It's odd though that the only complaint I've gotten about
posting since signing up as the twelth internet user in Maine (outside of
educational institutions, anyway) was for my line feeds producing broken up
text. The concensus then was, "leave the line wraps to the reader".

Actually that's not the way it works. The writer should produce the line
breaks. The problem with OE is that it doesn't do this properly, and
with HTML it's worse. Turn off HTML posting and you solve half the
problem.

The reason OE screws up quoted text is that while re-wrapping it doesn't
remove old line breaks before inserting new ones. It also doesn't
recognize its own quote marks, so you wind up with in the middle of
lines. Put an HTML page through this and it ruins the HTML, making it
unreadable by machine or human.

I recently had to reinstall Windows and OE. I don't know at this point
what format I was posting in previously. I've set it back to plain text
to see how it works.

The default for OE is HTML posting. You have to change it back to plain
text.

Matt O.