"the basic intent is to provide visual clues"
Well, this is a limited approach, generated exactly by the fact that some
programmers don't really care about all those who read, but care the most
about their own preferences.
I am blind and the visual clues don't mean anything, but make the things
harder to understand.
If I need to read a thread of many email messages, which are usually
received in a separate folder for each mailing list, and where the messages
can be grouped by threads, I *already* know very well what that thread is
all about, and I don't need to re-read or skip tens of lines just in order
to read 2 or 3 new lines.
So top-posting is recommended for this reason.
The problem is that most perl programmers are (for the moment) Linux users,
and usually the mail clients under Linux are configured by default in such a
way that they make easier bottom-posting.
So, for this reason, I use to bottom-post on perl mailing lists, just
because this is the preference of the majority, and if I need some help, I
need to put the questions in such a way that those who know more like it,
because they surely don't care that there are people that just can't use a
mouse or a monitor.
What I don't like, and this is also not recommended is to include the entire
text of previous messages.
But again, some mail clients know how to hide the quoted text of previous
messages, so their users don't care that other users can't use those mail
clients because they are not accessible for screen readers.
Octavian
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
