In article <[log in to unmask]>, dated Wed, 9 Dec 1998
at 11:25:28, David Meldrum <[log in to unmask]> writes
>Is it allowable in the charter to send messages in char sets that upset
>some browsers ?
It's less a matter of what is allowed and more one of 'common sense'.
The only MIME header that should appear in mail being distributed to
people whose email application MIME compatibility is indeterminable
(e.g. most mailing lists) is
>MIME-Version: 1.0
The above simple identifies the sender as MIME compliant and therefore
capable of receiving and (in theory!) displaying satisfactorily MIME
encoded/encapsulated email. Any other MIME headers and content
potentially increase reading difficulty in non-MIME compliant email
applications and should therefore be avoided, assuming of course the
sender wishes their words of wisdom to be read by the largest possible
audience! The same applies to HTML whether it is included as part of a
MIME encapsulation or in raw form. The former usually comes with a plain
text alternative which is nice for those of us with good MIME compliant
email applications but again is to be avoided for reasons already
mentioned.
Chris
--
Chris Salter (Vice Chairman) Lincolnshire Post-Polio Network
Registered Charity No. 1064177
<URL:http://www.zynet.co.uk/ott/polio/lincolnshire/>
Web Site & Vice Chairman Email: [log in to unmask]
Honorary Secretary Email: [log in to unmask]
Member of the British Healthcare Internet Association
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|