From: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: questions regarding `\date`
Date: Tue, 31 Aug 2010 14:14:50 +0200 [thread overview]
Message-ID: <20100831121450.GB24714@aides> (raw)
In-Reply-To: <4C7CEA52.9090501@elvenkind.com>
[-- Attachment #1.1: Type: text/plain, Size: 1985 bytes --]
On 2010-08-31 <13:41:06>, Taco Hoekwater wrote:
> On 08/31/2010 11:48 AM, Philipp Gesang wrote:
> >unfortunately I can only come up with a negative answer: I
> >skimmed the Bringhurst and although he does discuss date strings
> >with slashes as separators,
>
> The Chicago manual (14ed) says that slashed/dotted dates are bad style
> and should be avoided and that one should use full month names instead.
>
> Best wishes,
> Taco
That's what I prefer, too. Bringhurst (v.3.2, p. 81f.) only uses
the date as an example for the opposition virgule/solidus and
states that “[i]t is useful in dates [...] and in text where a
comma or parenthesis might otherwise have been used”. He does not
give general advice wrt typesetting of dates.
For the record, p. 406 of the TeXbook has this:
··8<············································································
\def\today{\ifcase\month\or
January\or February\or March\or April\or May\or June\or
July\or August\or September\or October\or November\or December\fi
\space\number\day, \number\year}
··8<············································································
Ergo common spaces.
Philipp
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 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 prev parent reply other threads:[~2010-08-31 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 14:02 Paul Menzel
2010-08-28 18:54 ` Wolfgang Schuster
2010-08-28 19:02 ` Peter Münster
2010-08-28 19:10 ` Wolfgang Schuster
2010-08-28 20:51 ` Wolfgang Schuster
2010-08-29 10:17 ` Wolfgang Schuster
2010-08-31 8:29 ` Paul Menzel
2010-08-31 9:48 ` Philipp Gesang
2010-08-31 11:41 ` Taco Hoekwater
2010-08-31 12:14 ` Philipp Gesang [this message]
2010-08-31 13:03 ` Martin Schröder
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=20100831121450.GB24714@aides \
--to=pgesang@ix.urz.uni-heidelberg.de \
--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).