[access-uk] Re: E-mail Guidance
- From: "George Bell" <george@xxxxxxxxxxxxxxxxxxx>
- To: <access-uk@xxxxxxxxxxxxx>
- Date: Mon, 4 Apr 2005 15:02:11 +0100
You've more or less answered your own question about short
lines, Ray.
I've generally found that a line length of 65 suit most
situations.
Of course, if someone has a narrow reading window, you're
still back to the old problem, but there's little one can do
about that.
George.
> -----Original Message-----
> From: access-uk@xxxxxxxxxxxxx
> [mailto:access-uk@xxxxxxxxxxxxx] On Behalf Of Ray's Home
> Sent: 04 April 2005 14:59
> To: access-uk@xxxxxxxxxxxxx
> Subject: [access-uk] Re: E-mail Guidance
>
> Thanks for that informative post. (This being a 'top
posting'
> you'll see Tinks original below.)
>
> I'd only add that one article I read on the net mentioned
as
> well as plain text being much prefered, that line length
> should be kept to sixty or seventy characters at most.
His
> argument being that longer line lengths often did not fit
> propperly in peoples'
> email clients or else you got the mess of shortened lines
in
> some messages. Speaking of which, does anyone know how to
> avoid those anoying short lines, often every other line?
And
> much more important , how to reformat to get rid of them?
> Ray
>
> Personal emails: Email me at
> mailto:ray-48@xxxxxxxx
>
> ----- Original Message -----
> From: "Tink Watson" <tink@xxxxxxxxxx>
> To: <access-uk@xxxxxxxxxxxxx>
> Sent: Monday, April 04, 2005 2:46 PM
> Subject: [access-uk] Re: E-mail Guidance
>
>
> Sam,
>
> Much of this comes down to personal taste, even the
oldest of
> Internet
> conventions have largely been superceded by people's own
> preferences.
>
> For my part, I'd advise using plain text to send and
receive
> email
> messages, but I've outlined the pros and cons of both
plain text
> and html
> emails below.
>
> Plain text emails are smaller to send and receive,
because
> they don't
> allow the inclusion of graphics or web page style
formatting. For
> this
> reason, they are more secure than HTML email messages,
> particularly when you
> are on the receiving end of one, because there is no place
to
> hide possible
> email nasties.
>
> HTML emails are slightly larger to send and receive,
because
> the allow
> for the inclusion of graphics and web page style
formatting. It
> is possible
> for malware or unwanted code to be triggered via an HTML
email,
> particularly
> if you are on the receiving, rather than sending end of
things.
>
> Another classic argument you'll come across with
email, is
> whether to
> top post, bottom post or integrate. Again, I've given a
bit of an
> outline of
> each below:
>
> Top posting is what happens on most VI related lists.
When
> replying to
> an email, you hit the reply button and just begin typing
at the
> top. We find
> this easier because of the way our assistive technologies
work.
>
> Bottom posting used to be the convention on the
Internet,
> particularly
> in the days of UseNet, but it has now fallen by the
wayside a
> little for all
> but a hardy few. This involves hitting the reply button on
an
> email and
> typing your text in immediately under the person's
original email
> text.
>
> Integrating is a combination of the two. You
customarily
> start typing at
> the top of the email, but either cut and paste quotes of
the
> original into
> the main body of your text, or add your text at various
points
> throughout
> the original mail.
>
> My personal rule of thumb is to top post, except where
I
> think a brief
> reminder of the original post might be useful to the
reader, in
> which case
> I'll cut and paste the relevant quote to a suitable point
in my
> reply. Most
> of the VI lists are fairly easy going on this, but I've
come
> across some
> newsgroups and mailing lists, where this is a sore topic
of
> contention.
>
> Ultimately, keep emails short, to the point, as
friendly as
> possible.
> Add in graphics if they are needed, but otherwise try to
avoid
> doing so. Use
> plain text, rather than HTML by convention and use top
posting
> when
> replying, except if a quote would be useful. At least,
that's
> pretty much
> the way I do it. *Smile.
>
> Tink.
>
>
>
>
> ----- Original Message -----
> From: "Howie, Sam" <Sam.Howie@xxxxxxxxxxxxxxxxx>
> To: "Access-Uk (E-mail)" <access-uk@xxxxxxxxxxxxx>
> Sent: Monday, April 04, 2005 2:21 PM
> Subject: [access-uk] E-mail Guidance
>
>
> Hi All
>
> I have been asked by a colleague to give some advice in
terms of
> writing
> e-mail messages. Does anyone know of any guidance around
about
> writing
> e-mails in terms of size, best style of text to use what
about if
> they
> wanted to include pictures and so on.
>
> Any advice will be appreciated
> Cheers
> Sam
>
>
>
------------------------------------------------------------
--
> --------------
> Disclaimer:
> This message is intended only for use of the addressee. If
this
> message
> was sent to you in error, please notify the sender and
delete
> this message.
> Glasgow City Council cannot accept responsibility for
viruses, so
> please
> scan attachments. Views expressed in this message do not
> necessarily reflect
> those of the Council who will not necessarily be bound by
its
> contents.
>
------------------------------------------------------------
--
> --------------
>
> ** To leave the list, click on the immediately-following
link:-
> **
[mailto:access-uk-request@xxxxxxxxxxxxx?subject=unsubscribe]
> ** If this link doesn't work then send a message to:
> ** access-uk-request@xxxxxxxxxxxxx
> ** and in the Subject line type
> ** unsubscribe
> ** For other list commands such as vacation mode, click on
the
> ** immediately-following link:-
> ** [mailto:access-uk-request@xxxxxxxxxxxxx?subject=faq]
> ** or send a message, to
> ** access-uk-request@xxxxxxxxxxxxx with the Subject:- faq
>
>
> ** To leave the list, click on the immediately-following
link:-
> **
[mailto:access-uk-request@xxxxxxxxxxxxx?subject=unsubscribe]
> ** If this link doesn't work then send a message to:
> ** access-uk-request@xxxxxxxxxxxxx
> ** and in the Subject line type
> ** unsubscribe
> ** For other list commands such as vacation mode, click on
the
> ** immediately-following link:-
> ** [mailto:access-uk-request@xxxxxxxxxxxxx?subject=faq]
> ** or send a message, to
> ** access-uk-request@xxxxxxxxxxxxx with the Subject:- faq
>
>
>
> ** To leave the list, click on the immediately-following
link:-
> **
[mailto:access-uk-request@xxxxxxxxxxxxx?subject=unsubscribe]
> ** If this link doesn't work then send a message to:
> ** access-uk-request@xxxxxxxxxxxxx
> ** and in the Subject line type
> ** unsubscribe
> ** For other list commands such as vacation mode, click on
the
> ** immediately-following link:-
> ** [mailto:access-uk-request@xxxxxxxxxxxxx?subject=faq]
> ** or send a message, to
> ** access-uk-request@xxxxxxxxxxxxx with the Subject:- faq
>
>
This Message has been scanned for viruses by McAfee Groupshield.
** To leave the list, click on the immediately-following link:-
** [mailto:access-uk-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** access-uk-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:access-uk-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** access-uk-request@xxxxxxxxxxxxx with the Subject:- faq
Other related posts: