From: dfawcus+lists-coff at employees.org (Derek Fawcus)
Subject: [COFF] On having a slash
Date: Tue, 14 Apr 2020 14:34:03 +0100 [thread overview]
Message-ID: <20200414133403.GB46873@clarinet.employees.org> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2004140752350.1535@aneurin.horsfall.org>
On Tue, Apr 14, 2020 at 08:09:21AM +1000, Dave Horsfall wrote:
> On Mon, 13 Apr 2020, Paul Guertin wrote:
>
> > I would love to see a study correlating the serif length on 1 with both
> > the age of the writer and the place he or she learned to write. Most
> > Europeans write ones with serifs, but while some of them write normal
> > serifs, others go full CVS receipt and end up with serifs longer than
> > the character they're seriffing.
I (raised in England), in my early 50s:
draw a 1 as simply a vertical stroke, no serifs
draw a 7 without any bar, but did see that being used by some while in middle school
draw an 4 'open', rather than 'closed'
draw 0 variably depending upon context
A 0 usually without slash, occasionaly with a slash when writing code
or it would otherwise be ambiguous (licence codes, etc).
We tended to view the stroked 7 as a Continental practice, but some people adopted it.
As to your question about spaces, I do it as Paul described - a short of shallow bucket.
> I (English-born, Aussie-bred) use s short serif and underline on the "1".
Aha - so you were pulling our legs with your phrasing of the subject.
DF
next prev parent reply other threads:[~2020-04-14 13:34 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 [this message]
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
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=20200414133403.GB46873@clarinet.employees.org \
--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).