Re: Call for help about html_css doc pages

[email protected] (Mark Wiesemann)
Newsgroups php.pear.doc
Message-ID <[email protected]>
Laurent Laville wrote:
> Curious, because html_quickform used syntax like
> 
> ....
> 
> &package.html.html-quickform.html-quickform.setmaxfilesize;
> &package.html.html-quickform.html-quickform.updateelementattr;
>  </sect2>
> 
>  <sect2 id="package.html.html-quickform.elements">
>   <title>Classes representing form elements</title>
>   <para>
> To be written
>   </para>
>   <sect3 id="package.html.html-quickform.elements.base">
>     <title>Base classes</title>
> &package.html.html-quickform.html-quickform-element;
> &package.html.html-quickform.html-quickform-element.html-quickform-element;
> &package.html.html-quickform.html-quickform-element.accept;
> &package.html.html-quickform.html-quickform-element.apiversion;
> 
> ...
> 
> &package.html.html-quickform.html-quickform-input.settype;
>   </sect3>
> 
> Where are difference from mine ? I'm not myself a DockBook expert, but 
> here I really don't understand what 's wrong !

The difference is that you have something like this:
  <sect2 id="package.html.html-css.intro">
   <title>Introduction</title>
   <sect3 id="package.html.html-css.intro.use">
    <title>Why use HTML_CSS ?</title>
[...]
   </sect3>
   <sect3 id="package.html.html-css.intro.use.features">
[...]
   </sect3>
   <sect3 id="package.html.html-css.intro.use.requires">
[...]
   </sect3>
   &package.html.html-css.faq;
   &package.html.html-css.whatsnew;
  </sect2>

You'll have <sect3> tags inside <sect2> tags here, and additionally 
references inside the <sect2> tag. If you wouldn't have the <sect3> tags 
in this block, there would be no error. If you move the two references 
inside another <sect3> tag, the file will also be valid. The mixture of 
<sect3> and the references seems to be the problem here.

Regards,
Mark

-- 
http://www.markwiesemann.eu
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.