From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from forward20p.cmail.yandex.net (forward20p.cmail.yandex.net [77.88.31.15])
	by fantadrom.bsd.lv (OpenSMTPD) with ESMTP id 7bc349e3
	for <discuss@mdocml.bsd.lv>;
	Sat, 14 Nov 2015 10:02:16 -0500 (EST)
Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [IPv6:2a02:6b8:0:1402::118])
	by forward20p.cmail.yandex.net (Yandex) with ESMTP id 5A10021100;
	Sat, 14 Nov 2015 18:02:11 +0300 (MSK)
Received: from smtp17.mail.yandex.net (localhost [127.0.0.1])
	by smtp17.mail.yandex.net (Yandex) with ESMTP id 35CC71901462;
	Sat, 14 Nov 2015 18:02:11 +0300 (MSK)
Received: by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id de8ABuvmQA-2An4CUst;
	Sat, 14 Nov 2015 18:02:10 +0300
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(Client certificate not present)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1447513330;
	bh=kk439pK9fL9cEs6vMuAZn6sfe7GOc5cwWMwHR6JQR1w=;
	h=Date:From:To:Cc:Subject:Message-ID:References:In-Reply-To:
	 Mail-Followup-To:User-Agent;
	b=hVx/OxAgeDsWiyHWSr3wdIJ6Srxq+a85XgAtZDKHCK/oXgt16pjPJmahSFbOaKgfL
	 mOdMTRzMJi8ikxCwq1YlmAd/dK6s4llx4CTUTy5AQ0G82LK/otBJ3VXdkgesLzezeY
	 DY/yTm7ziNfiFw0JruLzwVUN5AzlDPdH296bJnTM=
Authentication-Results: smtp17.mail.yandex.net; dkim=pass header.i=@yandex.com
X-Yandex-ForeignMX:  NO
Date: Sat, 14 Nov 2015 16:02:01 +0100
From: Steffen Nurpmeso <sdaoden@yandex.com>
To: discuss@mdocml.bsd.lv
Cc: <des@des.no>
Subject: Re: Mdocdate
Message-ID: <20151114150201.btVpSjagp%sdaoden@yandex.com>
References: <86r3jva7s9.fsf@desk.des.no>
 <20151112213135.GL20023@athene.usta.de> <86r3jua1ja.fsf@desk.des.no>
 <20151114012201.GL7344@athene.usta.de>
In-Reply-To: <20151114012201.GL7344@athene.usta.de>
Mail-Followup-To: discuss@mdocml.bsd.lv,
 <des@des.no>
User-Agent: s-nail v14.8.5-145-g8facf61
X-Mailinglist: mdocml-discuss
Reply-To: discuss@mdocml.bsd.lv

Hello,

Ingo Schwarze <schwarze@usta.de> wrote:
 |Hi Dag-Erling,

 |generate non-portable output.  Actually, it might be possible with
 |a bit of effort to get similar patches into groff and Heirloom,
 |Werner and Carsten are usually very helpful - but i'm not convinced
 |the format you propose makes much sense.  We really don't need
 |seconds and timezones in .Dd, and i wouldn't know how to explain
 |the need to Werner and Carsten.  Rather than trying to change the
 |world, i think it makes more sense to teach SVN to generate .Dd

but i think ISO 8601 / RFC 3339 "full-date" would be a useful
extension since they are (a) standardized and well-known and (b)
locale / charset agnostic and worldwide relatively (it is a
Gregorian date in the end) easy perceivable.
I lack the overview, but localized manpages have to ship with
those english / american dates, too?  So no, now that groff's mdoc
has been extended to support mdocml's cvs(1) tag natively i think
i'll add ISO 8601 YYYY-MM-DD to my mdoc copy once i come to
development of my roff fork, and add a Savannah bug report with
the patch, then.

--steffen
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv