discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Cc: Thomas Klausner <wiz@NetBSD.org>, Jason McIntyre <jmc@kerhand.co.uk>
Subject: Re: deprecate .Tn and .Ux
Date: Wed, 30 Jul 2014 13:56:18 +0200	[thread overview]
Message-ID: <20140730115618.GA2142@acme.spoerlein.net> (raw)
In-Reply-To: <20140623204144.GE619@iris.usta.de>

On Mon, 2014-06-23 at 22:41:44 +0200, Ingo Schwarze wrote:
> Hi Thomas,
> 
> Thomas Klausner wrote on Mon, Jun 23, 2014 at 10:15:31PM +0200:
> > On Mon, Jun 23, 2014 at 09:55:35PM +0200, Ingo Schwarze wrote:
> 
> >> Hmm...  Any comments from other BSDs, or whom do you think
> >> should we ask about this in your projects, in case you fear
> >> people might get upset about it?
> 
> > I don't have a problem with it as long as Tn/Ux still work for now
> > (too many occurrences in the NetBSD man pages). But that seems to be
> > what the patch does,
> 
> Exactly.
> 
> I don't plan code changes to remove support for old stuff at all.  
> I want to be able to use mandoc to view original Version 7 AT&T UNIX
> and original 2BSD - 4.4BSD manuals out of the box (Version 6 and 1BSD
> won't work, though, they use an older macro set).
> 
> This is exclusively about which usage we want to encourage or
> discourage in modern manuals.

Sorry for being late to the party, but the deprecation is also perfectly
fine with me. Just as long as we don't break the old manuals.

Thanks!
Uli
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2014-07-30 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22 18:55 Ingo Schwarze
     [not found] ` <20140622210005.GA6196@harkle.home.gateway>
2014-06-23 19:55   ` Ingo Schwarze
2014-06-23 20:15     ` Thomas Klausner
2014-06-23 20:41       ` Ingo Schwarze
2014-07-30 11:56         ` Ulrich Spörlein [this message]

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=20140730115618.GA2142@acme.spoerlein.net \
    --to=uqs@spoerlein.net \
    --cc=discuss@mdocml.bsd.lv \
    --cc=jmc@kerhand.co.uk \
    --cc=wiz@NetBSD.org \
    /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).