From owner-svn-src-head@freebsd.org Thu Mar 23 18:07:47 2017 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F4DBD1A346; Thu, 23 Mar 2017 18:07:47 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com [209.85.128.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2D6D1608; Thu, 23 Mar 2017 18:07:46 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-wr0-f178.google.com with SMTP id l37so153115739wrc.1; Thu, 23 Mar 2017 11:07:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=nneNp4oc9fnVGljXn4GK6u4oEUW4Ycgdx6vVaO0qUQM=; b=dG0Z/h4naUgHAGv+Aal6mAuiBmRydSgC4Ye8fnl2yDyX1NfbYxC6tHEOdgXpGpc27V Mvv0IoUx+Ok+urIgBrTEQO2bGu7tsDPMOADYEkVAJulZcH1kZvQC37tCclmgpYt7+k3M YkJ6ABJ3SoFZLLauaqLV4eZMDkyyq8O8gm8oZKRv/P+qFiu1QRbkNz548SiuS1SrpX/H OS4F7sQa0ENAnEFdSthnwePNJdgijLUD42k1h4hv3qrT10uKEnHfgXjh2ZqVX5BT1dmC dGaF9GmrLET+wWdX7rtwqARlEoh0jYkNxpsk/1++VLyDuSiK3edSKQwwN+ZfS74wmKjo 9ONw== X-Gm-Message-State: AFeK/H2ruBX9UYHmdaWcC3icMVbOO75L1iSt0QlVPzSoN9QG3XrTjS+aEUeVBEduGZuHEA== X-Received: by 10.223.139.5 with SMTP id n5mr3073843wra.200.1490282315688; Thu, 23 Mar 2017 08:18:35 -0700 (PDT) Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com. [74.125.82.46]) by smtp.gmail.com with ESMTPSA id w99sm6240602wrb.3.2017.03.23.08.18.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Mar 2017 08:18:35 -0700 (PDT) Received: by mail-wm0-f46.google.com with SMTP id n11so63982584wma.1; Thu, 23 Mar 2017 08:18:35 -0700 (PDT) X-Received: by 10.28.111.136 with SMTP id c8mr3367293wmi.128.1490282315401; Thu, 23 Mar 2017 08:18:35 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.80.169.4 with HTTP; Thu, 23 Mar 2017 08:18:34 -0700 (PDT) In-Reply-To: <20170323205948.N2588@besplex.bde.org> References: <201703230834.v2N8YVDA003255@repo.freebsd.org> <20170323205948.N2588@besplex.bde.org> From: Conrad Meyer Date: Thu, 23 Mar 2017 08:18:34 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: svn commit: r315850 - head/sys/boot/forth To: Bruce Evans Cc: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2017 18:07:47 -0000 On Thu, Mar 23, 2017 at 4:21 AM, Bruce Evans wrote: > On Thu, 23 Mar 2017, [UTF-8] Dag-Erling Sm=C3=B8rgrav wrote: > >> Log: >> The original author abused Nd (one-line description, used by makewhatis= ) >> for its side effect of producing an en-dash. This broke whatis with >> newer versions of mdocml. Use \(en instead. > > > Nd (or is it mumble-dash?) is broken for all man pages. Old man renders > the dash for Nd as 2 hyphens in ascii. New man renders it as 1 hyphen in > ascii. postscript output is even more broken. Old man renders the dash > for Nd as an especially wide one. New man still seems to render it as 1 > hyphen, and hyphens are especially narrow in postscript output for new > man (they are 1.5 to 2 times narrower than with old man, and that is with > a larger font for the smaller hyphens). Altogther, the dash for Nd is > about 4 times larger with old man after adjusting for the font size > (about 3 average characters wide instead of 3/4). > > Whatever the dash for Nd is, it shouldn't look like a hyphen. Yep. In this context an 'em' dash should be used instead of an 'en' dash. Theoretically, there also should not be spaces around the dashes. I'm not sure that's easy to do in manual pages, though. http://www.thepunctuationguide.com/em-dash.html http://www.thepunctuationguide.com/en-dash.html Best, Conrad