From: Robin Kirkham <robin.kirkham@csiro.au>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: \unit and Hertz, lux, and degrees/minutes/seconds
Date: Fri, 18 Nov 2011 14:10:42 +1100 [thread overview]
Message-ID: <D67AF36A-2F5A-4CDA-AF10-7A1924E9022B@csiro.au> (raw)
In-Reply-To: <mailman.707.1321583719.4232.ntg-context@ntg.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1044 bytes --]
On 18/11/2011, Pontus Lurcock <pont@talvi.net> wrote:
>>> Degrees, minutes and seconds of arc (also degrees Celsius) are an
>>> exception and are not supposed to have any space between the
>>> digits and the degree symbol [1], so to be correct, I think
>>> Context should by default veto any space between digits and
>>> numbers, in these cases only.
>>
>> Correction, I should have written "(but not degrees Celsius)",
>> apologies.
>
> Conventions for setting the degrees of temperature symbol vary; see
> http://en.wikipedia.org/wiki/Degree_symbol#Typography and references
> therein. In most professionally published works that I've seen, there
> is no space between the number and the °, or between the ° and the C.
Pont,
I agree they vary, and no space before the °C is quite common (and frequently my own practice too). However in setting default behaviour for Context I am inclined to favour conforming to international standards, where they exist (but a \setupunits override it probably called for).
Robin
[-- Attachment #1.2: Type: text/html, Size: 3390 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 parent reply other threads:[~2011-11-18 3:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.707.1321583719.4232.ntg-context@ntg.nl>
2011-11-18 3:10 ` Robin Kirkham [this message]
2011-11-18 3:31 ` Pontus Lurcock
2011-11-18 7:26 ` Hans Hagen
2011-11-18 9:28 ` Pontus Lurcock
[not found] <mailman.0.1321614002.10878.ntg-context@ntg.nl>
2011-11-21 1:00 ` Robin Kirkham
2011-11-21 9:52 ` Hans Hagen
2011-11-24 12:36 ` Robin.Kirkham
2011-11-24 12:58 ` Wolfgang Schuster
2011-11-25 9:29 ` Ian Lawrence
2011-11-25 10:00 ` Hans Hagen
2011-11-24 13:42 ` Romain Diss
2011-11-24 20:18 ` Pontus Lurcock
2011-11-25 8:18 ` Hans Hagen
2011-11-25 13:54 ` Wolfgang Schuster
2011-11-25 8:29 ` Hans Hagen
2011-11-27 10:59 ` Robin.Kirkham
2011-11-18 2:05 Robin Kirkham
2011-11-18 2:12 ` Robin Kirkham
2011-11-18 2:35 ` Pontus Lurcock
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=D67AF36A-2F5A-4CDA-AF10-7A1924E9022B@csiro.au \
--to=robin.kirkham@csiro.au \
--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).