From owner-freebsd-current@FreeBSD.ORG Tue May 19 12:37:39 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB4BA22E; Tue, 19 May 2015 12:37:39 +0000 (UTC) Received: from forward10l.mail.yandex.net (forward10l.mail.yandex.net [84.201.143.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 361CF1447; Tue, 19 May 2015 12:37:39 +0000 (UTC) Received: from smtp18.mail.yandex.net (smtp18.mail.yandex.net [95.108.252.18]) by forward10l.mail.yandex.net (Yandex) with ESMTP id 3E6B9BA145E; Tue, 19 May 2015 15:37:29 +0300 (MSK) Received: from smtp18.mail.yandex.net (localhost [127.0.0.1]) by smtp18.mail.yandex.net (Yandex) with ESMTP id 85D0B18A00EC; Tue, 19 May 2015 15:37:28 +0300 (MSK) Received: from unknown (unknown [89.204.139.107]) by smtp18.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 0GjKSN4Rdg-bRuOstr1; Tue, 19 May 2015 15:37:27 +0300 (using TLSv1.2 with cipher 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=1432039047; bh=ZDi5OsOGSmzPFCfzKhvLI0yIuR751uUkVNWIMYL70X0=; h=Date:From:To:Cc:Subject:Message-ID:References:In-Reply-To: User-Agent:MIME-Version:Content-Type; b=CzolMYR6AqSTfNDxNM57v/KQR4Q3OZVUTtrqkcMRT4qThcmwrYKuylD/8Em5uImLV juos2olA1Au9KesZBRtLE1Co+kK5QXMWtcOv2kZEnITpOUFiBxDEkNau53cJDjg2nT JnVfdDujzbOo5t/Rz6FohtlJE4/bOC2+cPvyB/1A= Authentication-Results: smtp18.mail.yandex.net; dkim=pass header.i=@yandex.com Date: Tue, 19 May 2015 14:37:22 +0200 From: Steffen Nurpmeso To: Baptiste Daroussin Cc: current@freebsd.org, "Julian H. Stacey" Subject: Re: [RFC] Replace gnu groff in base by heirloom doctools Message-ID: <20150519123722.KSZHLtTvPWw8%sdaoden@yandex.com> References: <20150514000211.GA9410@ivaldir.etoilebsd.net> <201505152342.t4FNgRgq076946@fire.js.berklix.net> <20150519112644.GB52236@ivaldir.etoilebsd.net> In-Reply-To: <20150519112644.GB52236@ivaldir.etoilebsd.net> User-Agent: s-nail v14.8.0-29-gc18370b-dirty MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Tue, 19 May 2015 12:39:55 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 12:37:39 -0000 Baptiste Daroussin wrote: |On Sat, May 16, 2015 at 01:42:26AM +0200, Julian H. Stacey wrote: |>> I think keeping a fully functionnal roff(7) toolchain part of the |>> base system is very good on a unix. |>> From what I could check I cannot find any regression when \ |>> migrating from gnu |>> groff to heirloom doctools, if there is a particular area \ |>> when you think extra |>> care is needed please share it. It seems you haven't checked at all. It seems to me that e.g. mdoc(7) of n-t-r seems to require quite a bit of work in order to be at all usable. |Heirloom in base is a win over groff because it has better \ |support for roff(7) |better font handling etc. The macros i use for myself don't work with n-t-r, too: once i truly looked (a few months ago) i found that i would have to rewrite all traps and other positioning in order to get that right. Despite that you seem to do what you want to do anyway, n-t-r is possibly a usable troff, if you go its way and deal with it you may be able to gain a bit nicer output _faster_ and without converting your beloved special fonts first, but in no way is n-t-r a _replacement_ for groff. Ciao, --steffen