From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: skyhorse--- via ntg-context <ntg-context@ntg.nl>
Cc: Alan Braslau <alan.braslau@icloud.com>
Subject: Re: [NTG-context] new units
Date: Sat, 6 May 2023 20:51:38 -0600 [thread overview]
Message-ID: <20230506205138.4a4f9691@boo.my.domain> (raw)
In-Reply-To: <20230506161031.7650@sachi>
On Sat, 06 May 2023 16:10:31 -0800
skyhorse--- via ntg-context <ntg-context@ntg.nl> wrote:
>
>
> Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
> >......
> > Oh, so a bug, I'll fix the message. Not really a unit but then, feet
> > is also not one.
> >
>
> That is incorrect. Feet is an establish and proper unit of
> measurement, which consists of 12 inches. It is used by, at least,
> several hundred million people. It can be said that the ability to
> grok and manipulate fractions has many benefits, which the metric
> system sorely lacks.
The inch is properly defined as *exactly* 2.54cm.
So the foot is a proper unit defined as 12*2.54cm.
Manipulating fractions, I stated, is the entire point of Imperial
measurements.
Now go figure: Physical Review Letters once objected to my publishing a
graph without units on the abscissa. I satisfied the editor by adding
$[m\times m^{-1}]$ (my graph was in radians).
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-05-07 2:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 0:10 skyhorse--- via ntg-context
2023-05-07 2:43 ` Michael Urban via ntg-context
2023-05-07 6:09 ` Mikael Sundqvist via ntg-context
2023-05-07 8:15 ` Hans Hagen via ntg-context
2023-05-07 2:51 ` Alan Braslau via ntg-context [this message]
2023-05-07 8:22 ` Hans Hagen via ntg-context
-- strict thread matches above, loose matches on Subject: below --
2023-05-04 8:01 Hans Hagen via ntg-context
2023-05-06 16:45 ` Alan Braslau via ntg-context
2023-05-06 19:40 ` Hans Hagen via ntg-context
2023-05-06 21:53 ` Arthur Rosendahl via ntg-context
2023-05-06 23:29 ` Hans Hagen via ntg-context
2023-05-07 9:10 ` Henning Hraban Ramm via ntg-context
2023-05-07 9:29 ` Mojca Miklavec via ntg-context
2023-05-07 10:04 ` Hans Hagen via ntg-context
2023-05-07 10:06 ` Hans Hagen via ntg-context
2023-05-07 9:45 ` Hans Hagen via ntg-context
2023-05-07 10:09 ` Henning Hraban Ramm via ntg-context
2023-05-07 10:29 ` Hans Hagen via ntg-context
2023-05-07 15:56 ` Henning Hraban Ramm via ntg-context
2023-05-07 14:56 ` Hans Hagen via ntg-context
2023-05-07 12:00 ` Bruce Horrocks via ntg-context
2023-05-07 13:07 ` Hans Hagen via ntg-context
2023-05-07 15:58 ` Alan Braslau via ntg-context
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=20230506205138.4a4f9691@boo.my.domain \
--to=ntg-context@ntg.nl \
--cc=alan.braslau@icloud.com \
/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).