Re: cvs: peardoc /en/package/html/html-css api.xml
[email protected] (Mark Wiesemann)
| Newsgroups | php.pear.doc |
|---|---|
| Message-ID | <[email protected]> |
Laurent Laville wrote: > Mark Wiesemann a écrit : >> There are still errors: >> - the new <sect3> tag in html-css.xml needs a <title> tag >> (this removes the first three errors in the current log) >> - you'll need for every XML file a line like this: >> &package.html.html-css.XYZ; >> => otherwise the HTML files won't be build and the >> references in the <link> tags will be invalid > > Hope this time, all will be fixed. It's getting better. ;-) If you'll add the <title> tag to the <sect3> tag, only the following errors occur: $ make test /usr/bin/onsgmls -i lang-en -s ./phpdocxml.dcl manual.xml /usr/bin/onsgmls:./en/package/html/html-css/api.xml:67:21:X: reference to non-existent ID "package.html.html-css.html-css.setoutputgroupsfirst" /usr/bin/onsgmls:./en/package/html/html-css/api.xml:57:21:X: reference to non-existent ID "package.html.html-css.html-css.setsinglelineoutput" /usr/bin/onsgmls:./en/package/html/html-css/api.xml:12:27:X: reference to non-existent ID "package.html.html-css.html-css.html-css" /usr/bin/onsgmls:./en/package/html/html-css/api.xml:20:21:X: reference to non-existent ID "package.html.html-css.html-css.setxhtmlcompliance" /usr/bin/onsgmls:./en/package/html/html-css/api.xml:47:21:X: reference to non-existent ID "package.html.html-css.html-css.setcache" The references to these files seem to be missing in html-css.xml. > I understand now why few users write final doc under DocBook format : > - No way to test under all platform The current system works under at least Linux, MacOS and Windows (with Cygwin). This situation will improve once Hannes Magnusson's great new PhD system is ready for peardoc. > BTW, <title> is not mandatory on <sect3> tag , but id attribute is > Then I've fixed in that way That might be true, but there is still an error if the <title> tag is missing. > Even If HTML_CSS, seems to be the only effort I'll do to include my doc > into PEAR manual, The "problem" in your case is that you've started with more DocBook features. Those developers (like me) that did it only for peardoc had to live with the current limitations. Regards, Mark -- http://www.markwiesemann.eu