From: khm@sciops.net (Kurt H Maier)
Subject: [TUHS] Fun with early troff.
Date: Tue, 8 May 2018 13:43:42 -0700 [thread overview]
Message-ID: <20180508204342.GA58741@wopr> (raw)
In-Reply-To: <CAEoi9W7fNWOLv=Ad3r6HKBTZGH3w=vhxejXcNuSuGzmzpCvY1Q@mail.gmail.com>
On Tue, May 08, 2018 at 04:14:54PM -0400, Dan Cross wrote:
>
> For example, there is a NATO-standard "10-line" message
When did they add the 10th line? What is in it? I was trained on the
9-line during my service, and I'd be fascinated to know what extra info
was judged important enough to update the manuals.
>
> Yup. Troff. I took it to war.
>
It's been well over a decade, but there were QRF bases in Kabul whose
security manuals and operation maps were generated onsite in TeX on my
ancient Thinkpad. I suspect, however, an academic study of combat-zone
typesetting would be dominated by the inevitability of Powerpoint.
I've often noticed the battlefield is ruled by Windows (e.g. those
pilots were probably poking at Falconview) while the research side is
extremely tied to unix and its ilk. Obviously BRLCAD and other ARL
involvement here, and just about all of of the DoD HPC program skews
toward unix and linux.
khm
next prev parent reply other threads:[~2018-05-08 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 17:44 Ron Natalie
2018-05-08 17:51 ` Larry McVoy
2018-05-08 18:02 ` Ron Natalie
2018-05-08 20:14 ` Dan Cross
2018-05-08 20:43 ` Kurt H Maier [this message]
2018-05-08 22:01 ` Dan Cross
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=20180508204342.GA58741@wopr \
--to=khm@sciops.net \
/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).