The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] attachments: MIME and uuencode
Date: Mon, 13 Mar 2017 12:37:45 +0100	[thread overview]
Message-ID: <20170313113745.lSbbS%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAC20D2N80ZsD3+jd=T=Jc6Ofh3wQfTxB167yKUFDzCnnvATpqw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

Clem Cole <clemc at ccc.com> wrote:
 |On Sun, Mar 12, 2017 at 2:13 PM, Doug McIlroy <[1]doug at cs.dartmouth.edu[/1]\
 |> wrote:
 |
 |  [1] mailto:doug at cs.dartmouth.edu
 |
 |And it's an annoying chore when companies I actually want
 |to deal with send receipts and the like in (godawful) HTML only.
 |
 |Or when your HR and Legal dept sends legal documents (like tax info \
 |and patent disclosures )  using XPS instead of PS or PDF and wonder \
 |why much of the 
 |company can not or will not read it when "legal can read it just fine."

And market power is actively misused by major players, but which
is possibly the only natural aspect of them: Google simply uses
Cascading-Style-Sheets to create quotes, which is fine per se, but
it does this by using a "class gmail_quote" without giving the
actual definition of it, forcing everbody all around the world to
special treat "gmail_quote", otherwise it will look like above.
There is not even an external reference to the CSS.

  Content-Type: text/html; charset=UTF-8
  Content-Transfer-Encoding: quoted-printable

  <div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
  On Sun, Mar 12, 2017 at 2:13 PM, Doug McIlroy <span dir=3D"ltr">&lt;<a href=

Turning off the HTML text part takes a button click (or took once
i looked last) ... and it turns out to be too much work.  Even
that.

--steffen


  parent reply	other threads:[~2017-03-13 11:37 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 18:13 Doug McIlroy
2017-03-12 18:22 ` Larry McVoy
2017-03-12 18:26 ` Clem Cole
2017-03-13  0:34   ` Dan Cross
2017-03-13  1:28     ` Larry McVoy
2017-03-13  5:39       ` Dave Horsfall
2017-03-13 11:37   ` Steffen Nurpmeso [this message]
2017-03-13 20:21     ` Steffen Nurpmeso
2017-03-13 22:14       ` Doug McIlroy
2017-03-14 10:49         ` Steffen Nurpmeso
2017-03-12 18:33 ` Paul Winalski
2017-03-13  5:58   ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2017-03-12 20:04 Noel Chiappa
2017-03-12 21:34 ` Random832
2017-03-12 22:12   ` Noel Chiappa
2017-03-13 14:58     ` Michael Kjörling
2017-03-13 21:56       ` Dave Horsfall
2017-03-14 10:33         ` Steffen Nurpmeso
2017-03-16 18:52         ` Michael Kjörling
2017-03-12 18:57 Andy Valencia
2017-03-12 15:10 Noel Chiappa
2017-03-11 19:07 Mary Ann Horton
2017-03-11 23:01 ` Paul Winalski
2017-03-11 23:05   ` Mary Ann Horton
2017-03-12  1:14     ` Dan Cross
2017-03-12  6:28       ` jsteve
2017-03-12 23:41         ` Gregg Levine
2017-03-13  0:00           ` Larry McVoy
2017-03-13  1:59             ` Dave Horsfall
2017-03-12 23:43       ` Mary Ann Horton
2017-03-12 21:10   ` Dave Horsfall
     [not found]     ` <12de3888-3a82-4a8c-9177-50e6cb4cb931.maildroid@localhost>
2017-03-19  2:34       ` Dave Horsfall
2017-03-12 13:53 ` Tim Bradshaw
2017-03-12 17:42 ` Clem Cole
2017-03-12 23:35   ` Mary Ann Horton
2017-03-13  0:07     ` Clem Cole
2017-03-13  0:09     ` Warren Toomey
2017-03-13  0:11       ` Clem Cole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170313113745.lSbbS%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).