The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] attachments: MIME and uuencode
Date: Sun, 12 Mar 2017 18:28:13 -0700	[thread overview]
Message-ID: <20170313012813.GN2685@mcvoy.com> (raw)
In-Reply-To: <CAEoi9W5KakkesPKydvNTXSJUQi2K8X66=BFBdzOFdbAiYazL6Q@mail.gmail.com>

On Sun, Mar 12, 2017 at 08:34:27PM -0400, Dan Cross wrote:
> Or when the project management consultants ask to see your requirements
> document and you send it to them in troff and they write back, "I can't
> open this in Word." Sigh.
> 
> One of my pet peeves when I got my first job outside of a university
> environment was that I was expected to drop all of the tools I'd been
> accustomed to using and start using "the standard", which basically meant
> something Microsoft based. Even though I was running FreeBSD on my
> workstation, and not Windows NT. It was somewhat maddening; whenever I
> tried to use Windows I felt like I was typing in jello because it was so
> unfamiliar.

Yep, agreed.  I fought the good fight in my company, our commercial
contract is a troff document (complete with troff's version of #ifdef so I
sourced a generic MLA, an Intel specific one, a Cisco specific one, an HP
specific one, an educational one, and something else I'd have to go look).

Invariably the customers would suck the roff output into word and wack
it and send it back.  I built up tools to deal with that, I'd export
back to text and then run it through something I call pfmt which 
reformats stuff such that each sentence starts on a new line.
That made it very easy to diff and see changes.

This actually caught some really bad behaviour on HP's part (this is
all ancient history so I doubt anyone cares).  They sucked it into Word,
turned on track changes, made some minor changes, then turned off track
changes and made some major changes.  If I had been trusting Word's
history we would not have noticed the major changes.  But I didn't,
I caught them, when they were presented to HP they did the classic
"however did that happen, we have no idea, blah, blah, blah".  Pretty
darn sleazy.

--lm

P.S.  For those of you who are business guys, yeah, every single customer
we have ever had has been on our paper.  Including Intel.  We may be the
only small company that can make that claim.


  reply	other threads:[~2017-03-13  1:28 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 [this message]
2017-03-13  5:39       ` Dave Horsfall
2017-03-13 11:37   ` Steffen Nurpmeso
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=20170313012813.GN2685@mcvoy.com \
    --to=lm@mcvoy.com \
    /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).