Date: Tue, 13 Jul 2004 17:52:32 +0100 From: Ceri Davies <ceri@FreeBSD.org> To: Warren Block <wblock@wonkity.com> Cc: doc@freebsd.org Subject: Re: Handbook Acronyms Message-ID: <20040713165232.GT29928@submonkey.net> In-Reply-To: <20040712171533.R43767@wonkity.com> References: <20040712171533.R43767@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--ggHp9WSrPOeNxb0b Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 12, 2004 at 05:31:25PM -0600, Warren Block wrote: > In most books, the first use of an acronym or term is defined. With the= =20 > Handbook, that is probably not very helpful, since most users will not=20 > read it straight through and may miss the definition. >=20 > A glossary would help, particularly for HTML, where the definition is=20 > just a link away. This fails on paper versions of the Handbook, though. >=20 > Ideally, the first use of a glossary term in a chapter would have a=20 > short definition: >=20 > With NFS (Network File System), files may be... >=20 > In the HTML version, the entire "NFS (Network File System)" would be a=20 > link to the glossary. Later references and links would just be "NFS". >=20 > If every acronym is defined in the glossary, is it possible to generate= =20 > the link and definition the first time an acronym is used in a chapter? Yes, and that's the plan at the moment. Ceri --=20 It is not tinfoil, it is my new skin. I am a robot. --ggHp9WSrPOeNxb0b Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA9BNPocfcwTS3JF8RAt/sAJ9aa5ggvYCZBE4kvb8eZ4kaKOIXbwCghCQI 2Xaa69lzrGCYxq4CE+Mm2cQ= =b1mS -----END PGP SIGNATURE----- --ggHp9WSrPOeNxb0b--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040713165232.GT29928>