Nathan (gemsling) wrote,

Newsletters: PDF, HTML, multipart

Perceptions are interesting. Theresa, who has become one of the core members of Shoestring Theatre Company, is charged with doing their monthly newsletter. Upon receiving her first draft (HTML email), John said it should be sent in PDF format. The reason? It will feel more like a "real" newsletter.

So, to cater to perceptions, the newsletter becomes less accessible, comes attached to an email that says nothing about the contents (though Theresa could add a summary or ToC if she wished), and is only seen if recipients can be bothered opening the attachment.

The question is, what is the right way to do email newsletters or announcements? I've been thinking about this, because, as the moderator of Hartwell's mailing list, I'm hoping to exert a little quality control over it.

Plain text is good for purists like me, but formatted text aids reading, especially for long messages and newsletters. However, many email clients have little or no support for HTML.

The solution is to use multipart/alternative: send both a text version and an HTML version and let the client choose.

But how do you create it and send it? Sure, most programs will do it, but a) they have limited support for making good HTML and b) they automatically create the plain text version, which means you don't get control over the plain text layout.

After much searching, I've finally found out how to create multipart/alternative using mutt. Well, it's new functionality, so I'll need the development version.

1. Create HTML message.
2. Format plain text version.
3. Attach both in mutt (plain text first for non MIME clients).
4. Group them together and send.

Tags: accessibility, html, theatre

  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded