From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: skyhorse--- via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] new units
Date: Sun, 7 May 2023 10:22:35 +0200 [thread overview]
Message-ID: <d38fb35d-c944-97bb-fb49-b563c2e67360@freedom.nl> (raw)
In-Reply-To: <20230506161031.7650@sachi>
On 5/7/2023 2:10 AM, skyhorse--- via ntg-context 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.
Sure, but it's not a unit in tex like 10ft so reporting 19 feet looks a
bit odd for the (majority) texusers who dont'use feet. (we have mm and
cm but not in and ft). I suppose yards could also have been used but
probably points out more prominently the limitation.
https://nl.wikipedia.org/wiki/Voet_(lengtemaat)
An amsterdam voet being somewhat smaller actually would have made 20
which is a nicer number and also fits the base 20 inuit system discussed
a few weeks ago.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 8:23 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
2023-05-07 8:22 ` Hans Hagen via ntg-context [this message]
-- 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=d38fb35d-c944-97bb-fb49-b563c2e67360@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/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).