> > How about instead we use, for example, the <acronym> tag (or
> > similar) so:
> >
> > <acronym>CVS</acronym>
> >
> > And in acronyms.xml we would list a definition for such terms.
> > I don't know if <acronym> is the appropriate tag but the
> > idea is what's important here. I prefer this method.
>
> Yes, this is nice.
I'm not familiar with XSLT and on my TODO is to figure out
how to implement this. I assume it'll exist as:
<acronym>CVS</acronym>
And when someone uses them they'll add the info into acronyms.xml
Also, make test will check for this. The terms will then link to
the appropriate acronyms entry in html builds.
All tips welcome or if someone implements this that's great too
but I do plan to research this at somepoint.
> > Avenger is translating english to chinese, he knows what CVS
> > means but wasn't sure about the context. I blame the
> > note, which shouldn't have been there. But of course your
> > point is valid.
>
> Apologies if I used an inappropriate platform to launch into one of my
> favourite mini-rants ("Use plain English wherever possible..." "Use plain
> English wherever possible..." "Use plain English wherever possible..."), but
> if it gets results...
:) This is a good rant and point well taken. The PHP manual
is pretty good about this as PHP attracts newbies by the
busload! Keep looking and we can discuss changes. I hope the
acronyms system works out.
> > Please list a few other terms, I'm curious. Sometimes these
> > techie terms are important and if people don't understand them
> > they shouldn't use the function! Of course I'm being a little
> > conservative on the idea and can only offer my opinions on a
> > case-by-case basis :) I look forward to your CVS access to the
> > phpdoc tree and hope spare time finds its way into your life and
> > into the php manual.
>
> Well, such a list is one of the things I need some spare time for ;) -- at
> the moment, it's just an impression I've formed from fighting my way through
> a selection of manual pages. I'll try to be a bit more rigorous about
> noting such usages as and when I come across them!
Cool, don't hesitate to mark them as user notes. User notes are
made for this sort of thing as we are to go through them and
update the manual pages accordingly. And even if the note gets
deleted it'll be archived so you'll never forget again! :) I
guess writing a list out works too. :)
Regards,
Philip Olson
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
