Computer Old Farts Forum
 help / color / mirror / Atom feed
From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] On having a slash
Date: Tue, 14 Apr 2020 10:12:19 +1000	[thread overview]
Message-ID: <20200414001219.GA57134@eureka.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2004131832580.1535@aneurin.horsfall.org>

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

On Monday, 13 April 2020 at 19:01:13 +1000, Dave Horsfall wrote:
> 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?

It's funny that nobody seems to have differentiated these usages.
I've seen at least three:

1.  "European" characters: 1 with a serif (is that really the correct
    term?), 7 with a stroke, Z also with a stroke.  Also small u with
    a stroke above it in German, left over from the days
    („Sütterlinschrift“) when this was the only distinction between
    written u and n.  None of these had anything to do with computers.

2.  The distinction between O and 0.  Put a cross through the 0 and
    leave the O as it was.  In my experience, this too predated
    computers: I first learnt it round 1963 when trying to become a
    radio amateur, much to the disgust of my maths teacher, who also
    didn't like the hooked 1s and the crossed 7s.

3.  The distinction between O and 0.  The same as before, almost: put
    a cross through the O and leave the 0 normal.  This must be a US
    usage, since O and Ø are both valid (and different) letters in
    some Nordic languages.

Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200414/993fa3c5/attachment.sig>


  parent reply	other threads:[~2020-04-14  0:12 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 [this message]
2020-04-14  2:57 ` paul.allan.palmer
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=20200414001219.GA57134@eureka.lemis.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).