Is better to use reference which is most suitable for our templates.
DocBook evolves and it might be ok to stick with old edition if only
templates were stable, but templates change and along with new features
from new DocBook standard there are a lot of bugfixes. In other words if
we use new
ID: 34476
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Bogus
+Status: Open
Bug Type:Livedocs problem
PHP Version: Irrelevant
New Comment:
Sean, update your ulinks. =)
http://docbook.org/tdg/en/html/ulink.html
When the content of the ULink
Jean-Sebastien Goupil wrote:
When I was talking about bogus or fixed, it's because I've talked about
the doc problem or a livedoc problem in my first message... Yes it
wasn't the good bug type, but I can't put two bug types :) Normally,
when that happens, the bug used to be reclassified.
But
When I was talking about bogus or fixed, it's because I've talked about
the doc problem or a livedoc problem in my first message... Yes it
wasn't the good bug type, but I can't put two bug types :) Normally,
when that happens, the bug used to be reclassified.
Regards
Jean-Sébastien Goupil
||*()*|| Hi, Sean.
Sean, update your ulinks. =)
http://docbook.org/tdg/en/html/ulink.html
When the content of the ULink element is empty, i.e., for either of
the following cases: ulink url=.../ and ulink url=.../ulink,
the content of the url attribute should be rendered as the text of the
Is better to use reference which is most suitable for our templates.
DocBook evolves and it might be ok to stick with old edition if only
templates were stable, but templates change and along with new features
from new DocBook standard there are a lot of bugfixes. In other words if
we use new
