From owner-freebsd-doc  Thu Jul 19 12: 9:45 2001
Delivered-To: freebsd-doc@freebsd.org
Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88])
	by hub.freebsd.org (Postfix) with ESMTP id CDC6737B406
	for <doc@FreeBSD.ORG>; Thu, 19 Jul 2001 12:09:42 -0700 (PDT)
	(envelope-from murray@meow.osd.bsdi.com)
Received: (from murray@localhost)
	by meow.osd.bsdi.com (8.11.4/8.11.2) id f6JJ9PQ32604;
	Thu, 19 Jul 2001 12:09:25 -0700 (PDT)
	(envelope-from murray)
Date: Thu, 19 Jul 2001 12:09:25 -0700
From: Murray Stokely <murray.stokely@windriver.com>
To: Dima Dorfman <dima@unixfreak.org>
Cc: doc@FreeBSD.ORG
Subject: Re: Markup for ports
Message-ID: <20010719120925.G27537@meow.osd.bsdi.com>
References: <20010719145728.177563E2F@bazooka.unixfreak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010719145728.177563E2F@bazooka.unixfreak.org>; from dima@unixfreak.org on Thu, Jul 19, 2001 at 07:57:28AM -0700
X-GPG-Key-ID: 1024D/0E451F7D
X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B  3CB5 B4D7 10A2 0E45 1F7D
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-doc.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc>
X-Loop: FreeBSD.org

  I support this in general, but more thought needs to be placed on
how this will look without the benefit of a hyperlink.  Another
example of dependence on hyperlinks is the use of <xrefs> being
printed out as file:/// in the printed version of the Handbook which
doesn't look very good.  It seems that many sentences are constructed
in the handbook such that they depend on the hyperlink for proper
context.  I don't want anything to encourage that practice.

  "Other interfaces, like databases/tkgnats should also work nicely."

  This is pretty informal.  Will the markup given to your new <port>
tag be sufficient to clue in new users that we are talking about a
FreeBSD port?  Or is more verbiage necessary, such as :

  "Other interfaces, like the port databases/tkgnats should also work
nicely."

  I'm not quite sure, I just don't like the over dependence on
hyperlinks that is infecting the Handbook. ;)

	- Murray

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message