From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] On having a slash
Date: Tue, 14 Apr 2020 08:09:21 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2004140752350.1535@aneurin.horsfall.org> (raw)
In-Reply-To: <c4d90b45-c9a8-39ea-3416-24514e543454@guertin.net>
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 (English-born, Aussie-bred) use s short serif and underline on the "1".
Hmmm... My MacBook puts a dot in the middle of the "0" (zero) and
serifs/underlines the "1" too.
I make spaces visible with a sort of a musical "flat" symbol but with a
short bar through it, write a tab as a short right arrow, and for me it's
always ^C etc (which is how they're echoed).
Part of my background is formal message-passing in emergency
communications, whereby the written message *must* be correct as that will
what will be sent (even spelling and grammatical errors, which used to
irritate me although I am allowed to query the author).
Ahhh... The Tower of Babel when it comes to something that must by
definition be precise :-)
-- Dave (VK2KFU)
next prev parent reply other threads:[~2020-04-13 22:09 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 [this message]
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
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=alpine.BSF.2.21.9999.2004140752350.1535@aneurin.horsfall.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).