Computer Old Farts Forum
 help / color / mirror / Atom feed
From: paul.allan.palmer at gmail.com (Paul Palmer)
Subject: [COFF] On having a slash
Date: Mon, 13 Apr 2020 21:57:46 -0500	[thread overview]
Message-ID: <CAM6ucknvQKFYem3v2UFKdi36DLv1c4oyW0uXumqS1yBQr4W1-Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2004131832580.1535@aneurin.horsfall.org>

Did anyone ever find a font with these characters? Preferably one I can use
with TeX.

Thanks

On Mon, Apr 13, 2020, 4:01 AM Dave Horsfall <dave at horsfall.org wrote:

> Way back then, when dinosaurs strode the earth and System/360 reigned
> supreme, we were taught to slash our zeros and sevens (can't quite find
> the glyphs for them right now) in order to distinguish them from Oscars
> and Ones for the benefit of the keypunch girls (yes, really; I had the
> hots for one of them at one time, but someone else took her) on those
> green sheets.
>
> In the time-mean I also saw a slash through "Z" (Zulu, Zed, Zee) in order
> to distinguish it from a "2" (FIGURES TWO); WTF?  And you *never* slashed
> your ones, lest thou ended up with the contents of an 029 chad-box over
> thine head...
>
> These days, I merely slash my sevens by habit and it doesn't even raise an
> eyebrow; even Oz Pigeon Post's mail mangler seems to accept it[*].
>
> What're other bods' experiences?
>
> [*]
> Don't even mention Redfern, OK?  Just don't...  And as for getting off at
> Redfern, well, I did a few times when I had a contract job around there.
>
> -- Dave, bored at home
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200413/551ea2c3/attachment.html>


  parent reply	other threads:[~2020-04-14  2:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  9:01 dave
2020-04-13 11:30 ` david
2020-04-13 12:38   ` clemc
2020-04-13 14:10     ` mike.ab3ap
2020-04-13 14:21       ` thomas.paulsen
2020-04-13 14:23         ` imp
2020-04-13 12:53   ` paul
2020-04-13 14:12     ` imp
2020-04-13 15:29   ` krewat
2020-04-13 15:40     ` pdagog
2020-04-13 13:21 ` thomas.paulsen
2020-04-13 13:23 ` cym224
2020-04-13 13:36   ` 
2020-04-13 17:35   ` paul
2020-04-13 22:09     ` dave
2020-04-14 13:34       ` dfawcus+lists-coff
2020-04-14 14:23         ` gdmr
2020-04-13 22:12     ` krewat
2020-04-13 23:21       ` dave
2020-04-14  0:12 ` grog
2020-04-14  2:57 ` paul.allan.palmer [this message]
2020-04-13 15:14 rudi.j.blom

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=CAM6ucknvQKFYem3v2UFKdi36DLv1c4oyW0uXumqS1yBQr4W1-Q@mail.gmail.com \
    --to=coff@minnie.tuhs.org \
    /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).