From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] attachments: MIME and uuencode (fwd)
Date: Mon, 13 Mar 2017 08:35:33 -0700 [thread overview]
Message-ID: <20170313153533.GB24086@mcvoy.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1703132341000.794@aneurin.horsfall.org>
Hey Steve,
I'll take a crack at porting these if you don't mind. I hate word
and if your docx2troff can tease apart a word doc into roff, that
would be *awesome*.
On Mon, Mar 13, 2017 at 11:41:51PM +1100, Dave Horsfall wrote:
> I think this was supposed to go public...
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
>
> ---------- Forwarded message ----------
> Date: Mon, 13 Mar 2017 11:39:45 +0000
> From: Steve Simon <steve at quintile.net>
> To: dave at horsfall.org
> Subject: Re: [TUHS] attachments: MIME and uuencode
>
> I still actively fight office. I wrote docx2troff and xlsx2txt.
>
> The former can extract txt or troff source from modern (DOCX / OPC) document
> as can the latter though, by their nature excel tables don't map well to tbl(1).
>
> These are written for plan9 and so the libraries are a bit different,
> but they could be ported to unix without too much pain.
>
> Shout if anyone is interested.
>
> -Steve
> Date: Mon, 13 Mar 2017 16:39:29 +1100 (EST)
> From: Dave Horsfall <dave at horsfall.org>
> To: The Eunuchs Hysterical Society <tuhs at tuhs.org>
> Subject: Re: [TUHS] attachments: MIME and uuencode
>
> On Sun, 12 Mar 2017, Larry McVoy wrote:
>
> [...]
>
> > 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.
>
> A former boss of mine used to get quotes in Word all the time (we were a
> Unix house); he used to run "strings" against the document, and challenge
> the supplier with the fact that they were giving a competitor a better deal.
>
> To this day, "strings" is still my best Word decoder...
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
prev parent reply other threads:[~2017-03-13 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 12:41 Dave Horsfall
2017-03-13 15:35 ` Larry McVoy [this message]
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=20170313153533.GB24086@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).