summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorDimitri van Heesch <dimitri@stack.nl>2002-02-24 18:57:25 (GMT)
committerDimitri van Heesch <dimitri@stack.nl>2002-02-24 18:57:25 (GMT)
commit837e4e86e7d2735cd7106efec6e4512db82d5e7a (patch)
tree81d72027898b1a75221b9ca82b04075277821a9f /doc
parentfa7e820834f7e7648a24accbbaa998092034c80f (diff)
downloadDoxygen-837e4e86e7d2735cd7106efec6e4512db82d5e7a.zip
Doxygen-837e4e86e7d2735cd7106efec6e4512db82d5e7a.tar.gz
Doxygen-837e4e86e7d2735cd7106efec6e4512db82d5e7a.tar.bz2
Release-1.2.14-20020224
Diffstat (limited to 'doc')
-rw-r--r--doc/external.doc5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/external.doc b/doc/external.doc
index f3a1e05..111703e 100644
--- a/doc/external.doc
+++ b/doc/external.doc
@@ -112,7 +112,10 @@ GENERATE_TAGFILE = ext2/ext2.tag
In some (hopefully exceptional) cases you may have the documentation
generated by doxygen, but not the sources nor a tag file. In this case you
can use the \ref doxytag_usage "doxytag" tool to extract a tag file from
-the generated HTML sources. This tool depends on the particular structure
+the generated HTML sources. Another case where you should use doxytag is
+if you want to create a tag file for the Qt documentation.
+
+The tool \c doxytag depends on the particular structure
of the generated output and on some special markers that are generated by
doxygen. Since this type of extraction is brittle and error prone I
suggest you to only use this approach if there is no alternative. The