From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: A problem with units
Date: Sat, 24 Nov 2012 01:39:43 +0100 [thread overview]
Message-ID: <CAF=dkzw5p1AQ_B53Wtu4D=1UkW-b406xxu4Tk5nvqnDPVoou3A@mail.gmail.com> (raw)
In-Reply-To: <20121123235619.40993358@aga-netbook>
Marcin wrote:
> being quite happy with things like \unit{10 km/h}, once I did \unit{45
> min}, only to get "45 m" in the resulting file. I suspect that \unit
> does not know about minutes; is there any way to teach it;)?
I think 'min' is parsed as 'meter nil nil', because (1) min is not
found in the list of short or long unit names, so it's assumed to be
composite; and (2) once processed composite, m-->meter-->m, while
i-->nil and n-->nil.
Solution: add 'min' to the list of short unit names (below).
Cheers,
Sietse
% phys-dim.lua
local short_units = { -- I'm not sure about casing
m = "meter",
Hz = "hertz",
hz = "hertz",
B = "bel",
b = "bel",
lx = "lux",
-- da = "dalton",
h = "hour",
s = "second",
g = "gram",
n = "newton",
v = "volt",
t = "tonne",
l = "liter",
-- w = "watt",
W = "watt",
-- a = "ampere",
A = "ampere",
+ min = "minute",
[utfchar(0x2103)] = "celsius",
[utfchar(0x2109)] = "fahrenheit",
}
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-11-24 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 22:56 Marcin Borkowski
2012-11-24 0:39 ` Sietse Brouwer [this message]
2012-11-24 9:54 ` Hans Hagen
2012-11-25 13:32 ` Marco Patzer
2012-11-24 7:50 ` Romain Diss
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='CAF=dkzw5p1AQ_B53Wtu4D=1UkW-b406xxu4Tk5nvqnDPVoou3A@mail.gmail.com' \
--to=sbbrouwer@gmail.com \
--cc=ntg-context@ntg.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).