Date: Wed, 2 Jan 2002 23:54:36 -0200 From: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org> To: Nik Clayton <nik@FreeBSD.ORG> Cc: Peter Pentchev <roam@ringlet.net>, doc@FreeBSD.ORG Subject: Re: <filename> -> <port> (<protocol>?) Message-ID: <20020103015458.9740.qmail@exxodus.fedaykin.here> In-Reply-To: <20020102111934.B70243@clan.nothing-going-on.org>; from nik@FreeBSD.ORG on Wed, Jan 02, 2002 at 11:19:34AM %2B0000 References: <20011231100926.A3512@straylight.oblivion.bg> <20020102111934.B70243@clan.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 02, 2002 at 11:19:34AM +0000, Nik Clayton wrote: > On Mon, Dec 31, 2001 at 10:09:26AM +0200, Peter Pentchev wrote: > > Is there a reason to use <filename> instead of <port> when referring > > to a port? If not, how about the attached patch? >=20 > I'm still uneasy about <port>. Apart from the ambiguous name: >=20 > <para>The webserver listens on port <port>80</port>.</para> >=20 > <para>The printer is connected to <port>lpt0</port>.</para> >=20 > the rest of the world prefers the 'package' nomenclature. >=20 > I'd be more comfortable with a=20 >=20 > <filename class=3D"port"> >=20 > or >=20 > <filename class=3D"package"> >=20 > mechanism. Or perhaps >=20 > <package category=3D"archivers">unzip</package> >=20 > or even >=20 > <command package=3D"archivers/unzip">unzip</package> I tend to agree. The later mechanisms both are not ambiguous and help in parsing. Now that we mention it. What about a <protocol></protocol> tag?=20 Furthermore, shouldn't we use more <acronym></acronym>? TCP,IRC,FTP are all protocols and acronyms.... Regards, --=20 Mario S F Ferreira - DF - Brazil - "I guess this is a signature." Computer Science Undergraduate | FreeBSD Committer | CS Developer flames to beloved devnull@someotherworldbeloworabove.org feature, n: a documented bug | bug, n: an undocumented feature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020103015458.9740.qmail>