💾 Archived View for dj-chase.com › documents › pleasant-html-mail.html captured on 2024-08-18 at 18:16:11.

View Raw

More Information

⬅️ Previous capture (2024-03-21)

-=-=-=-=-=-=-

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8">
    <title>
      Pleasant HTML Mail
    </title>
    <meta name="generator" content="//dj-chase.com/Make.py">
    <link rel="stylesheet" href="../style.css?cache-bust=2024-02-15">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
  </head>
  <body>
    <nav>
      <a href="#start">Skip to start</a>
      <!-- screen-reader–only p -->
      <p>You are here:</p>
      <ol>
        <li><a href="/" aria-label="home">⌂&nbsp;<span>›</span></a></li>
        <li><a href="/documents/">documents&nbsp;<span>›</span></a></li>
        <li><a href="/documents/pleasant-html-mail.gmi">pleasant-html-mail.gmi</a></li>
      </ol>
    </nav>
    <main id="start">
      <h1>
        Pleasant HTML Mail
      </h1>
      <p>
        I’ve always found HTML email to be unpleasant (even before I knew about HTML vs plain-text email), but it’s always been just an annoyance. However, I now use a <abbr title="Terminal User Interface">TUI</abbr> mail client (<a href="https://aerc-mail.org/">aerc</a>), so HTML emails are downright unreadable.
      </p>
      <p>
        I solved this by preprocessing HTML mails with <code>lynx -dump -stdin</code>, which turned out to be surprisingly pleasant. Because Lynx behaves like a filter in this mode, it just turns HTML emails into nicely-formatted plain-text emails. I say “nicely formatted” because lynx indents its output according to the document’s structure, which is particularly nice for long newsletters.
      </p>
      <p>
        For example, the FSF is really good about providing a plain-text alternative to their newsletters. The problem, though, is that their newsletters are really long, so parts of it can easily get buried.
      </p>
      <p>
        Here’s an example of their plain-text newsletter:
      </p>
      <pre>
# Newsletter Title

## First article title

Paragraphs and paragraphs of text.

## Second article title

Paragraphs and paragraphs of text.

## Third article title

You get the picture.
</pre>
      <p>
        But then here’s an example of their HTML newsletter run through lynx:
      </p>
      <pre>
                               Newsletter Title

First article title

   Paragraphs and paragraphs of text.


Second article title

   Paragraphs and paragraphs of text.


Third article title

  You get the picture.
</pre>
      <hr class="light">
      <p>
        I normally wouldn’t write a post about such a small thing, but I was so pleasantly surprised by this that I wanted to share it.
      </p><!-- html code generated by txt2tags 3.3 (http://txt2tags.org) -->
      <footer>
        <p>
          Questions, comments, or wrote a reply? <a href="mailto:u9000@posteo.mx">Email me</a>.
        </p>
        <p>
          ©&nbsp;DJ Chase 2022-08-30. Licensed under the Academic Free License (AFL&nbsp;3.0).
        </p>
        <p>
          <a href="/cgi-bin/cite.sh">Cite this page</a>
        </p>
        <p>
          <a href="https://u9.tel/pleasant-html-mail">Short link</a>
        </p>
      </footer><!-- cmdline: txt2tags  -->
    </main>
  </body>
</html>