summaryrefslogtreecommitdiffstats
path: root/doc/doxytag_usage.doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/doxytag_usage.doc')
-rw-r--r--doc/doxytag_usage.doc65
1 files changed, 22 insertions, 43 deletions
diff --git a/doc/doxytag_usage.doc b/doc/doxytag_usage.doc
index 6d7a5e1..b4472d8 100644
--- a/doc/doxytag_usage.doc
+++ b/doc/doxytag_usage.doc
@@ -17,38 +17,26 @@
/*! \page doxytag_usage Doxytag usage
Doxytag is a small command line based utility.
-It has two functions:
-<ul>
-<li>
- Doxytag can generate <em>tag files</em>.
- These tag files can be used with <a href="doxygen_usage.html">doxygen</a>
- to generate references to external documentation
- (i.e. documentation not contained in the input files that are used by
- doxygen).
- A tag file contains information about files, classes and members
- documented in external documentation. Doxytag extracts this information
- directly from the HTML files. This has the advantage that you do not need
- to have the sources from which the documentation was extracted.
- If you \e do have the sources it is better to let \c doxygen generate the
- tag file by putting the name of the tag file after
- \ref cfg_generate_tagfile "GENERATE_TAGFILE" in
- the configuration file.
-<li>
- Doxytag can generate a <em>search index</em> for the documentation
- generated with doxygen or for the Qt documentation. See the documentation of
- <a href="doxysearch_usage.html">doxysearch</a> for more information on how
- to do this.
- A search index contains information about all the words (and all substrings
- thereof) that are contained in the documentation.
- For each string the index contains the set of documentation blocks that
- contain the string and the frequency of occurrence. This way
- <code>doxysearch</code> can search for words very quickly
- (most queries are processed within a few milliseconds on my system.)
-</ul>
-In both cases the input of doxytag consists of a set of HTML files.
+It can generate <em>tag files</em>.
+These tag files can be used with <a href="doxygen_usage.html">doxygen</a>
+to generate references to external documentation
+(i.e. documentation not contained in the input files that are used by
+doxygen).
+
+A tag file contains information about files, classes and members
+documented in external documentation. Doxytag extracts this information
+directly from the HTML files. This has the advantage that you do not need
+to have the sources from which the documentation was extracted.
+
+If you \e do have the sources it is better to let \c doxygen generate the
+tag file by putting the name of the tag file after
+\ref cfg_generate_tagfile "GENERATE_TAGFILE" in
+the configuration file.
+
+The input of doxytag consists of a set of HTML files.
\par Important:
- If you use tag files or use a search engine, the links that
+ If you use tag files, the links that
are generated by doxygen will contain \e dummy links. You have to run
the \c installdox script to change these dummy links into real links.
See \ref installdox_usage for more information.
@@ -58,10 +46,10 @@ In both cases the input of doxytag consists of a set of HTML files.
only \c installdox has to be run.
\par Note:
-Because the HTML files are expected to have a certain
-structure, only HTML files generated with doxygen or with Qt's class
-browser generator can be used. Doxytag only <em>reads</em> the HTML files,
-they are not altered in any way.
+ Because the HTML files are expected to have a certain
+ structure, only HTML files generated with doxygen or with Qt's class
+ browser generator can be used. Doxytag only <em>reads</em> the HTML files,
+ they are not altered in any way.
Doxytag expects a list of all HTML files that form the documentation
or a directory that contains all HTML files. If neither is present doxytag
@@ -106,13 +94,4 @@ doxytag -t example.tag example/html
doxytag -t qt.tag $QTDIR/doc/html
\endverbatim
-A typical example to use doxytag to generate a search index is:
-\verbatim
-doxytag -s search.idx
-\endverbatim
-
-\par Note:
-In the current version of doxygen, the search index must be
-called \c search.idx.
-
*/