From: Steffen Nurpmeso <sdaoden@yandex.com>
To: discuss@mdocml.bsd.lv
Cc: <des@des.no>
Subject: Re: Mdocdate
Date: Sat, 14 Nov 2015 16:02:01 +0100 [thread overview]
Message-ID: <20151114150201.btVpSjagp%sdaoden@yandex.com> (raw)
In-Reply-To: <20151114012201.GL7344@athene.usta.de>
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
next prev parent reply other threads:[~2015-11-14 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 9:25 Mdocdate Dag-Erling Smørgrav
2015-11-12 21:31 ` Mdocdate Ingo Schwarze
2015-11-12 23:06 ` Mdocdate Ingo Schwarze
2015-11-13 5:52 ` Mdocdate Dag-Erling Smørgrav
2015-11-14 1:22 ` Mdocdate Ingo Schwarze
2015-11-14 15:02 ` Steffen Nurpmeso [this message]
2015-11-15 1:51 ` Mdocdate Ingo Schwarze
2015-11-16 13:35 ` Mdocdate Steffen Nurpmeso
2015-11-17 9:12 ` Mdocdate Svyatoslav Mishyn
2015-11-17 10:35 ` Mdocdate Steffen Nurpmeso
2015-11-23 20:48 ` Mdocdate Michael Dexter
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=20151114150201.btVpSjagp%sdaoden@yandex.com \
--to=sdaoden@yandex.com \
--cc=des@des.no \
--cc=discuss@mdocml.bsd.lv \
/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).