Lines Matching full:docs
85 <filename>foobar/docs/</filename> and
326 implementation in <filename>docs/internals/</filename>. Much of it
394 <sect2 id="manual-writing-tools.docs" xreflabel="Documentation">
399 The file <filename>docs/README</filename> has more details on getting
409 <para>The docs go in
410 <computeroutput>foobar/docs/</computeroutput>, which you will
416 <filename>none/docs/nl-manual.xml</filename> to
417 <computeroutput>foobar/docs/</computeroutput>, and rename it to
418 <filename>foobar/docs/fb-manual.xml</filename>.</para>
427 <filename>docs/xml/xml_help.txt</filename>.</para>
432 <filename>docs/xml/manual.xml</filename>. Copy and edit an
438 <filename>docs/xml/valgrind-manpage.xml</filename>. Copy and
443 <para>Validate <filename>foobar/docs/fb-manual.xml</filename> using
444 the following command from within <filename>docs/</filename>:
466 <para>You can (re-)generate the HTML docs while you are writing
469 <filename>docs/html/</filename>. Use the following
470 command, within <filename>docs/</filename>:</para>
472 make html-docs
478 check all is well, from within <filename>docs/</filename>:
481 make print-docs
486 <computeroutput>docs/print/</computeroutput>.</para>
488 <para>Note that the toolchain is even more fragile for the print docs,
