ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Mon, 21 Nov 2011 12:00:30 +1100	[thread overview]
Message-ID: <DB58BA22-BAE2-4A01-8DF3-8540436015B7@csiro.au> (raw)
In-Reply-To: <mailman.0.1321614002.10878.ntg-context@ntg.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2033 bytes --]

On 18/11/2011, at 10:00 PM, Pontus Lurcock <pont@talvi.net> wrote:

> On Fri 18 Nov 2011, Hans Hagen wrote:
>> so, best is that those asking for it come up with a list of issues:
>> which symbols need this option, is it language related or whatever,
>> so that i can do them all at once. We can already have different
>> mapping sets so spacing could be part of that.
> 
> I don't personally have a need for units in the foreseeable future (I
> was just nitpicking with Robin about spacing) so feel free to ignore
> any of my suggestions, but I think the summary so far would be:
> 
> 1. Spacing for almost all SI units should be the same and doesn't
>   need special cases.
> 
> 2. Geographical degrees/minutes/seconds should have no spaces.
> 
> 3. Spacing for degrees temperature varies according to different style 
>   guides -- both before and after the ° -- so ideally it would be
>   possible to set these independently of the rest of the units.
> 
> For my own part I would add:
> 
> 4. SI unit abbreviations are mostly capital letters, and look (to me)
>   strange with old-style figures. I have seen books which used 
>   old-style figures for page numbers, years, etc. but switched to
>   lining figures when a unit was involved; this is also what I did
>   in my thesis. So I think it would be useful to allow an automatic
>   switch to lining figures to be configured when typesetting a unit.
> 
> Pont

I agree on points 1 and 2 (although it seems arcminute and arcsecond are
not implemented anyway). Point 3, yes, but I'm dubious about space after °
for the temperature units °C or °F as it breaks the rule about unit
ambiguity ("° C" is a degree-Coulomb -- although I can't image a physical
situation that would need such a unit). Point 4 is a bit beyond the scope
of the SI units scheme but sounds like a potential need.

Over the weekend I've discovered a couple more problems with \unit so I'll
make up some test cases and desired output and post it in a few days.

Robin

[-- Attachment #1.2: Type: text/html, Size: 3535 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
___________________________________________________________________________________

       reply	other threads:[~2011-11-21  1:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1321614002.10878.ntg-context@ntg.nl>
2011-11-21  1:00 ` Robin Kirkham [this message]
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
     [not found] <mailman.707.1321583719.4232.ntg-context@ntg.nl>
2011-11-18  3:10 ` Robin Kirkham
2011-11-18  3:31   ` Pontus Lurcock
2011-11-18  7:26     ` Hans Hagen
2011-11-18  9:28       ` Pontus Lurcock
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=DB58BA22-BAE2-4A01-8DF3-8540436015B7@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).