From owner-freebsd-doc@FreeBSD.ORG Sun Jun 1 05:10:16 2003 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 985A037B401 for ; Sun, 1 Jun 2003 05:10:12 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 131E743FB1 for ; Sun, 1 Jun 2003 05:10:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h51CABUp020671 for ; Sun, 1 Jun 2003 05:10:11 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h51CABH7020670; Sun, 1 Jun 2003 05:10:11 -0700 (PDT) Date: Sun, 1 Jun 2003 05:10:11 -0700 (PDT) Message-Id: <200306011210.h51CABH7020670@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Simon L. Nielsen" Subject: Re: docs/52514, Bluetooth Handbook Chapter X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Simon L. Nielsen" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 12:10:17 -0000 The following reply was made to PR docs/52514; it has been noted by GNATS. From: "Simon L. Nielsen" To: Pav Lucistnik Cc: bug-followup@FreeBSD.ORG Subject: Re: docs/52514, Bluetooth Handbook Chapter Date: Sun, 1 Jun 2003 14:05:51 +0200 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2003.06.01 04:50:18 -0700, Pav Lucistnik wrote: > > + You can choose any PIN you like. Note that some devices,= like > > + headsets, have a fixed PIN built in. Start hcsecd -= d. > > + The switch forces the daemon to stay in t= he > > + terminal and not fork to the background, so we can see what i= s happening. > > + Set the remote device to receive pairing and initiate the HCI= connection > > + to the remote device. The remote device should say that pair= ing was > > + accepted, and let you enter the PIN. Enter the same PIN as y= ou have in your > > + hcsecd.conf. Now your PC and remote dev= ice are paired. > > + Alternatively, you can initiate pairing on the remote device. > > + This will appear in the hcsecd output: > >=20 > > Use &man.hcsecd.8; ? > =20 > I already have this one paragraph before. What's the policy in > situations like this, when the name of a command repeats many times in a > short section of the text - should we use man entities everywhere, or > should we use it only in the first appearance and leave rest alone? There was recently added a note about this to section 4.2.5.4 of FDP Primer: When referring to the same command multiple times in close proximity it is preferred to use the &man.command.section; notation to markup the first reference and use to markup subsequent references. This makes the generated output, especially HTML, appear visually better. Of course the definition of "close proximity" is very open. Try compiling it and see how it looks. --=20 Simon L. Nielsen --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+2ewe8kocFXgPTRwRAiCWAKCAxyyEN2cUcmidtLBCuH56qZYATgCfQ46C ExayfzNiHFwa+dLHyh7WKuo= =swrd -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--