Re: DocBook tags: <literal> versus <firstterm>
| From: | Richard Quadling | Date: | Thu, 25 Feb 2010 15:11:36 +0000 |
| Subject: | Re: DocBook tags: <literal> versus <firstterm> | ||
| References: | 1 2 3 | Groups: | php.doc php.pear.doc |
| Request: | Send a blank email to pear-doc+get-11912@lists.php.net to get a copy of this message | ||
On 25 February 2010 14:52, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Thu, 25 Feb 2010, Richard Quadling wrote:
>
> ... snip ...
>
>> firstterm : "This element marks the first occurrence of a word or term
>> in a given context. " (TDG)
>>
>> That certainly sounds like the tag to be used.
>>
>> The example TDG has is ...
>>
>> <article
>> xmlns='http://docbook.org/ns/docbook'>
>> <title>Example firstterm</title>
>>
>> <para>In an <firstterm>Object Oriented</firstterm> programming language,
>> data and procedures (called <glossterm>methods</glossterm>) are
>> bound together.
>> </para>
>>
>> </article>
>>
>> So, the tag is good and it is supported as part of the Generic package
>> which both the PEAR and PHP PhD packages extend.
>
> i can submit a patch that adjusts a number of those tagged terms.
> can someone explain the proper "svn diff" incantation to post, along
> with the proper subject line, etc?
>
> i'm familiar with the concept of submitting patches, having
> submitted quite a number of them to the linux kernel mailing list. i
> just need to know the proper recipe for submitting them here.
> if there's a web page that explains that, all i need is the link.
> thanks.
>
> rday
> --
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page:
> http://crashcourse.ca
> Twitter:
> http://twitter.com/rpjday
> ========================================================================
>
svn diff should be enough for the diff.
You can read the commit messages by looking at any of the commits
online (http://svn.php.net/viewvc?view=revision&revision=295501 for
example).
If you are fixing a bug, then using fix# or bug# followed by the
actual number will allow the the svn hooks update the bug for you.
--
-----
Richard Quadling
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
EE4Free : http://www.experts-exchange.com/becomeAnExpert.jsp
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling