DocBook tags: <literal> versus <firstterm>

From: Date: Thu, 25 Feb 2010 14:24:42 +0000
Subject: DocBook tags: <literal> versus <firstterm>
Groups: php.pear.doc 
Request: Send a blank email to pear-doc+get-11908@lists.php.net to get a copy of this message
working my way thru the PEAR manual, and i've already noticed a few examples of the introduction of a new term being tagged as <literal> rather than <firstterm>. proposed fix as output of "svn diff": Index: en/guide/users/concepts/package.xml =================================================================== --- en/guide/users/concepts/package.xml (revision 295501) +++ en/guide/users/concepts/package.xml (working copy) @@ -4,7 +4,7 @@ <para> The smallest unit that can be managed by Pyrus or the PEAR Installer is - a <literal>package</literal>. A package is a collection of files + a <firstterm>package</firstterm>. A package is a collection of files that are organized and defined by a meta-information file called <link linkend="guide.developers.package2.intro">package.xml</link>. </para> to be semantically proper, things like that really should be <firstterm>, should they not? is there any rendering problem with using <firstterm> in cases like that? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================

« previous php.pear.doc (#11908) next »