From 88030e6b0efd9ac75cd61eedd75f5a38bf1713c7 Mon Sep 17 00:00:00 2001
From: dimitri
Date: Mon, 4 Jun 2001 14:15:23 +0000
Subject: Release-1.2.8
---
INSTALL | 4 +-
README | 4 +-
VERSION | 2 +-
doc/Makefile.in | 8 +-
doc/Makefile.win_make.in | 10 +-
doc/Makefile.win_nmake.in | 2 +-
doc/commands.doc | 70 +--
doc/config.doc | 83 +--
doc/diagrams.doc | 6 +-
doc/docblocks.doc | 2 +-
doc/doxygen_usage.doc | 4 +-
doc/doxysearch_usage.doc | 8 +-
doc/external.doc | 4 +-
doc/faq.doc | 8 +-
doc/features.doc | 12 +-
doc/formulas.doc | 16 +-
doc/history.doc | 4 +-
doc/htmlcmds.doc | 37 +-
doc/index.doc | 20 +-
doc/install.doc | 31 +-
doc/maintainers.txt | 4 +
doc/output.doc | 4 +-
doc/starting.doc | 10 +-
examples/jdstyle.cpp | 2 +-
examples/qtstyle.cpp | 2 +-
packages/rpm/doxygen.spec | 2 +-
qtools/qcstring.cpp | 42 +-
src/config.h | 115 ++--
src/config.l | 120 +++-
src/defargs.l | 1 +
src/doc.l | 40 +-
src/dot.cpp | 12 +-
src/doxygen.cpp | 80 ++-
src/ftvhelp.cpp | 7 +
src/groupdef.cpp | 2 +-
src/htmlgen.cpp | 14 +-
src/htmlgen.h | 3 +-
src/htmlhelp.cpp | 10 +
src/language.cpp | 5 +
src/latexgen.cpp | 27 +-
src/latexgen.h | 2 +-
src/mangen.cpp | 21 +-
src/mangen.h | 2 +-
src/memberdef.cpp | 10 +-
src/outputgen.h | 4 +-
src/outputlist.h | 5 +-
src/rtfgen.cpp | 14 +-
src/rtfgen.h | 2 +-
src/scanner.l | 1 +
src/translator_cz.h | 38 +-
src/translator_de.h | 30 +-
src/translator_en.h | 8 +-
src/translator_es.h | 421 ++++++++++++--
src/translator_hr.h | 200 +++++--
src/translator_ru.h | 63 ++-
src/translator_sk.h | 1334 +++++++++++++++++++++++++++++++++++++++++++++
src/util.cpp | 89 ++-
src/util.h | 5 +-
58 files changed, 2573 insertions(+), 513 deletions(-)
create mode 100644 src/translator_sk.h
diff --git a/INSTALL b/INSTALL
index ee6e255..7cde105 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,6 +1,6 @@
-DOXYGEN Version 1.2.7-20010524
+DOXYGEN Version 1.2.8
Please read the installation section of the manual for instructions.
--------
-Dimitri van Heesch (24 May 2001)
+Dimitri van Heesch (04 June 2001)
diff --git a/README b/README
index bec5b17..feb2212 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-DOXYGEN Version 1.2.7_20010524
+DOXYGEN Version 1.2.8
Please read INSTALL for compilation instructions.
@@ -7,4 +7,4 @@ The latest version of doxygen can be obtained at
Enjoy,
-Dimitri van Heesch (24 May 2001)
+Dimitri van Heesch (04 June 2001)
diff --git a/VERSION b/VERSION
index 58be32e..db6fb4a 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-1.2.7-20010524
+1.2.8
diff --git a/doc/Makefile.in b/doc/Makefile.in
index 90c7d94..38675ed 100644
--- a/doc/Makefile.in
+++ b/doc/Makefile.in
@@ -12,7 +12,7 @@
# Documents produced by Doxygen are derivative works derived from the
# input used in their production; they are not affected by this license.
-all: FORCE
+all: language FORCE
DOXYGEN_DOCDIR=$(DOXYDOCS); \
export DOXYGEN_DOCDIR; \
VERSION=$(VERSION) ; \
@@ -28,9 +28,11 @@ all: FORCE
clean:
rm -rf ../html ../latex language.doc
-language: language.doc language.tpl translator.pl
+language: language.doc
-language.doc: language.tpl FORCE
+translators: $(wildcard ../src/translator_*.h)
+
+language.doc: translators maintainers.txt language.tpl translator.pl
$(PERL) translator.pl
FORCE:
diff --git a/doc/Makefile.win_make.in b/doc/Makefile.win_make.in
index b1a2009..3b7c3c7 100644
--- a/doc/Makefile.win_make.in
+++ b/doc/Makefile.win_make.in
@@ -12,7 +12,7 @@
# Documents produced by Doxygen are derivative works derived from the
# input used in their production; they are not affected by this license.
-all:
+all: language FORCE
@xcopy /s /q /i ..\examples ..\html\examples
set DOXYGEN_DOCDIR=. & \
set VERSION=$(VERSION) & \
@@ -26,5 +26,13 @@ all:
clean:
del /s /q ..\html ..\latex
+ del translator_report.txt *.bak
+
+language: language.doc
+
+translators: ..\src\translator_*.h
+
+language.doc: translators maintainers.txt language.tpl translator.pl
+ $(PERL) translator.pl
FORCE:
diff --git a/doc/Makefile.win_nmake.in b/doc/Makefile.win_nmake.in
index 92829a1..dd53b22 100644
--- a/doc/Makefile.win_nmake.in
+++ b/doc/Makefile.win_nmake.in
@@ -12,7 +12,7 @@
# Documents produced by Doxygen are derivative works derived from the
# input used in their production; they are not affected by this license.
-all: FORCE
+all: language FORCE
@xcopy /s /q /i ..\examples ..\html\examples
set DOXYGEN_DOCDIR=.
set VERSION=$(VERSION)
diff --git a/doc/commands.doc b/doc/commands.doc
index b0b9bc2..087fad0 100644
--- a/doc/commands.doc
+++ b/doc/commands.doc
@@ -145,7 +145,7 @@ documentation:
\endlatexonly
The following subsections provide a list of all commands that are recognized by
-Doxygen. Unrecognized commands are treated as normal text.
+doxygen. Unrecognized commands are treated as normal text.
\htmlonly
--- \endhtmlonly
Structural indicators
@@ -204,7 +204,7 @@ Doxygen. Unrecognized commands are treated as normal text.
\verbinclude class.h
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -218,7 +218,7 @@ Doxygen. Unrecognized commands are treated as normal text.
\verbinclude define.h
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -231,7 +231,7 @@ Doxygen. Unrecognized commands are treated as normal text.
categories. You can also use groups as members of other groups,
thus building a hierarchy of groups.
- The \ argument should be a single word identifier.
+ The \ argument should be a single-word identifier.
\sa page \ref grouping "Grouping", sections \ref cmdingroup "\\ingroup", \ref cmdaddtogroup "\\addtogroup",
\ref cmdweakgroup "\\weakgroup".
@@ -256,7 +256,7 @@ Doxygen. Unrecognized commands are treated as normal text.
\verbinclude enum.h
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -271,7 +271,7 @@ Doxygen. Unrecognized commands are treated as normal text.
If any are found, the names are cross-referenced with the documentation.
Source files or directories can be specified using the
\ref cfg_example_path "EXAMPLE_PATH"
- tag of Doxygen's configuration file.
+ tag of doxygen's configuration file.
If \ itself is not unique for the set of example files specified
by the
@@ -287,7 +287,7 @@ Doxygen. Unrecognized commands are treated as normal text.
\verbinclude example_test.cpp
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
\sa section \ref cmdinclude "\\include".
@@ -310,7 +310,7 @@ Doxygen. Unrecognized commands are treated as normal text.
\verbinclude file.h
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -331,7 +331,7 @@ Doxygen. Unrecognized commands are treated as normal text.
\verbinclude func.h
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
\sa section \ref cmdvar "\\var" and \ref cmdtypedef "\\typedef".
@@ -343,7 +343,7 @@ Doxygen. Unrecognized commands are treated as normal text.
By default the value of a define and the initializer of a variable
are displayed unless they are longer than 30 lines. By putting
this command in a comment block of a define or variable, the
- initializer always hidden.
+ initializer is always hidden.
\sa section \ref cmdshowinitializer "\\showinitializer".
@@ -461,7 +461,7 @@ Public/Protected/Private/... section.
\verbinclude examples/overload.cpp
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -471,14 +471,14 @@ Public/Protected/Private/... section.
Indicates that a comment block contains a piece of documentation that is
not directly related to one specific class, file or member.
The HTML generator creates a page containing the documentation. The
- \htmlonly LaTeX\endhtmlonly\latexonly\LaTeX\ \endlatexonly generator
+ \f$\mbox{\LaTeX}\f$ generator
starts a new section in the chapter `Page documentation'.
\par Example:
\verbinclude page.doc
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
\par Note:
@@ -509,7 +509,7 @@ Public/Protected/Private/... section.
\verbinclude relates.cpp
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -537,7 +537,7 @@ Public/Protected/Private/... section.
\subsection cmdtypedef \typedef (typedef declaration)
\addindex \typedef
- Indicates that a comment block contains documentation for a typedef,
+ Indicates that a comment block contains documentation for a
typedef (either global or as a member of a class).
This command is equivalent to \\var and \\fn.
@@ -557,7 +557,7 @@ Public/Protected/Private/... section.
\subsection cmdvar \var (variable declaration)
\addindex \var
- Indicates that a comment block contains documentation for a variable,
+ Indicates that a comment block contains documentation for a variable or
enum value (either global or as a member of a class).
This command is equivalent to \\typedef and \\fn.
@@ -606,7 +606,7 @@ Public/Protected/Private/... section.
\verbinclude author.cpp
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -771,7 +771,7 @@ Public/Protected/Private/... section.
\verbinclude par.cpp
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
@@ -821,7 +821,7 @@ Public/Protected/Private/... section.
\subsection cmdremarks \remarks { remark text }
\addindex \remarks
- Starts a paragraph where one or more marks may be entered.
+ Starts a paragraph where one or more remarks may be entered.
The paragraph will be indented.
The text of the paragraph has no special internal structure. All visual
enhancement commands may be used inside the paragraph.
@@ -847,7 +847,7 @@ Public/Protected/Private/... section.
\subsection cmdretval \retval { description }
\addindex \retval
- Starts a return value for a function with name
+ Starts a return value description for a function with name
\. Followed by a description of the return value.
The text of the paragraph that forms the description has no special
internal structure. All visual enhancement commands may be used inside the
@@ -863,7 +863,7 @@ Public/Protected/Private/... section.
\addindex \sa
Starts a paragraph where one or more cross-references to classes,
functions, methods, variables, files or URL may be specified.
- Two names joines by either :: or \#
+ Two names joined by either :: or \#
are understood as referring to a class and one of its members.
One of several overloaded methods or constructors
may be selected by including a parenthesized list of argument types after
@@ -975,7 +975,7 @@ Public/Protected/Private/... section.
\subsection cmdlink \link
\addindex \link
- The links that are automatically generated by Doxygen always have the
+ The links that are automatically generated by doxygen always have the
name of the object they point to as link-text.
The \\link command can be used to create a link to an object (a file,
@@ -1048,7 +1048,7 @@ Public/Protected/Private/... section.
add documentation between the pieces.
Source files or directories can be specified using the
\ref cfg_example_path "EXAMPLE_PATH"
- tag of Doxygen's configuration file.
+ tag of doxygen's configuration file.
The class and member declarations and definitions inside the code fragment
are `remembered' during the parsing of the comment block that contained
@@ -1065,7 +1065,7 @@ Public/Protected/Private/... section.
\verbinclude example_test.cpp
\htmlonly
Click here
- for the corresponding HTML documentation that is generated by Doxygen.
+ for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
\sa sections \ref cmdline "\\line", \ref cmdskip "\\skip",
@@ -1079,7 +1079,7 @@ Public/Protected/Private/... section.
The command takes the name of an include file as an argument.
Source files or directories can be specified using the
\ref cfg_example_path "EXAMPLE_PATH"
- tag of Doxygen's configuration file.
+ tag of doxygen's configuration file.
If \ itself is not unique for the set of example files specified
by the
@@ -1178,7 +1178,7 @@ Public/Protected/Private/... section.
placing \\verbatim and \\endverbatim commands around it.
Files or directories that doxygen should look for can be specified using the
- \ref cfg_example_path "EXAMPLE_PATH" tag of Doxygen's configuration file.
+ \ref cfg_example_path "EXAMPLE_PATH" tag of doxygen's configuration file.
\subsection cmdhtmlinclude \htmlinclude
@@ -1189,7 +1189,7 @@ Public/Protected/Private/... section.
placing \\htmlonly and \\endhtmlonly commands around it.
Files or directories that doxygen should look for can be specified using the
- \ref cfg_example_path "EXAMPLE_PATH" tag of Doxygen's configuration file.
+ \ref cfg_example_path "EXAMPLE_PATH" tag of doxygen's configuration file.
\htmlonly
--- \endhtmlonly
@@ -1378,7 +1378,7 @@ Public/Protected/Private/... section.
endhtmlonly command.
This command can be used to include HTML code that is too complex
- for Doxygen (i.e. applets, java-scripts, and HTML tags that
+ for doxygen (i.e. applets, java-scripts, and HTML tags that
require attributes). You can use the \\latexonly and \\endlatexonly
pair to provide a proper \f$\mbox{\LaTeX}\f$ alternative.
@@ -1401,12 +1401,12 @@ Public/Protected/Private/... section.
following values are supported: \c html and \c latex.
The second argument specifies the file name of the image.
- Doxygen will look for files in the paths (or files) that you specified
+ doxygen will look for files in the paths (or files) that you specified
after the \ref cfg_image_path "IMAGE_PATH" tag.
If the image is found it will be copied to the correct output directory.
If the image name contains spaces you'll have to put quotes (") around it.
You can also specify an absolute URL instead of a file name, but then
- doxygen does not copy the image or check its existance.
+ doxygen does not copy the image nor check its existance.
The third argument is optional and can be used to specify the caption
that is displayed below the image. This argument has to be specified
@@ -1439,9 +1439,9 @@ Public/Protected/Private/... section.
\warning The image format for HTML is limited to what your
browser supports. For \f$\mbox{\LaTeX}\f$ the image format
- must be an encapsulated postscipt (eps).
+ must be Encapsulated PostScipt (eps).
- Doxygen does not check if the image is in the correct format.
+ doxygen does not check if the image is in the correct format.
So \e you have to make sure this is the case!
@@ -1453,7 +1453,7 @@ Public/Protected/Private/... section.
endlatexonly command.
This command can be used to include \f$\mbox{\LaTeX}\f$ code that is too
- complex for Doxygen (i.e. images, formulas, special characters). You can
+ complex for doxygen (i.e. images, formulas, special characters). You can
use the \\htmlonly and \\endhtmlonly pair to provide a proper HTML
alternative.
@@ -1531,7 +1531,7 @@ Public/Protected/Private/... section.
\addindex \\
This command writes a backslash character (\\) to the HTML and
\f$\mbox{\LaTeX}\f$ output. The backslash has to be escaped in some
- cases because Doxygen uses it to detect commands.
+ cases because doxygen uses it to detect commands.
\subsection cmdat \@
@@ -1539,7 +1539,7 @@ Public/Protected/Private/... section.
\addindex \@
This command writes an at-sign (@) to the HTML and
\f$\mbox{\LaTeX}\f$ output. The at-sign has to be escaped in some cases
- because Doxygen uses it to detect JavaDoc commands.
+ because doxygen uses it to detect JavaDoc commands.
\subsection cmdamp \&
diff --git a/doc/config.doc b/doc/config.doc
index f5d1f1e..13d3991 100644
--- a/doc/config.doc
+++ b/doc/config.doc
@@ -14,7 +14,7 @@
* input used in their production; they are not affected by this license.
*
*/
-/*! \page config
+/*! \page config Configuration
\section config Configuration
@@ -213,7 +213,7 @@ followed by the descriptions of the tags grouped by category.
\c OUTPUT_DIRECTORY
\addindex OUTPUT_DIRECTORY
The \c OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
- path into which the generated HTML and Latex documentation will be written.
+ path into which the generated documentation will be written.
If a relative path is entered, it will be relative to the location
where doxygen was started. If left blank the current directory will be used.
@@ -254,7 +254,7 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_hide_undoc_members
\c HIDE_UNDOC_MEMBERS
\addindex HIDE_UNDOC_MEMBERS
- If the \c HIDE_UNDOC_MEMBERS tag is set to \c YES, Doxygen will hide all
+ If the \c HIDE_UNDOC_MEMBERS tag is set to \c YES, doxygen will hide all
undocumented members inside documented classes or files.
If set to \c NO (the default) these members will be included in the
various overviews, but no documentation section is generated.
@@ -263,7 +263,7 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_hide_undoc_classes
\c HIDE_UNDOC_CLASSES
\addindex HIDE_UNDOC_CLASSES
- If the \c HIDE_UNDOC_CLASSESS tag is set to \c YES, Doxygen will hide all
+ If the \c HIDE_UNDOC_CLASSESS tag is set to \c YES, doxygen will hide all
undocumented classes.
If set to \c NO (the default) these classes will be included in the
various overviews.
@@ -272,7 +272,7 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_brief_member_desc
\c BRIEF_MEMBER_DESC
\addindex BRIEF_MEMBER_DESC
- If the \c BRIEF_MEMBER_DESC tag is set to \c YES (the default) Doxygen will
+ If the \c BRIEF_MEMBER_DESC tag is set to \c YES (the default) doxygen will
include brief member descriptions after the members that are listed in
the file and class documentation (similar to JavaDoc).
Set to NO to disable this.
@@ -280,7 +280,7 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_repeat_brief
\c REPEAT_BRIEF
\addindex REPEAT_BRIEF
- If the \c REPEAT_BRIEF tag is set to \c YES (the default) Doxygen will
+ If the \c REPEAT_BRIEF tag is set to \c YES (the default) doxygen will
prepend the brief description of a member or function before the detailed
description
@@ -292,13 +292,13 @@ followed by the descriptions of the tags grouped by category.
\c ALWAYS_DETAILED_SEC
\addindex ALWAYS_DETAILED_SEC
If the \c ALWAYS_DETAILED_SEC and \c REPEAT_BRIEF tags are both set to \c YES then
- Doxygen will generate a detailed section even if there is only a brief
+ doxygen will generate a detailed section even if there is only a brief
description.
\anchor cfg_full_path_names
\c FULL_PATH_NAMES
\addindex FULL_PATH_NAMES
- If the \c FULL_PATH_NAMES tag is set to \c YES Doxygen will prepend the full
+ If the \c FULL_PATH_NAMES tag is set to \c YES doxygen will prepend the full
path before files name in the file list and in the header files. If set
to NO the shortest path that makes the file name unique will be used
@@ -321,8 +321,8 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_class_diagrams
\c CLASS_DIAGRAMS
\addindex CLASS_DIAGRAMS
- If the \c CLASS_DIAGRAMS tag is set to \c YES (the default) Doxygen will
- generate a class diagram (in Html and \f$\mbox{\LaTeX}\f$) for classes with base or
+ If the \c CLASS_DIAGRAMS tag is set to \c YES (the default) doxygen will
+ generate a class diagram (in HTML and \f$\mbox{\LaTeX}\f$) for classes with base or
super classes. Setting the tag to \c NO turns the diagrams off.
\anchor cfg_source_browser
@@ -347,7 +347,7 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_case_sense_names
\c CASE_SENSE_NAMES
\addindex CASE_SENSE_NAMES
- If the \c CASE_SENSE_NAMES tag is set to \c NO (the default) then Doxygen
+ If the \c CASE_SENSE_NAMES tag is set to \c NO (the default) then doxygen
will only generate file names in lower case letters. If set to
\c YES upper case letters are also allowed. This is useful if you have
classes or files whose names only differ in case and if your file system
@@ -363,14 +363,14 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_hide_scope_names
\c HIDE_SCOPE_NAMES
\addindex HIDE_SCOPE_NAMES
- If the \c HIDE_SCOPE_NAMES tag is set to \c NO (the default) then Doxygen
+ If the \c HIDE_SCOPE_NAMES tag is set to \c NO (the default) then doxygen
will show members with their full class and namespace scopes in the
documentation. If set to \c YES the scope will be hidden.
\anchor cfg_verbatim_headers
\c VERBATIM_HEADERS
\addindex VERBATIM_HEADERS
- If the \c VERBATIM_HEADERS tag is set the \c YES (the default) then Doxygen
+ If the \c VERBATIM_HEADERS tag is set the \c YES (the default) then doxygen
will generate a verbatim copy of the header file for each class for
which an include is specified. Set to NO to disable this.
\sa Section \ref cmdclass "\\class".
@@ -378,14 +378,14 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_show_include_files
\c SHOW_INCLUDE_FILES
\addindex SHOW_INCLUDE_FILES
- If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
+ If the SHOW_INCLUDE_FILES tag is set to YES (the default) then doxygen
will put list of the files that are included by a file in the documentation
of that file.
\anchor cfg_javadoc_autobrief
\c JAVADOC_AUTOBRIEF
\addindex JAVADOC_AUTOBRIEF
- If the \c JAVADOC_AUTOBRIEF is set to \c YES then Doxygen
+ If the \c JAVADOC_AUTOBRIEF is set to \c YES then doxygen
will interpret the first line (until the first dot) of a JavaDoc-style
comment as the brief description. If set to NO (the default), the
Javadoc-style will behave just like the Qt-style comments.
@@ -665,7 +665,7 @@ followed by the descriptions of the tags grouped by category.
\c GENERATE_HTML
\addindex GENERATE_HTML
- If the \c GENERATE_HTML tag is set to \c YES (the default) Doxygen will
+ If the \c GENERATE_HTML tag is set to \c YES (the default) doxygen will
generate HTML output
\anchor cfg_html_output
@@ -760,16 +760,16 @@ followed by the descriptions of the tags grouped by category.
\c index.hhp, \c index.hhc, and \c index.hhk. The \c index.hhp is a
project file that can be read by
- Microsoft HTML help workshop
+ Microsoft HTML Help Workshop
\latexonly
(see http://msdn.microsoft.com/library/tools/htmlhelp/wkshp/download\_main.htm)
\endlatexonly
on Windows.
- The HTML workshop contains a compiler that can convert all HTML output
+ The HTML Help Workshop contains a compiler that can convert all HTML output
generated by doxygen into a single compressed HTML file (.chm). Compressed
HTML files are now used as the Windows 98 help format, and will replace
- the old windows help format (.hlp) on all Windows platforms in the future.
+ the old Windows help format (.hlp) on all Windows platforms in the future.
Compressed HTML files also contain an index, a table of contents,
and you can search for words in the documentation
(which basically renders \c doxysearch obsolete on Windows).
@@ -792,8 +792,8 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_toc_expand
\c TOC_EXPAND
\addindex TOC_EXPAND
- The \c TOC_EXPAND flag can be set YES to add extra items for
- group members to the table of contents of the Html help documentation
+ The \c TOC_EXPAND flag can be set to YES to add extra items for
+ group members to the table of contents of the HTML help documentation
and to the tree view.
\anchor cfg_disable_index
@@ -834,8 +834,8 @@ followed by the descriptions of the tags grouped by category.
\c GENERATE_LATEX
\addindex GENERATE_LATEX
- If the \c GENERATE_LATEX tag is set to \c YES (the default) Doxygen will
- generate Latex output.
+ If the \c GENERATE_LATEX tag is set to \c YES (the default) doxygen will
+ generate \f$\mbox{\LaTeX}\f$ output.
\anchor cfg_latex_output
\c LATEX_OUTPUT
@@ -848,7 +848,7 @@ followed by the descriptions of the tags grouped by category.
\anchor cfg_compact_latex
\c COMPACT_LATEX
\addindex COMPACT_LATEX
- If the \c COMPACT_LATEX tag is set to \c YES Doxygen generates more compact
+ If the \c COMPACT_LATEX tag is set to \c YES doxygen generates more compact
\f$\mbox{\LaTeX}\f$ documents. This may be useful for small projects and may help to
save some trees in general.
@@ -881,8 +881,8 @@ EXTRA_PACKAGES = times
\c LATEX_HEADER
\addindex LATEX_HEADER
The \c LATEX_HEADER tag can be used to specify a personal \f$\mbox{\LaTeX}\f$
- header for the generated latex document. The header should contain everything
- until the first chapter.
+ header for the generated \f$\mbox{\LaTeX}\f$ document.
+ The header should contain everything until the first chapter.
If it is left blank doxygen will generate a
standard header. See section \ref doxygen_usage for information on how to
@@ -904,10 +904,11 @@ EXTRA_PACKAGES = times
\c PDF_HYPERLINKS
\addindex PDF_HYPERLINKS
- If the \c PDF_HYPERLINKS tag is set to \c YES, the LaTeX that is generated
- is prepared for conversion to pdf (using ps2pdf). The pdf file will
+ If the \c PDF_HYPERLINKS tag is set to \c YES, the \f$\mbox{\LaTeX}\f$ that
+ is generated is prepared for conversion to PDF (using ps2pdf).
+ The PDF file will
contain links (just like the HTML output) instead of page references
- This makes the output suitable for online browsing using a pdf viewer.
+ This makes the output suitable for online browsing using a PDF viewer.
\anchor cfg_latex_batchmode
\c LATEX_BATCHMODE
@@ -926,7 +927,7 @@ EXTRA_PACKAGES = times
\c GENERATE_RTF
\addindex GENERATE_RTF
- If the \c GENERATE_RTF tag is set to \c YES Doxygen will generate RTF output.
+ If the \c GENERATE_RTF tag is set to \c YES doxygen will generate RTF output.
The RTF output is optimised for Word 97 and may not look too pretty with
other readers/editors.
@@ -940,7 +941,7 @@ EXTRA_PACKAGES = times
\anchor cfg_compact_rtf
\c COMPACT_RTF
\addindex COMPACT_RTF
- If the \c COMPACT_RTF tag is set to \c YES Doxygen generates more compact
+ If the \c COMPACT_RTF tag is set to \c YES doxygen generates more compact
RTF documents. This may be useful for small projects and may help to
save some trees in general.
@@ -954,7 +955,7 @@ EXTRA_PACKAGES = times
Word compatible reader that support those fields.
\par note:
- wordpad (write) and others do not support links.
+ WordPad (write) and others do not support links.
\anchor cfg_rtf_stylesheet_file
\c RTF_STYLESHEET_FILE
@@ -968,7 +969,7 @@ EXTRA_PACKAGES = times
\anchor cfg_rtf_extensions_file
\c RTF_EXTENSIONS_FILE
- Set optional variables used in the generation of an rtf document.
+ Set optional variables used in the generation of an RTF document.
Syntax is similar to doxygen's config file.
A template extensions file can be generated using
doxygen -e rtf extensionFile.
@@ -981,7 +982,7 @@ EXTRA_PACKAGES = times
\c GENERATE_MAN
\addindex GENERATE_MAN
- If the \c GENERATE_MAN tag is set to \c YES (the default) Doxygen will
+ If the \c GENERATE_MAN tag is set to \c YES (the default) doxygen will
generate man pages for classes and files.
\anchor cfg_man_output
@@ -1002,7 +1003,7 @@ EXTRA_PACKAGES = times
\anchor cfg_man_links
\c MAN_LINKS
\addindex MAN_LINKS
- If the \c MAN_LINKS tag is set to \c YES and Doxygen generates man output,
+ If the \c MAN_LINKS tag is set to \c YES and doxygen generates man output,
then it will generate one additional man file for each entity documented in
the real man page(s). These additional files only source the real man page,
but without them the man command would be unable to find the correct page.
@@ -1016,14 +1017,14 @@ EXTRA_PACKAGES = times
\c ENABLE_PREPROCESSING
\addindex ENABLE_PREPROCESSING
- If the \c ENABLE_PREPROCESSING tag is set to \c YES (the default) Doxygen will
+ If the \c ENABLE_PREPROCESSING tag is set to \c YES (the default) doxygen will
evaluate all C-preprocessor directives found in the sources and include
files.
\anchor cfg_macro_expansion
\c MACRO_EXPANSION
\addindex MACRO_EXPANSION
- If the \c MACRO_EXPANSION tag is set to \c YES Doxygen will expand all macro
+ If the \c MACRO_EXPANSION tag is set to \c YES doxygen will expand all macro
names in the source code. If set to \c NO (the default) only conditional
compilation will be performed. Macro expansion can be done in a controlled
way by setting \c EXPAND_ONLY_PREDEF to \c YES.
@@ -1039,7 +1040,7 @@ EXTRA_PACKAGES = times
\c SEARCH_INCLUDES
\addindex SEARCH_INCLUDES
If the \c SEARCH_INCLUDES tag is set to \c YES (the default) the includes files
- in the \c INCLUDE_PATH (see below) will be search if a \#include is found.
+ in the \c INCLUDE_PATH (see below) will be searched if a \#include is found.
\anchor cfg_include_path
\addindex GENERATE_LEGEND
- If the \c GENERATE_LEGEND tag is set to \c YES (the default) Doxygen will
+ If the \c GENERATE_LEGEND tag is set to \c YES (the default) doxygen will
generate a legend page explaining the meaning of the various boxes and
arrows in the dot generated graphs.
@@ -1222,7 +1223,7 @@ TAGFILES = file1=loc1 "file2 = loc2" ...
\c CGI_URL
\addindex CGI_URL
The \c CGI_URL tag should be the absolute URL to the directory where the
- cgi binaries are located. See the documentation of your http daemon for
+ cgi binaries are located. See the documentation of your HTTP daemon for
details.
\anchor cfg_doc_url
@@ -1363,7 +1364,7 @@ EXPAND_AS_DEFINED = Q_OBJECT_FAKE Q_OBJECT ACTIVATE_SIGNAL_WITH_PARAM \
Q_VARIANT_AS
\endverbatim
-Here Doxygen's preprocessor is used to substitute some
+Here doxygen's preprocessor is used to substitute some
macro names that are normally substituted by the C preprocessor,
but without doing full macro expansion.
diff --git a/doc/diagrams.doc b/doc/diagrams.doc
index 2153f16..3217800 100644
--- a/doc/diagrams.doc
+++ b/doc/diagrams.doc
@@ -61,7 +61,7 @@
little marker in the lower right corner to indicate that the class
contains base classes that are hidden.
For the class diagrams the maximum tree width is currently 8 elements.
- If a tree wider some nodes will be hidden.
+ If a tree is wider some nodes will be hidden.
If the box is filled with a
dashed pattern the inheritance relation is virtual.
A \b white box indicates that the documentation of the class
@@ -81,7 +81,7 @@
If the box has a \b dashed border this indicates virtual inheritance.
A \b solid arrow indicates public inheritance.
A \b dashed arrow indicates protected inheritance.
-
A \b dotted arrow indicated private inheritance.
+
A \b dotted arrow indicates private inheritance.
The elements in the graphs generated by the dot tool have the following
@@ -91,7 +91,7 @@
A box with a \b red border indicates a node that has
\e more arrows than are shown!
In order words: the graph is \e truncated with respect to this node.
- The reason a graph is sometimes truncated is too prevent images
+ The reason a graph is sometimes truncated is to prevent images
from becoming too large.
For the graphs generated with dot doxygen tries
to limit the width of the resulting image to 1024 pixels.
diff --git a/doc/docblocks.doc b/doc/docblocks.doc
index 547e617..bb73ccb 100644
--- a/doc/docblocks.doc
+++ b/doc/docblocks.doc
@@ -204,7 +204,7 @@ Here is an example of the use of these comment blocks:
for the corresponding HTML documentation that is generated by doxygen.
\endhtmlonly
-\warning These blocks can only be used to document \e members.
+\warning These blocks can only be used to document \e members and \e parameters.
They cannot be used to document files, classes, unions, structs,
groups, namespaces and enums themselves. Furthermore, the structural
commands mentioned in the previous section
diff --git a/doc/doxygen_usage.doc b/doc/doxygen_usage.doc
index 5796896..865f5ca 100644
--- a/doc/doxygen_usage.doc
+++ b/doc/doxygen_usage.doc
@@ -44,7 +44,7 @@ doxygen
If you have a configuration file generated with an older version of
-doxygen that you can upgrade it to the current version by running doxygen
+doxygen, you can upgrade it to the current version by running doxygen
with the -u option.
\verbatim
doxygen -u
@@ -85,7 +85,7 @@ doxygen -w rtf rtfstyle.cfg
file then you can use the optional \c -s option. This can use be
used in combination with the \c -u option, to add or strip the
documentation from an existing configuration file.
- Please use the \c -s this option if you send me a configuration file
+ Please use the \c -s option if you send me a configuration file
as part of a bug report!
To make doxygen read/write to standard input/output instead of from/to
a file, use \c - for the file name.
diff --git a/doc/doxysearch_usage.doc b/doc/doxysearch_usage.doc
index 72dc397..6d6ad29 100644
--- a/doc/doxysearch_usage.doc
+++ b/doc/doxysearch_usage.doc
@@ -27,7 +27,7 @@ Doxysearch must be run as a CGI binary. This implies the following:
You must have permission to install and execute a CGI binary on the
target.
-Ask you system administrator or provider if you are unsure if this is possible.
+Ask your system administrator or provider if you are unsure if this is possible.
In order to be able to search fast and efficient, doxysearch does not
search the generated documentation directly. Instead, it uses an
@@ -131,8 +131,8 @@ This can be done by carefully following these steps:
\par Note:
Doxytag requires quite a large amount of memory to
- generate the search index (about 30 Mb on my Linux box)!
- The resulting index file requires about 3 Mb space on your disk.
+ generate the search index (about 30 MB on my Linux box)!
+ The resulting index file requires about 3 MB space on your disk.
Edit the shell script search.cgi with a text editor.
@@ -174,7 +174,7 @@ http://blizzard/cgi-bin/search.cgi
\endverbatim
in the additional information section of the index.html file.
Start your favourite web browser and click on the link.
- If everything is ok, you should get a page where you can enter
+ If everything is OK, you should get a page where you can enter
search terms.
diff --git a/doc/external.doc b/doc/external.doc
index d8f4285..f3a1e05 100644
--- a/doc/external.doc
+++ b/doc/external.doc
@@ -45,7 +45,7 @@ To generate a tag file for your project, simply put the name of the
tag file after the \ref cfg_generate_tagfile "GENERATE_TAGFILE" option in
the configuration file.
-To combine the output of one or more external projects with you own project
+To combine the output of one or more external projects with your own project
you should specify the name of the tag files after
the \ref cfg_tagfiles "TAGFILES" option in the configuration file.
@@ -57,7 +57,7 @@ There are two ways to do this:
At configuration time:
just assign the location of the output to the
tag files specified after the \ref cfg_tagfiles "TAGFILES" configuration
option. If you use a relative path it should be relative with respect to
- the directory where the html output of your project is generated.
+ the directory where the HTML output of your project is generated.
After compile time:
if you do not assign a location to a tag file,
doxygen will generate dummy links for all external HTML references. It will
also generate a perl script called \ref installdox_usage "installdox" in
diff --git a/doc/faq.doc b/doc/faq.doc
index 7b4894b..f20dfc0 100644
--- a/doc/faq.doc
+++ b/doc/faq.doc
@@ -91,7 +91,7 @@ around the blocks that should be hidden and put:
in the config file then all blocks should be skipped by Doxygen as long
as PREPROCESSING = YES.
-
How can I change what's after the \#include in the class documentation?
+
How can I change what is after the \#include in the class documentation?
You can document your class like
@@ -119,7 +119,7 @@ brackets you should type:
*/
\endverbatim
-
How can I use tag files in combination with compressed HTML
+
How can I use tag files in combination with compressed HTML?
If you want to refer from one compressed HTML file
\c a.chm to another compressed HTML file
@@ -160,7 +160,7 @@ doxygen generates. You can include this by putting
\verbatim
\endverbatim
-In the HEAD section of the HTML page.
+in the HEAD section of the HTML page.
Why does doxygen use Qt?
@@ -194,7 +194,7 @@ This error happens when doxygen lexical scanner has a rules that matches
more than 16K input character in one go. I've seen this happening
on a very large generated file (>16K lines), where the built-in preprocessor
converted it into an empty file (with >16K of newlines). Another case
-where this might happen is if you have lines in you code with more than
+where this might happen is if you have lines in your code with more than
16K characters.
diff --git a/doc/features.doc b/doc/features.doc
index 68d54f0..053a9db 100644
--- a/doc/features.doc
+++ b/doc/features.doc
@@ -14,7 +14,7 @@
* input used in their production; they are not affected by this license.
*
*/
-/*! \page features.html
+/*! \page features Features
\section features Features
@@ -23,12 +23,12 @@
Requires very little overhead from the writer of the documentation.
Plain text will do, but for more fancy or structured output HTML tags
and/or some of doxygen's special commands can be used.
-
Supports C++, (Corba, Microsoft, and KDE-DCOP) Java, IDL and C sources.
+
Supports C++, Java, (Corba, Microsoft, and KDE-DCOP) Java, IDL and C sources.
Supports documentation of files, namespaces, classes, structs, unions,
templates, variables, functions, typedefs, enums and defines.
JavaDoc (1.1), Qt-Doc, and KDOC compatible.
Automatically generates class diagrams in HTML (as clickable
- image maps) and \f$\mbox{\LaTeX}\f$ (as encapsulated postscript images).
+ image maps) and \f$\mbox{\LaTeX}\f$ (as Encapsulated PostScript images).
Uses the dot tool of the Graphviz tool kit to generate
include dependency graphs, collaboration diagrams, and
graphical class hierarchy graphs.
@@ -38,11 +38,11 @@
Can generate a list of all members of a class (including any inherited
members) along with their protection level.
Outputs documentation in on-line format (HTML and UNIX man page) and
- off-line format (\f$\mbox{\LaTeX}\f$) and RTF simultaniously
+ off-line format (\f$\mbox{\LaTeX}\f$ and RTF) simultaneously
(any of these can be disabled if desired). All formats are optimized for
ease of reading.
Furthermore, compressed HTML can be generated from HTML output using
- Microsoft's HTML help workshop (Windows only) and PDF can be generated
+ Microsoft's HTML Help Workshop (Windows only) and PDF can be generated
from the \f$\mbox{\LaTeX}\f$ output.
Includes a full C preprocessor to allow proper parsing of conditional
code fragments and to allow expansion of all or part of macros definitions.
@@ -57,7 +57,7 @@
Includes a fast, rank based search engine to search for strings or words
in the class and member documentation.
You can type normal HTML tags in your documentation. Doxygen will convert
- them to their equivalent \f$\mbox{\LaTeX}\f$ and man-page
+ them to their equivalent \f$\mbox{\LaTeX}\f$, RTF, and man-page
counterparts automatically.
Allows references to documentation generated for other projects
(or another part of the same project) in a location independent way.
diff --git a/doc/formulas.doc b/doc/formulas.doc
index bd1aa22..e90424f 100644
--- a/doc/formulas.doc
+++ b/doc/formulas.doc
@@ -17,17 +17,17 @@
/*! \page formulas Including formulas
Doxygen allows you to put \f$\mbox{\LaTeX}\f$ formulas in the
-output (this works only for the HTML and \f$\mbox{\LaTeX}\f$ formats,
-not for the man page output). To be able to include formulas (as images)
-in the HTML documentation, you will also need to have the following tools
-installed
+output (this works only for the HTML and \f$\mbox{\LaTeX}\f$ output,
+not for the RTF nor for the man page output). To be able to include
+formulas (as images) in the HTML documentation, you will also need to
+have the following tools installed
\c latex: the \f$\mbox{\LaTeX}\f$ compiler, needed to parse the formulas.
To test I have used the teTeX 0.9 distribution.
-
\c dvips: a tool to convert dvi files to postscript files
+
\c dvips: a tool to convert DVI files to PostScript files
I have used version 5.86 from Radical Eye software for testing.
-
\c gs: the ghostscript interpreter for converting postscript files
- to bitmaps. I have used Aladdin Ghostscript 5.10 for testing.
+
\c gs: the GhostScript interpreter for converting PostScript files
+ to bitmaps. I have used Aladdin GhostScript 5.10 for testing.
There are two ways to include formulas in the documentation.
@@ -44,7 +44,7 @@ There are two ways to include formulas in the documentation.
\f$\sqrt{(x_2-x_1)^2+(y_2-y_1)^2}\f$.
Unnumbered displayed formulas that are centered on a separate line.
- These formulas should be put between \\f\[ and \\f\] commands.
+ These formulas should be put between \\f[ and \\f] commands.
An example:
\verbatim
\f[
diff --git a/doc/history.doc b/doc/history.doc
index eb5f2f1..5a28e9d 100644
--- a/doc/history.doc
+++ b/doc/history.doc
@@ -24,7 +24,7 @@
Using the dot tool of the AT&T's GraphViz package, doxygen can now
generate inheritance diagrams, collaboration diagrams, include
dependency graphs, included by graphs and graphical inheritance overviews.
-
Function arguments can now be documentation with separate comment blocks.
+
Function arguments can now be documented with separate comment blocks.
Initializers and macro definitions are now included in the documentation.
Variables and typedefs are now put in their own section.
Old configuration files can be upgraded using the -u option without
@@ -52,7 +52,7 @@
Support for templates and namespaces.
Internationalization support. Currently supported languages are:
- English, Czech, German, Spanish, Finnish, French, Italian, Japanse,
+ English, Czech, German, Spanish, Finnish, French, Italian, Japanese,
Dutch, and Swedish.
Automatic generation of inheritance diagrams for sub & super classes.
Support for man page, compressed HTML help, and hyperlinked PDF output.
diff --git a/doc/htmlcmds.doc b/doc/htmlcmds.doc
index 0429139..79faf11 100644
--- a/doc/htmlcmds.doc
+++ b/doc/htmlcmds.doc
@@ -38,8 +38,8 @@ documentation. Note that all attributes of a HTML tag are ignored
\c Ends a \c section.
\c
Starts a description list.
\c Ends a description list.
-
\c
Starts a item title.
-
\c
Does not generate any output.
+
\c
Starts an item title.
+
\c
Ends an item title.
\c Starts a piece of text displayed in an italic font.
\c
Ends a \c section.
\c
Does not generate any output.
-
\c
starts a preformatted fragment.
-
\c ends a preformatted fragment.
-
\c starts a section of text displayed in a smaller font.
-
\c
ends a \c section.
-
\c starts a section of bold text.
-
\c
ends a section of bold text.
+
\c Ends a paragraph.
+
\c
Starts a preformatted fragment.
+
\c Ends a preformatted fragment.
+
\c Starts a section of text displayed in a smaller font.
+
\c
Ends a \c section.
+
\c Starts a section of bold text.
+
\c
Ends a section of bold text.
\c Starts a piece of text displayed in subscript.
\c
Ends a \c section.
\c Starts a piece of text displayed in superscript.
\c
Ends a \c section.
-
\c
starts a table, the available space of a page is always
- divided equally amount the columns.
-
\c
ends a table
-
\c
Starts a new table element.
-
\c
Does not generate any output.
+
\c
starts a table.
+
\c
ends a table.
+
\c
Starts a new table data element.
+
\c
Ends a table data element.
\c
Starts a new table row.
-
\c
Does not generate any output.
+
\c Ends a table row.
\c Starts a piece of text displayed in a typewriter font.
\c
Ends a \c section.
\c Starts a piece of text displayed in a typewriter font.
diff --git a/doc/index.doc b/doc/index.doc
index cb1b9c3..a66df37 100644
--- a/doc/index.doc
+++ b/doc/index.doc
@@ -14,7 +14,7 @@
* input used in their production; they are not affected by this license.
*
*/
-/*! \page index
+/*! \page index Index
\if logo_on
\htmlonly
@@ -41,7 +41,7 @@ See the
GNU General Public License
for more details.
-Documents produced by Doxygen are derivative works derived from the
+Documents produced by doxygen are derivative works derived from the
input used in their production; they are not affected by this license.
Introduction
@@ -54,7 +54,7 @@ It can help you in three ways:
off-line reference manual (in \f$\mbox{\LaTeX}\f$) from a set
of documented source files.
There is also support for generating output in RTF (MS-Word),
- Postscript, hyperlinked PDF, compressed HTML, and Unix man pages.
+ PostScript, hyperlinked PDF, compressed HTML, and Unix man pages.
The documentation is extracted directly from the sources, which
makes it much easier to keep the documentation consistent with the
source code.
@@ -70,7 +70,7 @@ It can help you in three ways:
Doxygen is developed under Linux,
but is set-up to be highly portable. As a result, it runs on most
-other UNIX flavors as well. Furthermore, an executable for
+other Unix flavors as well. Furthermore, an executable for
Windows 9x/NT is also available.
This manual is divided into two parts, each of which is divided into several
@@ -98,17 +98,17 @@ The first part forms a user manual:
The second part forms a reference manual:
-
Section \ref features presents an overview of what Doxygen can do.
+
Section \ref features presents an overview of what doxygen can do.
Section \ref history shows what has changed during the development
- of Doxygen and what still has to be done.
+ of doxygen and what still has to be done.
Section \ref doxygen_usage shows how to use the \c doxygen program.
Section \ref doxytag_usage shows how to use the \c doxytag program.
Section \ref doxysearch_usage shows how to use the \c doxysearch program.
Section \ref doxywizard_usage shows how to use the \c doxywizard program.
Section \ref installdox_usage shows how to use the \c installdox
- script that is generated by Doxygen if you use tag files.
+ script that is generated by doxygen if you use tag files.
Section \ref output shows how to generate the various output formats
- supported by Doxygen.
+ supported by doxygen.
Section \ref autolink shows how to put links to files, classes,
and members in the documentation.
Section \ref config shows how to fine-tune doxygen, so it
@@ -151,9 +151,9 @@ Thanks go to:
\addindex Doc++
Malte Zöckler and Roland Wunderling, authors of DOC++.
- The first version of Doxygen borrowed some code of an old version of DOC++.
+ The first version of doxygen borrowed some code of an old version of DOC++.
Although I have rewritten practically all code since then, DOC++ has still
- given me a good start in writing Doxygen.
+ given me a good start in writing doxygen.
All people at Troll Tech, for creating a beautiful GUI Toolkit
(which is very useful as a Windows/Unix platform abstraction layer :-)
My brother Frank
diff --git a/doc/install.doc b/doc/install.doc
index 2a5a6e6..79743b9 100644
--- a/doc/install.doc
+++ b/doc/install.doc
@@ -161,9 +161,10 @@ Compilation is now done by performing the following steps:
make install
\endverbatim
- Binaries are installed in the directory \/bin
- Documentation and examples in the directory
- \/doc/doxygen
+ Binaries are installed in the directory \/bin,
+ documentation and examples in the directory
+ \/share/doc/packages/doxygen (use
+ DOCDIR\\ after make to change this).
\ defaults to /usr but can be changed with
the --prefix option of the configure script.
@@ -182,12 +183,12 @@ Compilation is now done by performing the following steps:
Qt problems
-The Qt include files and libraries are not a sub directory of the
-directory pointed to by QTDIR on some systems.
+The Qt include files and libraries are not a subdirectory of the
+directory pointed to by QTDIR on some systems
(for instance on Red Hat 6.0 includes are in /usr/include/qt and
-libs are in /usr/lib)
+libs are in /usr/lib).
-The solution: goto the root of the doxygen distribution and do:
+The solution: go to the root of the doxygen distribution and do:
\verbatim
mkdir qt
cd qt
@@ -203,7 +204,7 @@ Now install doxygen as described above.
Latex problems
-the file a4wide.sty is not available for all distributions. If
+The file a4wide.sty is not available for all distributions. If
your distribution does not have it please select another paper type
in the config file (see the \ref cfg_paper_type "PAPER_TYPE" tag in the
config file).
@@ -352,7 +353,7 @@ Here is what is required:
Borland C++ or MINGW (see http://www.mingw.org) are also supported.
-
Perl 5.0 or higher for Windows. This can be download from:
+
Perl 5.0 or higher for Windows. This can be downloaded from:
http://www.ActiveState.com/Products/ActivePerl/
The GNU tools flex, bison, and sed.
@@ -390,7 +391,7 @@ Here is what is required:
As a result doxygen can be compiled on systems without X11 or the
commerical version of Qt.
- For doxywizard, a complete Qt library this is
+ For doxywizard, a complete Qt library is
still a requirement however. You may be interested in the professional
license of Qt for
Windows \latexonly\par (see
@@ -400,7 +401,7 @@ Here is what is required:
To generate LaTeX documentation or formulas in HTML you need the tools:
latex, dvips and gswin32.
To get these working under Windows
- install the fpTeX distribution You can download it at:
+ install the fpTeX distribution. You can download it at:
ftp://ctan.tug.org/tex-archive/systems/win32/web2c/fptex-0.3/
Make sure the tools are available from a dos box, by adding the
@@ -409,7 +410,7 @@ Here is what is required:
For your information, the LaTeX is freely available set of so
called macros and styles on the top of the famous TeX program
(by famous Donald Knuth) and the accompanied utilities (all
- available for free). It is used to for high quality
+ available for free). It is used for high quality
typesetting. The result -- in the form of so called
DVI (DeVice Independent) file -- can be printed or
displayed on various devices preserving exactly the same look up
@@ -457,7 +458,7 @@ Compilation is now done by performing the following steps:
of the documentation into PostScript or PDF.
It is \e not needed for compiling the doxygen's binaries.
-
goto the doxygen root dir and type:
+
Go to the doxygen root dir and type:
\verbatim
make.bat msvc
@@ -486,10 +487,10 @@ Compilation is now done by performing the following steps:
nmake
\endverbatim
- The generated docs int HTML are located in the ..\html
+ The generated HTML docs are located in the ..\html
subdirectory.
- The sources for LaTeX documentation are located in ..\latex
+ The sources for LaTeX documentation are located in the ..\latex
subdirectory. From those sources, the DVI, PostScript, and PDF
documentation can be generated.
diff --git a/doc/maintainers.txt b/doc/maintainers.txt
index bddd9d4..11a231a 100644
--- a/doc/maintainers.txt
+++ b/doc/maintainers.txt
@@ -30,6 +30,7 @@ French
Christophe Bordeux: bordeux@lig.di.epfl.ch
German
+Jens Seidel: jensseidel@users.sourceforge.net
Jens Breitenstein: Jens.Breitenstein@tlc.de
Hungarian
@@ -60,6 +61,9 @@ Alexandru Iosup: aiosup@yahoo.com
Russian
Alexandr Chelpanov: cav@cryptopro.ru
+Slovak
+Stanislav Kudlac: qwerty1@pobox.sk
+
Slovene
Matjaz Ostroversnik: matjaz.ostroversnik@zrs-tk.si
diff --git a/doc/output.doc b/doc/output.doc
index 1c6508f..8e427a9 100644
--- a/doc/output.doc
+++ b/doc/output.doc
@@ -39,14 +39,14 @@ The following output formats are \e indirectly supported by doxygen:
Compressed HTML (a.k.a. Windows 98 help)
Generated by Microsoft's HTML Help workshop from the HTML output if
\c GENERATE_HTMLHELP is set to \c YES.
-
Postscript
+
PostScript
Generated from the \f$\mbox{\LaTeX}\f$ output by
running make ps in the output directory.
For the best results \c PDF_HYPERLINKS should be set to \c NO.