begin Monday 21 June 2004 18:15, Bob Hentges quote:
Howdy all,
I was just wondering what you people think of witting messages in text
format = flowed to mailing lists - instead of the commonly used line
break at char 72 or wherever.
An overlong line by any other name is still an overlong line (if that
is what you mean by "text format flowed") ;-)
Accepted netiquette is indeed to keep line length under 80 characters
(or even 72, in order to leave room for quote characters, in case your
message is replied to). Most online netiquette guides seem to agree on
this:
http://www.use-net.ch/netiquette_engl.html#lines :
Limit Line Length and Avoid Control Characters
Try to keep your text in a generic format. Many (if not most) of the
people reading Usenet do so from 80 column terminals or from
workstations with 80 column terminal windows. Try to keep your lines
of text to less than 80 characters for optimal readability. If
people quote part of your article in a followup, short lines will
probably show up better, too.
http://www.eschkitai.de/openoffice/netikette.html#zeile :
12. Die Zeilenlänge beträgt höchstens 72 Zeichen
Begrenze die Zeilenlaenge im Text auf höchstens 72 Zeichen, noch
besser wären 68 Zeichen. So bleibt der Zeilenumbruch auch nach
mehrmaligem Quoting erhalten.
http://www.scibermentor.ca/mentor/netiquette_page_1_mentors.htm :
For lengthy messages, try to keep the length of lines in your email
below 70 characters; short lines are easier to read, especially on a
computer screen. Other people's terminals may not be able to display
more than 70 characters, so they may not be able to read the ends of
long lines.
http://www.cs.cornell.edu/courses/cs312/2002sp/netiquette.htm :
Line lengths
Like your code, posts and email should not have excessively long
lines. This generally means 80 characters per line maximum. It is
annoying for the reader to have to scroll to read long lines.
Fortunately, most email clients make it intentionnally difficult to
violate this guideline. If ever you need longer lines for a good
reason (for instance, for quoting shell commands, or for extra-wide
ASCII drawings), you need to switch off this safety. In kmail, for
instance, you can do this by unchecking Options->Wordwrap . However,
as pointed out above, this should only be done in exceptional
circumstances.
I am conscious that basically a whitespace
at EOL is bad(TM), and the the evil OE aka Outlook Express will not
quote correctly when replying to a message written in flowed mode - but
still...
If the goal is to discourage people to use Outlook Express, there are
other methods than using long lines. One idea, for instance is to use
the word "begin" followed by two spaces at the start of a line ;-)
what is your opinion concerning text format flowed ?
;-)
Friendly,
Bob Hentges
Regards,
Alain