diff options
Diffstat (limited to 'src')
| -rw-r--r-- | src/config.h | 5 | ||||
| -rw-r--r-- | src/config.l | 50 | ||||
| -rw-r--r-- | src/config.xml | 1383 | ||||
| -rwxr-xr-x | src/configgen.py | 137 | ||||
| -rw-r--r-- | src/configoptions.cpp | 3321 | ||||
| -rw-r--r-- | src/dot.cpp | 2 | ||||
| -rw-r--r-- | src/doxygen.cpp | 8 | ||||
| -rw-r--r-- | src/doxygen.css | 4 | ||||
| -rw-r--r-- | src/doxygen_css.h | 4 | ||||
| -rw-r--r-- | src/lang_cfg.h | 1 | ||||
| -rw-r--r-- | src/language.cpp | 9 | ||||
| -rw-r--r-- | src/pre.l | 70 | ||||
| -rw-r--r-- | src/scanner.l | 4 | ||||
| -rw-r--r-- | src/translator_tr.h | 1781 |
14 files changed, 5035 insertions, 1744 deletions
diff --git a/src/config.h b/src/config.h index e2cf96b..f87b2ba 100644 --- a/src/config.h +++ b/src/config.h @@ -342,7 +342,8 @@ class ConfigBool : public ConfigOption class ConfigObsolete : public ConfigOption { public: - ConfigObsolete(OptionType t) : ConfigOption(t) {} + ConfigObsolete(const char *name,OptionType t) : ConfigOption(t) + { m_name = name; } void writeTemplate(QTextStream &,bool,bool) {} void substEnvVars() {} void writeXML(QTextStream&); @@ -523,7 +524,7 @@ class Config /*! Adds an option that has become obsolete. */ ConfigOption *addObsolete(const char *name) { - ConfigObsolete *option = new ConfigObsolete(ConfigOption::O_Obsolete); + ConfigObsolete *option = new ConfigObsolete(name,ConfigOption::O_Obsolete); m_dict->insert(name,option); m_obsolete->append(option); return option; diff --git a/src/config.l b/src/config.l index 0b07236..1f72fe6 100644 --- a/src/config.l +++ b/src/config.l @@ -284,7 +284,9 @@ void ConfigInt::writeXML(QTextStream& t) "docs='\n" << convertToXML(docs()) << "' " "minval='" << m_minVal << "' " "maxval='" << m_maxVal << "' " - "defval='" << m_defValue << "'/>" << endl; + "defval='" << m_defValue << "'"; + if (!m_dependency.isEmpty()) t << " depends='" << m_dependency << "'"; + t << "/>" << endl; } void ConfigBool::writeXML(QTextStream& t) @@ -292,7 +294,9 @@ void ConfigBool::writeXML(QTextStream& t) t << " <option type='bool' " "id='" << convertToXML(name()) << "' " "docs='\n" << convertToXML(docs()) << "' " - "defval='" << m_defValue << "'/>" << endl; + "defval='" << m_defValue << "'"; + if (!m_dependency.isEmpty()) t << " depends='" << m_dependency << "'"; + t << "/>" << endl; } void ConfigString::writeXML(QTextStream& t) @@ -308,7 +312,9 @@ void ConfigString::writeXML(QTextStream& t) "id='" << convertToXML(name()) << "' " "format='" << format << "' " "docs='\n" << convertToXML(docs()) << "' " - "defval='" << convertToXML(m_defValue) << "'/>" << endl; + "defval='" << convertToXML(m_defValue) << "'"; + if (!m_dependency.isEmpty()) t << " depends='" << m_dependency << "'"; + t << "/>" << endl; } void ConfigEnum::writeXML(QTextStream &t) @@ -316,7 +322,9 @@ void ConfigEnum::writeXML(QTextStream &t) t << " <option type='enum' " "id='" << convertToXML(name()) << "' " "defval='" << convertToXML(m_defValue) << "' " - "docs='\n" << convertToXML(docs()) << "'>" << endl; + "docs='\n" << convertToXML(docs()) << "'"; + if (!m_dependency.isEmpty()) t << " depends='" << m_dependency << "'"; + t << ">" << endl; char *enumVal = m_valueRange.first(); while (enumVal) @@ -341,7 +349,9 @@ void ConfigList::writeXML(QTextStream &t) t << " <option type='list' " "id='" << convertToXML(name()) << "' " "format='" << format << "' " - "docs='\n" << convertToXML(docs()) << "'>" << endl; + "docs='\n" << convertToXML(docs()) << "'"; + if (!m_dependency.isEmpty()) t << " depends='" << m_dependency << "'"; + t << ">" << endl; char *enumVal = m_value.first(); while (enumVal) { @@ -355,8 +365,7 @@ void ConfigList::writeXML(QTextStream &t) void ConfigObsolete::writeXML(QTextStream &t) { t << " <option type='obsolete' " - "id='" << convertToXML(name()) << "' " - "docs='" << convertToXML(docs()) << "'/>" << endl; + "id='" << convertToXML(name()) << "'/>" << endl; } @@ -815,8 +824,8 @@ void Config::writeTemplate(QTextStream &t,bool sl,bool upd) void Config::writeXML(QTextStream &t) { t << "<doxygenconfig>" << endl; - ConfigOption *option = m_options->first(); bool first=TRUE; + ConfigOption *option = m_options->first(); while (option) { if (option->kind()==ConfigOption::O_Info) @@ -832,6 +841,12 @@ void Config::writeXML(QTextStream &t) } option = m_options->next(); } + option = m_obsolete->first(); + while (option) + { + option->writeXML(t); + option = m_obsolete->next(); + } if (!first) t << " </group>" << endl; t << "</doxygenconfig>" << endl; } @@ -1337,29 +1352,26 @@ void Config::check() // check QHP creation requirements if (Config_getBool("GENERATE_QHP")) { - bool quit = false; + bool qhp=TRUE; if (!Config_getBool("GENERATE_HTML")) { - config_err("Warning: GENERATE_QHP=YES requires GENERATE_HTML=YES.\n"); - quit = true; + config_err("Error: GENERATE_QHP=YES requires GENERATE_HTML=YES. Disabling QHP output.\n"); + qhp=FALSE; } if (Config_getString("QHP_NAMESPACE").isEmpty()) { - config_err("Warning: GENERATE_QHP=YES requires QHP_NAMESPACE to be set.\n"); - quit = true; + config_err("Error: GENERATE_QHP=YES requires QHP_NAMESPACE to be set. Disabling QHP output.\n"); + qhp=FALSE; } if (Config_getString("QHP_VIRTUAL_FOLDER").isEmpty()) { - config_err("Warning: GENERATE_QHP=YES requires QHP_VIRTUAL_FOLDER to be set.\n"); - quit = true; + config_err("Error: GENERATE_QHP=YES requires QHP_VIRTUAL_FOLDER to be set. Disabling QHP output.\n"); + qhp=FALSE; } - if (quit) - { - exit(1); - } + Config_getBool("GENERATE_QHP")=qhp; } // check QCH creation requirements diff --git a/src/config.xml b/src/config.xml new file mode 100644 index 0000000..90b77b2 --- /dev/null +++ b/src/config.xml @@ -0,0 +1,1383 @@ +<doxygenconfig> + <group name='Project' docs='Project related configuration options'> + <option type='string' id='DOXYFILE_ENCODING' format='string' docs=' +This tag specifies the encoding used for all characters in the config file +that follow. The default is UTF-8 which is also the encoding used for all +text before the first occurrence of this tag. Doxygen uses libiconv (or the +iconv built into libc) for the transcoding. See +http://www.gnu.org/software/libiconv for the list of possible encodings. +' defval='UTF-8'/> + <option type='string' id='PROJECT_NAME' format='string' docs=' +The PROJECT_NAME tag is a single word (or a sequence of words surrounded +by quotes) that should identify the project. ' defval=''/> + <option type='string' id='PROJECT_NUMBER' format='string' docs=' +The PROJECT_NUMBER tag can be used to enter a project or revision number. +This could be handy for archiving the generated documentation or +if some version control system is used. +' defval=''/> + <option type='string' id='OUTPUT_DIRECTORY' format='dir' docs=' +The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +base path where the generated documentation will be put. +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. +' defval=''/> + <option type='bool' id='CREATE_SUBDIRS' docs=' +If the CREATE_SUBDIRS tag is set to YES, then doxygen will create +4096 sub-directories (in 2 levels) under the output directory of each output +format and will distribute the generated files over these directories. +Enabling this option can be useful when feeding doxygen a huge amount of +source files, where putting all generated files in the same directory would +otherwise cause performance problems for the file system. +' defval='0'/> + <option type='enum' id='OUTPUT_LANGUAGE' defval='English' docs=' +The OUTPUT_LANGUAGE tag is used to specify the language in which all +documentation generated by doxygen is written. Doxygen will use this +information to generate all constant output in the proper language. +The default language is English, other supported languages are: +Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, +Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, +Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), +Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, +Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, Slovene, +Spanish, Swedish, and Ukrainian. +'> + <value name='Afrikaans'/> + <value name='Arabic'/> + <value name='Brazilian'/> + <value name='Catalan'/> + <value name='Chinese'/> + <value name='Chinese-Traditional'/> + <value name='Croatian'/> + <value name='Czech'/> + <value name='Danish'/> + <value name='Dutch'/> + <value name='English'/> + <value name='Finnish'/> + <value name='French'/> + <value name='German'/> + <value name='Greek'/> + <value name='Hungarian'/> + <value name='Italian'/> + <value name='Japanese'/> + <value name='Japanese-en'/> + <value name='Korean'/> + <value name='Korean-en'/> + <value name='Norwegian'/> + <value name='Farsi'/> + <value name='Persian'/> + <value name='Polish'/> + <value name='Portuguese'/> + <value name='Romanian'/> + <value name='Russian'/> + <value name='Serbian'/> + <value name='Slovak'/> + <value name='Slovene'/> + <value name='Spanish'/> + <value name='Swedish'/> + <value name='Ukrainian'/> + </option> + <option type='bool' id='BRIEF_MEMBER_DESC' docs=' +If the BRIEF_MEMBER_DESC tag is set to 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. +' defval='1'/> + <option type='bool' id='REPEAT_BRIEF' docs=' +If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend +the brief description of a member or function before the detailed description. +Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +brief descriptions will be completely suppressed. +' defval='1'/> + <option type='list' id='ABBREVIATE_BRIEF' format='string' docs=' +This tag implements a quasi-intelligent brief description abbreviator +that is used to form the text in various listings. Each string +in this list, if found as the leading text of the brief description, will be +stripped from the text and the result after processing the whole list, is +used as the annotated text. Otherwise, the brief description is used as-is. +If left blank, the following values are used ("$name" is automatically +replaced with the name of the entity): "The $name class" "The $name widget" +"The $name file" "is" "provides" "specifies" "contains" +"represents" "a" "an" "the" +'> + <value name='The $name class'/> + <value name='The $name widget'/> + <value name='The $name file'/> + <value name='is'/> + <value name='provides'/> + <value name='specifies'/> + <value name='contains'/> + <value name='represents'/> + <value name='a'/> + <value name='an'/> + <value name='the'/> + </option> + <option type='bool' id='ALWAYS_DETAILED_SEC' docs=' +If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +Doxygen will generate a detailed section even if there is only a brief +description. +' defval='0'/> + <option type='bool' id='INLINE_INHERITED_MEMB' docs=' +If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all +inherited members of a class in the documentation of that class as if those +members were ordinary class members. Constructors, destructors and assignment +operators of the base classes will not be shown. +' defval='0'/> + <option type='bool' id='FULL_PATH_NAMES' docs=' +If the FULL_PATH_NAMES tag is set to YES then 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. +' defval='1'/> + <option type='list' id='STRIP_FROM_PATH' format='string' docs=' +If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +can be used to strip a user-defined part of the path. Stripping is +only done if one of the specified strings matches the left-hand part of +the path. The tag can be used to show relative paths in the file list. +If left blank the directory from which doxygen is run is used as the +path to strip. +' depends='FULL_PATH_NAMES'> + <value name='/Users/dimitri/doxygen/mail/1.5.7/doxywizard/'/> + </option> + <option type='list' id='STRIP_FROM_INC_PATH' format='string' docs=' +The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of +the path mentioned in the documentation of a class, which tells +the reader which header file to include in order to use a class. +If left blank only the name of the header file containing the class +definition is used. Otherwise one should specify the include paths that +are normally passed to the compiler using the -I flag. +'> + </option> + <option type='bool' id='SHORT_NAMES' docs=' +If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +(but less readable) file names. This can be useful is your file systems +doesn't support long names like on DOS, Mac, or CD-ROM. +' defval='0'/> + <option type='bool' id='JAVADOC_AUTOBRIEF' docs=' +If the JAVADOC_AUTOBRIEF tag is set to 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 JavaDoc +comments will behave just like regular Qt-style comments +(thus requiring an explicit @brief command for a brief description.) +' defval='0'/> + <option type='bool' id='QT_AUTOBRIEF' docs=' +If the QT_AUTOBRIEF tag is set to YES then Doxygen will +interpret the first line (until the first dot) of a Qt-style +comment as the brief description. If set to NO, the comments +will behave just like regular Qt-style comments (thus requiring +an explicit \brief command for a brief description.) +' defval='0'/> + <option type='bool' id='MULTILINE_CPP_IS_BRIEF' docs=' +The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +treat a multi-line C++ special comment block (i.e. a block of //! or /// +comments) as a brief description. This used to be the default behaviour. +The new default is to treat a multi-line C++ comment block as a detailed +description. Set this tag to YES if you prefer the old behaviour instead. +' defval='0'/> + <option type='bool' id='INHERIT_DOCS' docs=' +If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +member inherits the documentation from any documented member that it +re-implements. +' defval='1'/> + <option type='bool' id='SEPARATE_MEMBER_PAGES' docs=' +If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce +a new page for each member. If set to NO, the documentation of a member will +be part of the file/class/namespace that contains it. +' defval='0'/> + <option type='int' id='TAB_SIZE' docs=' +The TAB_SIZE tag can be used to set the number of spaces in a tab. +Doxygen uses this value to replace tabs by spaces in code fragments. +' minval='1' maxval='16' defval='8'/> + <option type='list' id='ALIASES' format='string' docs=' +This tag can be used to specify a number of aliases that acts +as commands in the documentation. An alias has the form "name=value". +For example adding "sideeffect=\par Side Effects:\n" will allow you to +put the command \sideeffect (or @sideeffect) in the documentation, which +will result in a user-defined paragraph with heading "Side Effects:". +You can put \n's in the value part of an alias to insert newlines. +'> + </option> + <option type='bool' id='OPTIMIZE_OUTPUT_FOR_C' docs=' +Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C +sources only. Doxygen will then generate output that is more tailored for C. +For instance, some of the names that are used will be different. The list +of all members will be omitted, etc. +' defval='0'/> + <option type='bool' id='OPTIMIZE_OUTPUT_JAVA' docs=' +Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java +sources only. Doxygen will then generate output that is more tailored for +Java. For instance, namespaces will be presented as packages, qualified +scopes will look different, etc. +' defval='0'/> + <option type='bool' id='OPTIMIZE_FOR_FORTRAN' docs=' +Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran +sources only. Doxygen will then generate output that is more tailored for +Fortran. +' defval='0'/> + <option type='bool' id='OPTIMIZE_OUTPUT_VHDL' docs=' +Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL +sources. Doxygen will then generate output that is tailored for +VHDL. +' defval='0'/> + <option type='list' id='EXTENSION_MAPPING' format='string' docs=' +Doxygen selects the parser to use depending on the extension of the files it parses. +With this tag you can assign which parser to use for a given extension. +Doxygen has a built-in mapping, but you can override or extend it using this tag. +The format is ext=language, where ext is a file extension, and language is one of +the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, +Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat +.inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), +use: inc=Fortran f=C +'> + </option> + <option type='bool' id='BUILTIN_STL_SUPPORT' docs=' +If you use STL classes (i.e. std::string, std::vector, etc.) but do not want +to include (a tag file for) the STL sources as input, then you should +set this tag to YES in order to let doxygen match functions declarations and +definitions whose arguments contain STL classes (e.g. func(std::string); v.s. +func(std::string) {}). This also make the inheritance and collaboration +diagrams that involve STL classes more complete and accurate. +' defval='0'/> + <option type='bool' id='CPP_CLI_SUPPORT' docs=' +If you use Microsoft's C++/CLI language, you should set this option to YES to +enable parsing support. +' defval='0'/> + <option type='bool' id='SIP_SUPPORT' docs=' +Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. +Doxygen will parse them like normal C++ but will assume all classes use public +instead of private inheritance when no explicit protection keyword is present. +' defval='0'/> + <option type='bool' id='IDL_PROPERTY_SUPPORT' docs=' +For Microsoft's IDL there are propget and propput attributes to indicate getter +and setter methods for a property. Setting this option to YES (the default) +will make doxygen to replace the get and set methods by a property in the +documentation. This will only work if the methods are indeed getting or +setting a simple type. If this is not the case, or you want to show the +methods anyway, you should set this option to NO. +' defval='1'/> + <option type='bool' id='DISTRIBUTE_GROUP_DOC' docs=' +If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +tag is set to YES, then doxygen will reuse the documentation of the first +member in the group (if any) for the other members of the group. By default +all members of a group must be documented explicitly. +' defval='0'/> + <option type='bool' id='SUBGROUPING' docs=' +Set the SUBGROUPING tag to YES (the default) to allow class member groups of +the same type (for instance a group of public functions) to be put as a +subgroup of that type (e.g. under the Public Functions section). Set it to +NO to prevent subgrouping. Alternatively, this can be done per class using +the \nosubgrouping command. +' defval='1'/> + <option type='bool' id='TYPEDEF_HIDES_STRUCT' docs=' +When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum +is documented as struct, union, or enum with the name of the typedef. So +typedef struct TypeS {} TypeT, will appear in the documentation as a struct +with name TypeT. When disabled the typedef will appear as a member of a file, +namespace, or class. And the struct will be named TypeS. This can typically +be useful for C code in case the coding convention dictates that all compound +types are typedef'ed and only the typedef is referenced, never the tag name. +' defval='0'/> + <option type='int' id='SYMBOL_CACHE_SIZE' docs=' +The SYMBOL_CACHE_SIZE determines the size of the internal cache use to +determine which symbols to keep in memory and which to flush to disk. +When the cache is full, less often used symbols will be written to disk. +For small to medium size projects (<1000 input files) the default value is +probably good enough. For larger projects a too small cache size can cause +doxygen to be busy swapping symbols to and from disk most of the time +causing a significant performance penality. +If the system has enough physical memory increasing the cache will improve the +performance by keeping more symbols in memory. Note that the value works on +a logarithmic scale so increasing the size by one will rougly double the +memory usage. The cache size is given by this formula: +2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, +corresponding to a cache size of 2^16 = 65536 symbols +' minval='0' maxval='9' defval='0'/> + </group> + <group name='Build' docs='Build related configuration options'> + <option type='bool' id='EXTRACT_ALL' docs=' +If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +documentation are documented, even if no documentation was available. +Private class members and static file members will be hidden unless +the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES +' defval='0'/> + <option type='bool' id='EXTRACT_PRIVATE' docs=' +If the EXTRACT_PRIVATE tag is set to YES all private members of a class +will be included in the documentation. +' defval='0'/> + <option type='bool' id='EXTRACT_STATIC' docs=' +If the EXTRACT_STATIC tag is set to YES all static members of a file +will be included in the documentation. +' defval='0'/> + <option type='bool' id='EXTRACT_LOCAL_CLASSES' docs=' +If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) +defined locally in source files will be included in the documentation. +If set to NO only classes defined in header files are included. +' defval='1'/> + <option type='bool' id='EXTRACT_LOCAL_METHODS' docs=' +This flag is only useful for Objective-C code. When set to YES local +methods, which are defined in the implementation section but not in +the interface are included in the documentation. +If set to NO (the default) only methods in the interface are included. +' defval='0'/> + <option type='bool' id='EXTRACT_ANON_NSPACES' docs=' +If this flag is set to YES, the members of anonymous namespaces will be +extracted and appear in the documentation as a namespace called +'anonymous_namespace{file}', where file will be replaced with the base +name of the file that contains the anonymous namespace. By default +anonymous namespace are hidden. +' defval='0'/> + <option type='bool' id='HIDE_UNDOC_MEMBERS' docs=' +If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +undocumented members of documented classes, files or namespaces. +If set to NO (the default) these members will be included in the +various overviews, but no documentation section is generated. +This option has no effect if EXTRACT_ALL is enabled. +' defval='0'/> + <option type='bool' id='HIDE_UNDOC_CLASSES' docs=' +If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +undocumented classes that are normally visible in the class hierarchy. +If set to NO (the default) these classes will be included in the various +overviews. This option has no effect if EXTRACT_ALL is enabled. +' defval='0'/> + <option type='bool' id='HIDE_FRIEND_COMPOUNDS' docs=' +If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +friend (class|struct|union) declarations. +If set to NO (the default) these declarations will be included in the +documentation. +' defval='0'/> + <option type='bool' id='HIDE_IN_BODY_DOCS' docs=' +If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +documentation blocks found inside the body of a function. +If set to NO (the default) these blocks will be appended to the +function's detailed documentation block. +' defval='0'/> + <option type='bool' id='INTERNAL_DOCS' docs=' +The INTERNAL_DOCS tag determines if documentation +that is typed after a \internal command is included. If the tag is set +to NO (the default) then the documentation will be excluded. +Set it to YES to include the internal documentation. +' defval='0'/> + <option type='bool' id='CASE_SENSE_NAMES' docs=' +If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate +file names in lower-case letters. If set to 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 supports case sensitive file names. Windows +and Mac users are advised to set this option to NO. +' defval='0' altdefval='portable_fileSystemIsCaseSensitive()'/> + <option type='bool' id='HIDE_SCOPE_NAMES' docs=' +If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +will show members with their full class and namespace scopes in the +documentation. If set to YES the scope will be hidden. +' defval='0'/> + <option type='bool' id='SHOW_INCLUDE_FILES' docs=' +If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +will put a list of the files that are included by a file in the documentation +of that file. +' defval='1'/> + <option type='bool' id='INLINE_INFO' docs=' +If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +is inserted in the documentation for inline members. +' defval='1'/> + <option type='bool' id='SORT_MEMBER_DOCS' docs=' +If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen +will sort the (detailed) documentation of file and class members +alphabetically by member name. If set to NO the members will appear in +declaration order. +' defval='1'/> + <option type='bool' id='SORT_BRIEF_DOCS' docs=' +If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the +brief documentation of file, namespace and class members alphabetically +by member name. If set to NO (the default) the members will appear in +declaration order. +' defval='0'/> + <option type='bool' id='SORT_GROUP_NAMES' docs=' +If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the +hierarchy of group names into alphabetical order. If set to NO (the default) +the group names will appear in their defined order. +' defval='0'/> + <option type='bool' id='SORT_BY_SCOPE_NAME' docs=' +If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be +sorted by fully-qualified names, including namespaces. If set to +NO (the default), the class list will be sorted only by class name, +not including the namespace part. +Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. +Note: This option applies only to the class list, not to the +alphabetical list. +' defval='0'/> + <option type='bool' id='GENERATE_TODOLIST' docs=' +The GENERATE_TODOLIST tag can be used to enable (YES) or +disable (NO) the todo list. This list is created by putting \todo +commands in the documentation. +' defval='1'/> + <option type='bool' id='GENERATE_TESTLIST' docs=' +The GENERATE_TESTLIST tag can be used to enable (YES) or +disable (NO) the test list. This list is created by putting \test +commands in the documentation. +' defval='1'/> + <option type='bool' id='GENERATE_BUGLIST' docs=' +The GENERATE_BUGLIST tag can be used to enable (YES) or +disable (NO) the bug list. This list is created by putting \bug +commands in the documentation. +' defval='1'/> + <option type='bool' id='GENERATE_DEPRECATEDLIST' docs=' +The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or +disable (NO) the deprecated list. This list is created by putting +\deprecated commands in the documentation. +' defval='1'/> + <option type='list' id='ENABLED_SECTIONS' format='string' docs=' +The ENABLED_SECTIONS tag can be used to enable conditional +documentation sections, marked by \if sectionname ... \endif. +'> + </option> + <option type='int' id='MAX_INITIALIZER_LINES' docs=' +The MAX_INITIALIZER_LINES tag determines the maximum number of lines +the initial value of a variable or define consists of for it to appear in +the documentation. If the initializer consists of more lines than specified +here it will be hidden. Use a value of 0 to hide initializers completely. +The appearance of the initializer of individual variables and defines in the +documentation can be controlled using \showinitializer or \hideinitializer +command in the documentation regardless of this setting. +' minval='0' maxval='10000' defval='30'/> + <option type='bool' id='SHOW_USED_FILES' docs=' +Set the SHOW_USED_FILES tag to NO to disable the list of files generated +at the bottom of the documentation of classes and structs. If set to YES the +list will mention the files that were used to generate the documentation. +' defval='1'/> + <option type='bool' id='SHOW_DIRECTORIES' docs=' +If the sources in your project are distributed over multiple directories +then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy +in the documentation. The default is NO. +' defval='0'/> + <option type='bool' id='SHOW_FILES' docs=' +Set the SHOW_FILES tag to NO to disable the generation of the Files page. +This will remove the Files entry from the Quick Index and from the +Folder Tree View (if specified). The default is YES. +' defval='1'/> + <option type='bool' id='SHOW_NAMESPACES' docs=' +Set the SHOW_NAMESPACES tag to NO to disable the generation of the +Namespaces page. This will remove the Namespaces entry from the Quick Index +and from the Folder Tree View (if specified). The default is YES. +' defval='1'/> + <option type='string' id='FILE_VERSION_FILTER' format='file' docs=' +The FILE_VERSION_FILTER tag can be used to specify a program or script that +doxygen should invoke to get the current version for each file (typically from +the version control system). Doxygen will invoke the program by executing (via +popen()) the command <command> <input-file>, where <command> is the value of +the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file +provided by doxygen. Whatever the program writes to standard output +is used as the file version. See the manual for examples. +' defval=''/> + <option type='string' id='LAYOUT_FILE' format='file' docs=' +The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by +doxygen. The layout file controls the global structure of the generated output files +in an output format independent way. The create the layout file that represents +doxygen's defaults, run doxygen with the -l option. You can optionally specify a +file name after the option, if omitted DoxygenLayout.xml will be used as the name +of the layout file. +' defval=''/> + </group> + <group name='Messages' docs='configuration options related to warning and progress messages'> + <option type='bool' id='QUIET' docs=' +The QUIET tag can be used to turn on/off the messages that are generated +by doxygen. Possible values are YES and NO. If left blank NO is used. +' defval='0'/> + <option type='bool' id='WARNINGS' docs=' +The WARNINGS tag can be used to turn on/off the warning messages that are +generated by doxygen. Possible values are YES and NO. If left blank +NO is used. +' defval='1'/> + <option type='bool' id='WARN_IF_UNDOCUMENTED' docs=' +If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +for undocumented members. If EXTRACT_ALL is set to YES then this flag will +automatically be disabled. +' defval='1'/> + <option type='bool' id='WARN_IF_DOC_ERROR' docs=' +If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +potential errors in the documentation, such as not documenting some +parameters in a documented function, or documenting parameters that +don't exist or using markup commands wrongly. +' defval='1'/> + <option type='bool' id='WARN_NO_PARAMDOC' docs=' +This WARN_NO_PARAMDOC option can be abled to get warnings for +functions that are documented, but have no documentation for their parameters +or return value. If set to NO (the default) doxygen will only warn about +wrong or incomplete parameter documentation, but not about the absence of +documentation. +' defval='0'/> + <option type='string' id='WARN_FORMAT' format='string' docs=' +The WARN_FORMAT tag determines the format of the warning messages that +doxygen can produce. The string should contain the $file, $line, and $text +tags, which will be replaced by the file and line number from which the +warning originated and the warning text. Optionally the format may contain +$version, which will be replaced by the version of the file (if it could +be obtained via FILE_VERSION_FILTER) +' defval='$file:$line: $text'/> + <option type='string' id='WARN_LOGFILE' format='file' docs=' +The WARN_LOGFILE tag can be used to specify a file to which warning +and error messages should be written. If left blank the output is written +to stderr. +' defval=''/> + </group> + <group name='Input' docs='configuration options related to the input files'> + <option type='list' id='INPUT' format='filedir' docs=' +The INPUT tag can be used to specify the files and/or directories that contain +documented source files. You may enter file names like "myfile.cpp" or +directories like "/usr/src/myproject". Separate the files or directories +with spaces. +'> + <value name='/Users/dimitri/doxygen/mail/1.5.7/doxywizard'/> + </option> + <option type='string' id='INPUT_ENCODING' format='string' docs=' +This tag can be used to specify the character encoding of the source files +that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is +also the default input encoding. Doxygen uses libiconv (or the iconv built +into libc) for the transcoding. See http://www.gnu.org/software/libiconv for +the list of possible encodings. +' defval='UTF-8'/> + <option type='list' id='FILE_PATTERNS' format='string' docs=' +If the value of the INPUT tag contains directories, you can use the +FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +and *.h) to filter out the source-files in the directories. If left +blank the following patterns are tested: +*.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx +*.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 +'> + <value name='*.c'/> + <value name='*.cc'/> + <value name='*.cxx'/> + <value name='*.cpp'/> + <value name='*.c++'/> + <value name='*.d'/> + <value name='*.java'/> + <value name='*.ii'/> + <value name='*.ixx'/> + <value name='*.ipp'/> + <value name='*.i++'/> + <value name='*.inl'/> + <value name='*.h'/> + <value name='*.hh'/> + <value name='*.hxx'/> + <value name='*.hpp'/> + <value name='*.h++'/> + <value name='*.idl'/> + <value name='*.odl'/> + <value name='*.cs'/> + <value name='*.php'/> + <value name='*.php3'/> + <value name='*.inc'/> + <value name='*.m'/> + <value name='*.mm'/> + <value name='*.dox'/> + <value name='*.py'/> + <value name='*.f90'/> + <value name='*.f'/> + <value name='*.vhd'/> + <value name='*.vhdl'/> + </option> + <option type='bool' id='RECURSIVE' docs=' +The RECURSIVE tag can be used to turn specify whether or not subdirectories +should be searched for input files as well. Possible values are YES and NO. +If left blank NO is used. +' defval='0'/> + <option type='list' id='EXCLUDE' format='filedir' docs=' +The EXCLUDE tag can be used to specify files and/or directories that should +excluded from the INPUT source files. This way you can easily exclude a +subdirectory from a directory tree whose root is specified with the INPUT tag. +'> + </option> + <option type='bool' id='EXCLUDE_SYMLINKS' docs=' +The EXCLUDE_SYMLINKS tag can be used select whether or not files or +directories that are symbolic links (a Unix filesystem feature) are excluded +from the input. +' defval='0'/> + <option type='list' id='EXCLUDE_PATTERNS' format='string' docs=' +If the value of the INPUT tag contains directories, you can use the +EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +certain files from those directories. Note that the wildcards are matched +against the file with absolute path, so to exclude all test directories +for example use the pattern */test/* +'> + </option> + <option type='list' id='EXCLUDE_SYMBOLS' format='string' docs=' +The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names +(namespaces, classes, functions, etc.) that should be excluded from the +output. The symbol name can be a fully qualified name, a word, or if the +wildcard * is used, a substring. Examples: ANamespace, AClass, +AClass::ANamespace, ANamespace::*Test +'> + </option> + <option type='list' id='EXAMPLE_PATH' format='dir' docs=' +The EXAMPLE_PATH tag can be used to specify one or more files or +directories that contain example code fragments that are included (see +the \include command). +'> + </option> + <option type='list' id='EXAMPLE_PATTERNS' format='string' docs=' +If the value of the EXAMPLE_PATH tag contains directories, you can use the +EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +and *.h) to filter out the source-files in the directories. If left +blank all files are included. +'> + <value name='*'/> + </option> + <option type='bool' id='EXAMPLE_RECURSIVE' docs=' +If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +searched for input files to be used with the \include or \dontinclude +commands irrespective of the value of the RECURSIVE tag. +Possible values are YES and NO. If left blank NO is used. +' defval='0'/> + <option type='list' id='IMAGE_PATH' format='dir' docs=' +The IMAGE_PATH tag can be used to specify one or more files or +directories that contain image that are included in the documentation (see +the \image command). +'> + </option> + <option type='string' id='INPUT_FILTER' format='file' docs=' +The INPUT_FILTER tag can be used to specify a program that doxygen should +invoke to filter for each input file. Doxygen will invoke the filter program +by executing (via popen()) the command <filter> <input-file>, where <filter> +is the value of the INPUT_FILTER tag, and <input-file> is the name of an +input file. Doxygen will then use the output that the filter program writes +to standard output. If FILTER_PATTERNS is specified, this tag will be +ignored. +' defval=''/> + <option type='list' id='FILTER_PATTERNS' format='file' docs=' +The FILTER_PATTERNS tag can be used to specify filters on a per file pattern +basis. Doxygen will compare the file name with each pattern and apply the +filter if there is a match. The filters are a list of the form: +pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further +info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER +is applied to all files. +'> + </option> + <option type='bool' id='FILTER_SOURCE_FILES' docs=' +If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +INPUT_FILTER) will be used to filter the input files when producing source +files to browse (i.e. when SOURCE_BROWSER is set to YES). +' defval='0'/> + </group> + <group name='Source Browser' docs='configuration options related to source browsing'> + <option type='bool' id='SOURCE_BROWSER' docs=' +If the SOURCE_BROWSER tag is set to YES then a list of source files will +be generated. Documented entities will be cross-referenced with these sources. +Note: To get rid of all source code in the generated output, make sure also +VERBATIM_HEADERS is set to NO. +' defval='0'/> + <option type='bool' id='INLINE_SOURCES' docs=' +Setting the INLINE_SOURCES tag to YES will include the body +of functions and classes directly in the documentation. +' defval='0'/> + <option type='bool' id='STRIP_CODE_COMMENTS' docs=' +Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +doxygen to hide any special comment blocks from generated source code +fragments. Normal C and C++ comments will always remain visible. +' defval='1'/> + <option type='bool' id='REFERENCED_BY_RELATION' docs=' +If the REFERENCED_BY_RELATION tag is set to YES +then for each documented function all documented +functions referencing it will be listed. +' defval='0'/> + <option type='bool' id='REFERENCES_RELATION' docs=' +If the REFERENCES_RELATION tag is set to YES +then for each documented function all documented entities +called/used by that function will be listed. +' defval='0'/> + <option type='bool' id='REFERENCES_LINK_SOURCE' docs=' +If the REFERENCES_LINK_SOURCE tag is set to YES (the default) +and SOURCE_BROWSER tag is set to YES, then the hyperlinks from +functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will +link to the source code. Otherwise they will link to the documentation. +' defval='1'/> + <option type='bool' id='USE_HTAGS' docs=' +If the USE_HTAGS tag is set to YES then the references to source code +will point to the HTML generated by the htags(1) tool instead of doxygen +built-in source browser. The htags tool is part of GNU's global source +tagging system (see http://www.gnu.org/software/global/global.html). You +will need version 4.8.6 or higher. +' defval='0' depends='SOURCE_BROWSER'/> + <option type='bool' id='VERBATIM_HEADERS' docs=' +If the VERBATIM_HEADERS tag is set to 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. +' defval='1'/> + </group> + <group name='Index' docs='configuration options related to the alphabetical class index'> + <option type='bool' id='ALPHABETICAL_INDEX' docs=' +If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +of all compounds will be generated. Enable this if the project +contains a lot of classes, structs, unions or interfaces. +' defval='0'/> + <option type='int' id='COLS_IN_ALPHA_INDEX' docs=' +If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +in which this list will be split (can be a number in the range [1..20]) +' minval='1' maxval='20' defval='5'/> + <option type='list' id='IGNORE_PREFIX' format='string' docs=' +In case all classes in a project start with a common prefix, all +classes will be put under the same header in the alphabetical index. +The IGNORE_PREFIX tag can be used to specify one or more prefixes that +should be ignored while generating the index headers. +'> + </option> + </group> + <group name='HTML' docs='configuration options related to the HTML output'> + <option type='bool' id='GENERATE_HTML' docs=' +If the GENERATE_HTML tag is set to YES (the default) Doxygen will +generate HTML output. +' defval='1'/> + <option type='string' id='HTML_OUTPUT' format='dir' docs=' +The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +If a relative path is entered the value of OUTPUT_DIRECTORY will be +put in front of it. If left blank `html' will be used as the default path. +' defval='html' depends='GENERATE_HTML'/> + <option type='string' id='HTML_FILE_EXTENSION' format='string' docs=' +The HTML_FILE_EXTENSION tag can be used to specify the file extension for +each generated HTML page (for example: .htm,.php,.asp). If it is left blank +doxygen will generate files with .html extension. +' defval='.html' depends='GENERATE_HTML'/> + <option type='string' id='HTML_HEADER' format='file' docs=' +The HTML_HEADER tag can be used to specify a personal HTML header for +each generated HTML page. If it is left blank doxygen will generate a +standard header. +' defval='' depends='GENERATE_HTML'/> + <option type='string' id='HTML_FOOTER' format='file' docs=' +The HTML_FOOTER tag can be used to specify a personal HTML footer for +each generated HTML page. If it is left blank doxygen will generate a +standard footer. +' defval='' depends='GENERATE_HTML'/> + <option type='string' id='HTML_STYLESHEET' format='file' docs=' +The HTML_STYLESHEET tag can be used to specify a user-defined cascading +style sheet that is used by each HTML page. It can be used to +fine-tune the look of the HTML output. If the tag is left blank doxygen +will generate a default style sheet. Note that doxygen will try to copy +the style sheet file to the HTML output directory, so don't put your own +stylesheet in the HTML output directory as well, or it will be erased! +' defval='' depends='GENERATE_HTML'/> + <option type='bool' id='HTML_ALIGN_MEMBERS' docs=' +If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +files or namespaces will be aligned in HTML using tables. If set to +NO a bullet list will be used. +' defval='1' depends='GENERATE_HTML'/> + <option type='bool' id='HTML_DYNAMIC_SECTIONS' docs=' +If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML +documentation will contain sections that can be hidden and shown after the +page has loaded. For this to work a browser that supports +JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox +Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). +' defval='0' depends='GENERATE_HTML'/> + <option type='bool' id='GENERATE_DOCSET' docs=' +If the GENERATE_DOCSET tag is set to YES, additional index files +will be generated that can be used as input for Apple's Xcode 3 +integrated development environment, introduced with OSX 10.5 (Leopard). +To create a documentation set, doxygen will generate a Makefile in the +HTML output directory. Running make will produce the docset in that +directory and running "make install" will install the docset in +~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find +it at startup. +See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information. +' defval='0' depends='GENERATE_HTML'/> + <option type='string' id='DOCSET_FEEDNAME' format='string' docs=' +When GENERATE_DOCSET tag is set to YES, this tag determines the name of the +feed. A documentation feed provides an umbrella under which multiple +documentation sets from a single provider (such as a company or product suite) +can be grouped. +' defval='Doxygen generated docs' depends='GENERATE_DOCSET'/> + <option type='string' id='DOCSET_BUNDLE_ID' format='string' docs=' +When GENERATE_DOCSET tag is set to YES, this tag specifies a string that +should uniquely identify the documentation set bundle. This should be a +reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen +will append .docset to the name. +' defval='org.doxygen.Project' depends='GENERATE_DOCSET'/> + <option type='bool' id='GENERATE_HTMLHELP' docs=' +If the GENERATE_HTMLHELP tag is set to YES, additional index files +will be generated that can be used as input for tools like the +Microsoft HTML help workshop to generate a compiled HTML help file (.chm) +of the generated HTML documentation. +' defval='0' depends='GENERATE_HTML'/> + <option type='string' id='CHM_FILE' format='file' docs=' +If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can +be used to specify the file name of the resulting .chm file. You +can add a path in front of the file if the result should not be +written to the html output directory. +' defval='' depends='GENERATE_HTMLHELP'/> + <option type='string' id='HHC_LOCATION' format='file' docs=' +If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can +be used to specify the location (absolute path including file name) of +the HTML help compiler (hhc.exe). If non-empty doxygen will try to run +the HTML help compiler on the generated index.hhp. +' defval='' depends='GENERATE_HTMLHELP'/> + <option type='bool' id='GENERATE_CHI' docs=' +If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag +controls if a separate .chi index file is generated (YES) or that +it should be included in the master .chm file (NO). +' defval='0' depends='GENERATE_HTMLHELP'/> + <option type='string' id='CHM_INDEX_ENCODING' format='string' docs=' +If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING +is used to encode HtmlHelp index (hhk), content (hhc) and project file +content. +' defval='' depends='GENERATE_HTMLHELP'/> + <option type='bool' id='BINARY_TOC' docs=' +If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag +controls whether a binary table of contents is generated (YES) or a +normal table of contents (NO) in the .chm file. +' defval='0' depends='GENERATE_HTMLHELP'/> + <option type='bool' id='TOC_EXPAND' docs=' +The TOC_EXPAND flag can be set to YES to add extra items for group members +to the contents of the HTML help documentation and to the tree view. +' defval='0' depends='GENERATE_HTMLHELP'/> + <option type='bool' id='GENERATE_QHP' docs=' +If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER +are set, an additional index file will be generated that can be used as input for +Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated +HTML documentation. +' defval='0' depends='GENERATE_HTML'/> + <option type='string' id='QCH_FILE' format='file' docs=' +If the QHG_LOCATION tag is specified, the QCH_FILE tag can +be used to specify the file name of the resulting .qch file. +The path specified is relative to the HTML output folder. +' defval='' depends='GENERATE_QHP'/> + <option type='string' id='QHP_NAMESPACE' format='string' docs=' +The QHP_NAMESPACE tag specifies the namespace to use when generating +Qt Help Project output. For more information please see +http://doc.trolltech.com/qthelpproject.html#namespace +' defval='' depends='GENERATE_QHP'/> + <option type='string' id='QHP_VIRTUAL_FOLDER' format='string' docs=' +The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating +Qt Help Project output. For more information please see +http://doc.trolltech.com/qthelpproject.html#virtual-folders +' defval='doc' depends='GENERATE_QHP'/> + <option type='string' id='QHP_CUST_FILTER_NAME' format='string' docs=' +If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. +For more information please see +http://doc.trolltech.com/qthelpproject.html#custom-filters +' defval='' depends='GENERATE_QHP'/> + <option type='string' id='QHP_CUST_FILTER_ATTRS' format='string' docs=' +The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see +<a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>. +' defval='' depends='GENERATE_QHP'/> + <option type='string' id='QHP_SECT_FILTER_ATTRS' format='string' docs=' +The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's +filter section matches. +<a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>. +' defval='' depends='GENERATE_QHP'/> + <option type='string' id='QHG_LOCATION' format='file' docs=' +If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can +be used to specify the location of Qt's qhelpgenerator. +If non-empty doxygen will try to run qhelpgenerator on the generated +.qhp file. +' defval='' depends='GENERATE_QHP'/> + <option type='bool' id='DISABLE_INDEX' docs=' +The DISABLE_INDEX tag can be used to turn on/off the condensed index at +top of each HTML page. The value NO (the default) enables the index and +the value YES disables it. +' defval='0' depends='GENERATE_HTML'/> + <option type='int' id='ENUM_VALUES_PER_LINE' docs=' +This tag can be used to set the number of enum values (range [1..20]) +that doxygen will group on one line in the generated HTML documentation. +' minval='1' maxval='20' defval='4' depends='GENERATE_HTML'/> + <option type='enum' id='GENERATE_TREEVIEW' defval='NONE' docs=' +The GENERATE_TREEVIEW tag is used to specify whether a tree-like index +structure should be generated to display hierarchical information. +If the tag value is set to FRAME, a side panel will be generated +containing a tree-like index structure (just like the one that +is generated for HTML Help). For this to work a browser that supports +JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, +Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are +probably better off using the HTML help feature. Other possible values +for this tag are: HIERARCHIES, which will generate the Groups, Directories, +and Class Hierarchy pages using a tree view instead of an ordered list; +ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which +disables this behavior completely. For backwards compatibility with previous +releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE +respectively. +' depends='GENERATE_HTML'> + <value name='NONE'/> + <value name='FRAME'/> + <value name='HIERARCHIES'/> + <value name='ALL'/> + </option> + <option type='int' id='TREEVIEW_WIDTH' docs=' +If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be +used to set the initial width (in pixels) of the frame in which the tree +is shown. +' minval='0' maxval='1500' defval='250' depends='GENERATE_HTML'/> + <option type='int' id='FORMULA_FONTSIZE' docs=' +Use this tag to change the font size of Latex formulas included +as images in the HTML documentation. The default is 10. Note that +when you change the font size after a successful doxygen run you need +to manually remove any form_*.png images from the HTML output directory +to force them to be regenerated. +' minval='8' maxval='50' defval='10' depends='GENERATE_HTML'/> + </group> + <group name='LaTeX' docs='configuration options related to the LaTeX output'> + <option type='bool' id='GENERATE_LATEX' docs=' +If the GENERATE_LATEX tag is set to YES (the default) Doxygen will +generate Latex output. +' defval='1'/> + <option type='string' id='LATEX_OUTPUT' format='dir' docs=' +The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. +If a relative path is entered the value of OUTPUT_DIRECTORY will be +put in front of it. If left blank `latex' will be used as the default path. +' defval='latex' depends='GENERATE_LATEX'/> + <option type='string' id='LATEX_CMD_NAME' format='file' docs=' +The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be +invoked. If left blank `latex' will be used as the default command name. +' defval='latex' depends='GENERATE_LATEX'/> + <option type='string' id='MAKEINDEX_CMD_NAME' format='file' docs=' +The MAKEINDEX_CMD_NAME tag can be used to specify the command name to +generate index for LaTeX. If left blank `makeindex' will be used as the +default command name. +' defval='makeindex' depends='GENERATE_LATEX'/> + <option type='bool' id='COMPACT_LATEX' docs=' +If the COMPACT_LATEX tag is set to YES Doxygen generates more compact +LaTeX documents. This may be useful for small projects and may help to +save some trees in general. +' defval='0' depends='GENERATE_LATEX'/> + <option type='enum' id='PAPER_TYPE' defval='a4wide' docs=' +The PAPER_TYPE tag can be used to set the paper type that is used +by the printer. Possible values are: a4, a4wide, letter, legal and +executive. If left blank a4wide will be used. +' depends='GENERATE_LATEX'> + <value name='a4'/> + <value name='a4wide'/> + <value name='letter'/> + <value name='legal'/> + <value name='executive'/> + </option> + <option type='list' id='EXTRA_PACKAGES' format='string' docs=' +The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX +packages that should be included in the LaTeX output. +' depends='GENERATE_LATEX'> + </option> + <option type='string' id='LATEX_HEADER' format='file' docs=' +The LATEX_HEADER tag can be used to specify a personal LaTeX header for +the generated latex document. The header should contain everything until +the first chapter. If it is left blank doxygen will generate a +standard header. Notice: only use this tag if you know what you are doing! +' defval='' depends='GENERATE_LATEX'/> + <option type='bool' id='PDF_HYPERLINKS' docs=' +If the PDF_HYPERLINKS tag is set to YES, the LaTeX 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. +' defval='1' depends='GENERATE_LATEX'/> + <option type='bool' id='USE_PDFLATEX' docs=' +If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of +plain latex in the generated Makefile. Set this option to YES to get a +higher quality PDF documentation. +' defval='1' depends='GENERATE_LATEX'/> + <option type='bool' id='LATEX_BATCHMODE' docs=' +If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. +command to the generated LaTeX files. This will instruct LaTeX to keep +running if errors occur, instead of asking the user for help. +This option is also used when generating formulas in HTML. +' defval='0' depends='GENERATE_LATEX'/> + <option type='bool' id='LATEX_HIDE_INDICES' docs=' +If LATEX_HIDE_INDICES is set to YES then doxygen will not +include the index chapters (such as File Index, Compound Index, etc.) +in the output. +' defval='0' depends='GENERATE_LATEX'/> + </group> + <group name='RTF' docs='configuration options related to the RTF output'> + <option type='bool' id='GENERATE_RTF' docs=' +If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output +The RTF output is optimized for Word 97 and may not look very pretty with +other RTF readers or editors. +' defval='0'/> + <option type='string' id='RTF_OUTPUT' format='dir' docs=' +The RTF_OUTPUT tag is used to specify where the RTF docs will be put. +If a relative path is entered the value of OUTPUT_DIRECTORY will be +put in front of it. If left blank `rtf' will be used as the default path. +' defval='rtf' depends='GENERATE_RTF'/> + <option type='bool' id='COMPACT_RTF' docs=' +If the COMPACT_RTF tag is set to YES Doxygen generates more compact +RTF documents. This may be useful for small projects and may help to +save some trees in general. +' defval='0' depends='GENERATE_RTF'/> + <option type='bool' id='RTF_HYPERLINKS' docs=' +If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated +will contain hyperlink fields. The RTF file will +contain links (just like the HTML output) instead of page references. +This makes the output suitable for online browsing using WORD or other +programs which support those fields. +Note: wordpad (write) and others do not support links. +' defval='0' depends='GENERATE_RTF'/> + <option type='string' id='RTF_STYLESHEET_FILE' format='file' docs=' +Load stylesheet definitions from file. Syntax is similar to doxygen's +config file, i.e. a series of assignments. You only have to provide +replacements, missing definitions are set to their default value. +' defval='' depends='GENERATE_RTF'/> + <option type='string' id='RTF_EXTENSIONS_FILE' format='file' docs=' +Set optional variables used in the generation of an rtf document. +Syntax is similar to doxygen's config file. +' defval='' depends='GENERATE_RTF'/> + </group> + <group name='Man' docs='configuration options related to the man page output'> + <option type='bool' id='GENERATE_MAN' docs=' +If the GENERATE_MAN tag is set to YES (the default) Doxygen will +generate man pages +' defval='0'/> + <option type='string' id='MAN_OUTPUT' format='dir' docs=' +The MAN_OUTPUT tag is used to specify where the man pages will be put. +If a relative path is entered the value of OUTPUT_DIRECTORY will be +put in front of it. If left blank `man' will be used as the default path. +' defval='man' depends='GENERATE_MAN'/> + <option type='string' id='MAN_EXTENSION' format='string' docs=' +The MAN_EXTENSION tag determines the extension that is added to +the generated man pages (default is the subroutine's section .3) +' defval='.3' depends='GENERATE_MAN'/> + <option type='bool' id='MAN_LINKS' docs=' +If the MAN_LINKS tag is set to 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. The default is NO. +' defval='0' depends='GENERATE_MAN'/> + </group> + <group name='XML' docs='configuration options related to the XML output'> + <option type='bool' id='GENERATE_XML' docs=' +If the GENERATE_XML tag is set to YES Doxygen will +generate an XML file that captures the structure of +the code including all documentation. +' defval='0'/> + <option type='string' id='XML_OUTPUT' format='dir' docs=' +The XML_OUTPUT tag is used to specify where the XML pages will be put. +If a relative path is entered the value of OUTPUT_DIRECTORY will be +put in front of it. If left blank `xml' will be used as the default path. +' defval='xml' depends='GENERATE_XML'/> + <option type='string' id='XML_SCHEMA' format='string' docs=' +The XML_SCHEMA tag can be used to specify an XML schema, +which can be used by a validating XML parser to check the +syntax of the XML files. +' defval='' depends='GENERATE_XML'/> + <option type='string' id='XML_DTD' format='string' docs=' +The XML_DTD tag can be used to specify an XML DTD, +which can be used by a validating XML parser to check the +syntax of the XML files. +' defval='' depends='GENERATE_XML'/> + <option type='bool' id='XML_PROGRAMLISTING' docs=' +If the XML_PROGRAMLISTING tag is set to YES Doxygen will +dump the program listings (including syntax highlighting +and cross-referencing information) to the XML output. Note that +enabling this will significantly increase the size of the XML output. +' defval='1' depends='GENERATE_XML'/> + </group> + <group name='DEF' docs='configuration options for the AutoGen Definitions output'> + <option type='bool' id='GENERATE_AUTOGEN_DEF' docs=' +If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will +generate an AutoGen Definitions (see autogen.sf.net) file +that captures the structure of the code including all +documentation. Note that this feature is still experimental +and incomplete at the moment. +' defval='0'/> + </group> + <group name='PerlMod' docs='configuration options related to the Perl module output'> + <option type='bool' id='GENERATE_PERLMOD' docs=' +If the GENERATE_PERLMOD tag is set to YES Doxygen will +generate a Perl module file that captures the structure of +the code including all documentation. Note that this +feature is still experimental and incomplete at the +moment. +' defval='0'/> + <option type='bool' id='PERLMOD_LATEX' docs=' +If the PERLMOD_LATEX tag is set to YES Doxygen will generate +the necessary Makefile rules, Perl scripts and LaTeX code to be able +to generate PDF and DVI output from the Perl module output. +' defval='0' depends='GENERATE_PERLMOD'/> + <option type='bool' id='PERLMOD_PRETTY' docs=' +If the PERLMOD_PRETTY tag is set to YES the Perl module output will be +nicely formatted so it can be parsed by a human reader. This is useful +if you want to understand what is going on. On the other hand, if this +tag is set to NO the size of the Perl module output will be much smaller +and Perl will parse it just the same. +' defval='1' depends='GENERATE_PERLMOD'/> + <option type='string' id='PERLMOD_MAKEVAR_PREFIX' format='string' docs=' +The names of the make variables in the generated doxyrules.make file +are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. +This is useful so different doxyrules.make files included by the same +Makefile don't overwrite each other's variables.' defval='' depends='GENERATE_PERLMOD'/> + </group> + <group name='Preprocessor' docs='Configuration options related to the preprocessor '> + <option type='bool' id='ENABLE_PREPROCESSING' docs=' +If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will +evaluate all C-preprocessor directives found in the sources and include +files. +' defval='1'/> + <option type='bool' id='MACRO_EXPANSION' docs=' +If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro +names in the source code. If set to NO (the default) only conditional +compilation will be performed. Macro expansion can be done in a controlled +way by setting EXPAND_ONLY_PREDEF to YES. +' defval='0' depends='ENABLE_PREPROCESSING'/> + <option type='bool' id='EXPAND_ONLY_PREDEF' docs=' +If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES +then the macro expansion is limited to the macros specified with the +PREDEFINED and EXPAND_AS_DEFINED tags. +' defval='0' depends='ENABLE_PREPROCESSING'/> + <option type='bool' id='SEARCH_INCLUDES' docs=' +If the SEARCH_INCLUDES tag is set to YES (the default) the includes files +in the INCLUDE_PATH (see below) will be search if a #include is found. +' defval='1' depends='ENABLE_PREPROCESSING'/> + <option type='list' id='INCLUDE_PATH' format='dir' docs=' +The INCLUDE_PATH tag can be used to specify one or more directories that +contain include files that are not input files but should be processed by +the preprocessor. +' depends='ENABLE_PREPROCESSING'> + </option> + <option type='list' id='INCLUDE_FILE_PATTERNS' format='string' docs=' +You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard +patterns (like *.h and *.hpp) to filter out the header-files in the +directories. If left blank, the patterns specified with FILE_PATTERNS will +be used. +' depends='ENABLE_PREPROCESSING'> + </option> + <option type='list' id='PREDEFINED' format='string' docs=' +The PREDEFINED tag can be used to specify one or more macro names that +are defined before the preprocessor is started (similar to the -D option of +gcc). The argument of the tag is a list of macros of the form: name +or name=definition (no spaces). If the definition and the = are +omitted =1 is assumed. To prevent a macro definition from being +undefined via #undef or recursively expanded use the := operator +instead of the = operator. +' depends='ENABLE_PREPROCESSING'> + </option> + <option type='list' id='EXPAND_AS_DEFINED' format='string' docs=' +If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then +this tag can be used to specify a list of macro names that should be expanded. +The macro definition that is found in the sources will be used. +Use the PREDEFINED tag if you want to use a different macro definition. +' depends='ENABLE_PREPROCESSING'> + </option> + <option type='bool' id='SKIP_FUNCTION_MACROS' docs=' +If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then +doxygen's preprocessor will remove all function-like macros that are alone +on a line, have an all uppercase name, and do not end with a semicolon. Such +function macros are typically used for boiler-plate code, and will confuse +the parser if not removed. +' defval='1' depends='ENABLE_PREPROCESSING'/> + </group> + <group name='External' docs='Configuration::additions related to external references '> + <option type='list' id='TAGFILES' format='file' docs=' +The TAGFILES option can be used to specify one or more tagfiles. +Optionally an initial location of the external documentation +can be added for each tagfile. The format of a tag file without +this location is as follows: + TAGFILES = file1 file2 ... +Adding location for the tag files is done as follows: + TAGFILES = file1=loc1 "file2 = loc2" ... +where "loc1" and "loc2" can be relative or absolute paths or +URLs. If a location is present for each tag, the installdox tool +does not have to be run to correct the links. +Note that each tag file must have a unique name +(where the name does NOT include the path) +If a tag file is not located in the directory in which doxygen +is run, you must also specify the path to the tagfile here. +'> + </option> + <option type='string' id='GENERATE_TAGFILE' format='file' docs=' +When a file name is specified after GENERATE_TAGFILE, doxygen will create +a tag file that is based on the input files it reads. +' defval=''/> + <option type='bool' id='ALLEXTERNALS' docs=' +If the ALLEXTERNALS tag is set to YES all external classes will be listed +in the class index. If set to NO only the inherited external classes +will be listed. +' defval='0'/> + <option type='bool' id='EXTERNAL_GROUPS' docs=' +If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed +in the modules index. If set to NO, only the current project's groups will +be listed. +' defval='1'/> + <option type='string' id='PERL_PATH' format='dir' docs=' +The PERL_PATH should be the absolute path and name of the perl script +interpreter (i.e. the result of `which perl'). +' defval='/usr/bin/perl'/> + </group> + <group name='Dot' docs='Configuration options related to the dot tool '> + <option type='bool' id='CLASS_DIAGRAMS' docs=' +If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will +generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base +or super classes. Setting the tag to NO turns the diagrams off. Note that +this option is superseded by the HAVE_DOT option below. This is only a +fallback. It is recommended to install and use dot, since it yields more +powerful graphs. +' defval='1'/> + <option type='string' id='MSCGEN_PATH' format='string' docs=' +You can define message sequence charts within doxygen comments using the \msc +command. Doxygen will then run the mscgen tool (see +http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the +documentation. The MSCGEN_PATH tag allows you to specify the directory where +the mscgen tool resides. If left empty the tool is assumed to be found in the +default search path. +' defval=''/> + <option type='bool' id='HIDE_UNDOC_RELATIONS' docs=' +If set to YES, the inheritance and collaboration graphs will hide +inheritance and usage relations if the target is undocumented +or is not a class. +' defval='1'/> + <option type='bool' id='HAVE_DOT' docs=' +If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is +available from the path. This tool is part of Graphviz, a graph visualization +toolkit from AT&T and Lucent Bell Labs. The other options in this section +have no effect if this option is set to NO (the default) +' defval='0'/> + <option type='string' id='DOT_FONTNAME' format='string' docs=' +By default doxygen will write a font called FreeSans.ttf to the output +directory and reference it in all dot files that doxygen generates. This +font does not include all possible unicode characters however, so when you need +these (or just want a differently looking font) you can specify the font name +using DOT_FONTNAME. You need need to make sure dot is able to find the font, +which can be done by putting it in a standard location or by setting the +DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory +containing the font. +' defval='FreeSans' depends='HAVE_DOT'/> + <option type='int' id='DOT_FONTSIZE' docs=' +The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. +The default size is 10pt. +' minval='4' maxval='24' defval='10' depends='HAVE_DOT'/> + <option type='string' id='DOT_FONTPATH' format='string' docs=' +By default doxygen will tell dot to use the output directory to look for the +FreeSans.ttf font (which doxygen will put there itself). If you specify a +different font using DOT_FONTNAME you can set the path where dot +can find it using this tag. +' defval='' depends='HAVE_DOT'/> + <option type='bool' id='CLASS_GRAPH' docs=' +If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen +will generate a graph for each documented class showing the direct and +indirect inheritance relations. Setting this tag to YES will force the +the CLASS_DIAGRAMS tag to NO. +' defval='1' depends='HAVE_DOT'/> + <option type='bool' id='COLLABORATION_GRAPH' docs=' +If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen +will generate a graph for each documented class showing the direct and +indirect implementation dependencies (inheritance, containment, and +class references variables) of the class with other documented classes. +' defval='1' depends='HAVE_DOT'/> + <option type='bool' id='GROUP_GRAPHS' docs=' +If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen +will generate a graph for groups, showing the direct groups dependencies +' defval='1' depends='HAVE_DOT'/> + <option type='bool' id='UML_LOOK' docs=' +If the UML_LOOK tag is set to YES doxygen will generate inheritance and +collaboration diagrams in a style similar to the OMG's Unified Modeling +Language. +' defval='0' depends='HAVE_DOT'/> + <option type='bool' id='TEMPLATE_RELATIONS' docs=' +If set to YES, the inheritance and collaboration graphs will show the +relations between templates and their instances. +' defval='0' depends='HAVE_DOT'/> + <option type='bool' id='INCLUDE_GRAPH' docs=' +If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT +tags are set to YES then doxygen will generate a graph for each documented +file showing the direct and indirect include dependencies of the file with +other documented files. +' defval='1' depends='HAVE_DOT'/> + <option type='bool' id='INCLUDED_BY_GRAPH' docs=' +If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and +HAVE_DOT tags are set to YES then doxygen will generate a graph for each +documented header file showing the documented files that directly or +indirectly include this file. +' defval='1' depends='HAVE_DOT'/> + <option type='bool' id='CALL_GRAPH' docs=' +If the CALL_GRAPH and HAVE_DOT options are set to YES then +doxygen will generate a call dependency graph for every global function +or class method. Note that enabling this option will significantly increase +the time of a run. So in most cases it will be better to enable call graphs +for selected functions only using the \callgraph command. +' defval='0' depends='HAVE_DOT'/> + <option type='bool' id='CALLER_GRAPH' docs=' +If the CALLER_GRAPH and HAVE_DOT tags are set to YES then +doxygen will generate a caller dependency graph for every global function +or class method. Note that enabling this option will significantly increase +the time of a run. So in most cases it will be better to enable caller +graphs for selected functions only using the \callergraph command. +' defval='0' depends='HAVE_DOT'/> + <option type='bool' id='GRAPHICAL_HIERARCHY' docs=' +If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen +will graphical hierarchy of all classes instead of a textual one. +' defval='1' depends='HAVE_DOT'/> + <option type='bool' id='DIRECTORY_GRAPH' docs=' +If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES +then doxygen will show the dependencies a directory has on other directories +in a graphical way. The dependency relations are determined by the #include +relations between the files in the directories. +' defval='1' depends='HAVE_DOT'/> + <option type='enum' id='DOT_IMAGE_FORMAT' defval='png' docs=' +The DOT_IMAGE_FORMAT tag can be used to set the image format of the images +generated by dot. Possible values are png, jpg, or gif +If left blank png will be used. +' depends='HAVE_DOT'> + <value name='png'/> + <value name='jpg'/> + <value name='gif'/> + </option> + <option type='string' id='DOT_PATH' format='dir' docs=' +The tag DOT_PATH can be used to specify the path where the dot tool can be +found. If left blank, it is assumed the dot tool can be found in the path. +' defval='' depends='HAVE_DOT'/> + <option type='list' id='DOTFILE_DIRS' format='dir' docs=' +The DOTFILE_DIRS tag can be used to specify one or more directories that +contain dot files that are included in the documentation (see the +\dotfile command). +' depends='HAVE_DOT'> + </option> + <option type='int' id='DOT_GRAPH_MAX_NODES' docs=' +The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of +nodes that will be shown in the graph. If the number of nodes in a graph +becomes larger than this value, doxygen will truncate the graph, which is +visualized by representing a node as a red box. Note that doxygen if the +number of direct children of the root node in a graph is already larger than +DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note +that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. +' minval='0' maxval='10000' defval='50' depends='HAVE_DOT'/> + <option type='int' id='MAX_DOT_GRAPH_DEPTH' docs=' +The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the +graphs generated by dot. A depth value of 3 means that only nodes reachable +from the root by following a path via at most 3 edges will be shown. Nodes +that lay further from the root node will be omitted. Note that setting this +option to 1 or 2 may greatly reduce the computation time needed for large +code bases. Also note that the size of a graph can be further restricted by +DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. +' minval='0' maxval='1000' defval='0' depends='HAVE_DOT'/> + <option type='bool' id='DOT_TRANSPARENT' docs=' +Set the DOT_TRANSPARENT tag to YES to generate images with a transparent +background. This is disabled by default, because dot on Windows does not +seem to support this out of the box. Warning: Depending on the platform used, +enabling this option may lead to badly anti-aliased labels on the edges of +a graph (i.e. they become hard to read). +' defval='0' depends='HAVE_DOT'/> + <option type='bool' id='DOT_MULTI_TARGETS' docs=' +Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output +files in one run (i.e. multiple -o and -T options on the command line). This +makes dot run faster, but since only newer versions of dot (>1.8.10) +support this, this feature is disabled by default. +' defval='0' depends='HAVE_DOT'/> + <option type='bool' id='GENERATE_LEGEND' docs=' +If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will +generate a legend page explaining the meaning of the various boxes and +arrows in the dot generated graphs. +' defval='1' depends='HAVE_DOT'/> + <option type='bool' id='DOT_CLEANUP' docs=' +If the DOT_CLEANUP tag is set to YES (the default) Doxygen will +remove the intermediate dot files that are used to generate +the various graphs. +' defval='1' depends='HAVE_DOT'/> + </group> + <group name='Search' docs='Options related to the search engine'> + <option type='bool' id='SEARCHENGINE' docs=' +The SEARCHENGINE tag specifies whether or not a search engine should be +used. If set to NO the values of all tags below this one will be ignored. +' defval='0'/> + <option type='obsolete' id='USE_WINDOWS_ENCODING'/> + <option type='obsolete' id='DETAILS_AT_TOP'/> + <option type='obsolete' id='QTHELP_FILE'/> + <option type='obsolete' id='QTHELP_CONFIG'/> + <option type='obsolete' id='DOXYGEN2QTHELP_LOC'/> + <option type='obsolete' id='MAX_DOT_GRAPH_WIDTH'/> + <option type='obsolete' id='MAX_DOT_GRAPH_HEIGHT'/> + <option type='obsolete' id='CGI_NAME'/> + <option type='obsolete' id='CGI_URL'/> + <option type='obsolete' id='DOC_URL'/> + <option type='obsolete' id='DOC_ABSPATH'/> + <option type='obsolete' id='BIN_ABSPATH'/> + <option type='obsolete' id='EXT_DOC_PATHS'/> + </group> +</doxygenconfig> diff --git a/src/configgen.py b/src/configgen.py new file mode 100755 index 0000000..c58464d --- /dev/null +++ b/src/configgen.py @@ -0,0 +1,137 @@ +# python script to generate configoptions.cpp from config.xml +# +# Copyright (C) 1997-2008 by Dimitri van Heesch. +# +# Permission to use, copy, modify, and distribute this software and its +# documentation under the terms of the GNU General Public License is hereby +# granted. No representations are made about the suitability of this software +# for any purpose. It is provided "as is" without express or implied warranty. +# See the GNU General Public License for more details. +# +# Documents produced by Doxygen are derivative works derived from the +# input used in their production; they are not affected by this license. +# +import xml.dom.minidom +from xml.dom import minidom, Node + +def addValues(var,node): + for n in node.childNodes: + if n.nodeType == Node.ELEMENT_NODE: + name = n.getAttribute('name'); + print " %s->addValue(\"%s\");" % (var,name) + +def parseOption(node): + name = node.getAttribute('id') + type = node.getAttribute('type') + format = node.getAttribute('format') + doc = node.getAttribute('docs') + defval = node.getAttribute('defval') + adefval = node.getAttribute('altdefval') + depends = node.getAttribute('depends') + # replace \ by \\, replace " by \", and ' ' by a newline with end string and start string at next line + docC = doc.strip().replace('\\','\\\\').replace('"','\\"').replace(' ',' \\n"\n "') + print " //----" + if type=='bool': + if len(adefval)>0: + enabled = adefval + else: + enabled = "TRUE" if defval=='1' else "FALSE" + print " cb = cfg->addBool(" + print " \"%s\"," % (name) + print " \"%s\"," % (docC) + print " %s" % (enabled) + print " );" + if depends!='': + print " cb->addDependency(\"%s\");" % (depends) + elif type=='string': + print " cs = cfg->addString(" + print " \"%s\"," % (name) + print " \"%s\"" % (docC) + print " );" + if defval!='': + print " cs->setDefaultValue(\"%s\");" % (defval) + if format=='file': + print " cs->setWidgetType(ConfigString::File);" + elif format=='dir': + print " cs->setWidgetType(ConfigString::Dir);" + if depends!='': + print " cs->addDependency(\"%s\");" % (depends) + elif type=='enum': + print " ce = cfg->addEnum(" + print " \"%s\"," % (name) + print " \"%s\"," % (docC) + print " \"%s\"" % (defval) + print " );" + addValues("ce",node) + if depends!='': + print " ce->addDependency(\"%s\");" % (depends) + elif type=='int': + minval = node.getAttribute('minval') + maxval = node.getAttribute('maxval') + print " ci = cfg->addInt(" + print " \"%s\"," % (name) + print " \"%s\"," % (docC) + print " %s,%s,%s" % (minval,maxval,defval) + print " );" + if depends!='': + print " ci->addDependency(\"%s\");" % (depends) + elif type=='list': + print " cl = cfg->addList(" + print " \"%s\"," % (name) + print " \"%s\"" % (docC) + print " );" + addValues("cl",node) + if depends!='': + print " cl->addDependency(\"%s\");" % (depends) + if format=='file': + print " cl->setWidgetType(ConfigList::File);" + elif format=='dir': + print " cl->setWidgetType(ConfigList::Dir);" + elif format=='filedir': + print " cl->setWidgetType(ConfigList::FileAndDir);" + elif type=='obsolete': + print " cfg->addObsolete(\"%s\");" % (name) + + + + +def parseGroups(node): + name = node.getAttribute('name') + doc = node.getAttribute('docs') + print " //---------------------------------------------------------------------------"; + print " cfg->addInfo(\"%s\",\"%s\");" % (name,doc) + print " //---------------------------------------------------------------------------"; + print + for n in node.childNodes: + if n.nodeType == Node.ELEMENT_NODE: + parseOption(n) + + +def main(): + doc = xml.dom.minidom.parse("config.xml") + elem = doc.documentElement + print "/* WARNING: This file is generated!" + print " * Do not edit this file, but edit config.xml instead and run" + print " * python configgen.py to regenerate this file!" + print " */" + print "" + print "#include \"configoptions.h\"" + print "#include \"config.h\"" + print "#include \"portable.h\"" + print "" + print "void addConfigOptions(Config *cfg)" + print "{" + print " ConfigString *cs;" + print " ConfigEnum *ce;" + print " ConfigList *cl;" + print " ConfigInt *ci;" + print " ConfigBool *cb;" + print "" + for n in elem.childNodes: + if n.nodeType == Node.ELEMENT_NODE: + parseGroups(n) + print "}" + +if __name__ == '__main__': + main() + diff --git a/src/configoptions.cpp b/src/configoptions.cpp index 038046f..4010359 100644 --- a/src/configoptions.cpp +++ b/src/configoptions.cpp @@ -1,61 +1,46 @@ -/****************************************************************************** - * - * - * - * - * Copyright (C) 1997-2008 by Dimitri van Heesch. - * - * Permission to use, copy, modify, and distribute this software and its - * documentation under the terms of the GNU General Public License is hereby - * granted. No representations are made about the suitability of this software - * for any purpose. It is provided "as is" without express or implied warranty. - * See the GNU General Public License for more details. - * - * Documents produced by Doxygen are derivative works derived from the - * input used in their production; they are not affected by this license. - * +/* WARNING: This file is generated! + * Do not edit this file, but edit config.xml instead and run + * python configgen.py to regenerate this file! */ #include "configoptions.h" #include "config.h" #include "portable.h" -#include "lang_cfg.h" void addConfigOptions(Config *cfg) { - ConfigString *cs; ConfigEnum *ce; ConfigList *cl; ConfigInt *ci; ConfigBool *cb; - - // option definitions - //----------------------------------------------------------------------------------------------- + + //--------------------------------------------------------------------------- cfg->addInfo("Project","Project related configuration options"); - //----------------------------------------------------------------------------------------------- - + //--------------------------------------------------------------------------- + + //---- cs = cfg->addString( - "DOXYFILE_ENCODING", - "This tag specifies the encoding used for all characters in the config file \n" - "that follow. The default is UTF-8 which is also the encoding used for all \n" - "text before the first occurrence of this tag. Doxygen uses libiconv (or the \n" - "iconv built into libc) for the transcoding. See \n" - "http://www.gnu.org/software/libiconv for the list of possible encodings.\n" + "DOXYFILE_ENCODING", + "This tag specifies the encoding used for all characters in the config file \n" + "that follow. The default is UTF-8 which is also the encoding used for all \n" + "text before the first occurrence of this tag. Doxygen uses libiconv (or the \n" + "iconv built into libc) for the transcoding. See \n" + "http://www.gnu.org/software/libiconv for the list of possible encodings." ); cs->setDefaultValue("UTF-8"); //---- cs = cfg->addString( "PROJECT_NAME", "The PROJECT_NAME tag is a single word (or a sequence of words surrounded \n" - "by quotes) that should identify the project. " + "by quotes) that should identify the project." ); //---- cs = cfg->addString( "PROJECT_NUMBER", "The PROJECT_NUMBER tag can be used to enter a project or revision number. \n" "This could be handy for archiving the generated documentation or \n" - "if some version control system is used.\n" + "if some version control system is used." ); //---- cs = cfg->addString( @@ -63,19 +48,19 @@ void addConfigOptions(Config *cfg) "The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) \n" "base path where the generated documentation will be put. \n" "If a relative path is entered, it will be relative to the location \n" - "where doxygen was started. If left blank the current directory will be used.\n" - ); + "where doxygen was started. If left blank the current directory will be used." + ); cs->setWidgetType(ConfigString::Dir); //---- cb = cfg->addBool( "CREATE_SUBDIRS", "If the CREATE_SUBDIRS tag is set to YES, then doxygen will create \n" "4096 sub-directories (in 2 levels) under the output directory of each output \n" - "format and will distribute the generated files over these directories. \n" - "Enabling this option can be useful when feeding doxygen a huge amount of \n" - "source files, where putting all generated files in the same directory would \n" - "otherwise cause performance problems for the file system. \n", - FALSE + "format and will distribute the generated files over these directories. \n" + "Enabling this option can be useful when feeding doxygen a huge amount of \n" + "source files, where putting all generated files in the same directory would \n" + "otherwise cause performance problems for the file system.", + FALSE ); //---- ce = cfg->addEnum( @@ -84,1304 +69,1242 @@ void addConfigOptions(Config *cfg) "documentation generated by doxygen is written. Doxygen will use this \n" "information to generate all constant output in the proper language. \n" "The default language is English, other supported languages are: \n" - "Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, \n" - "Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, \n" - "Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), \n" - "Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, \n" - "Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, Slovene, \n" - "Spanish, Swedish, and Ukrainian.\n", - "English" - ); -#ifdef LANG_ZA + "Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, \n" + "Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, \n" + "Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), \n" + "Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, \n" + "Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, Slovene, \n" + "Spanish, Swedish, and Ukrainian.", + "English" + ); ce->addValue("Afrikaans"); -#endif -#ifdef LANG_AR ce->addValue("Arabic"); -#endif -#ifdef LANG_BR ce->addValue("Brazilian"); -#endif -#ifdef LANG_CA ce->addValue("Catalan"); -#endif -#ifdef LANG_CN ce->addValue("Chinese"); -#endif -#ifdef LANG_TW ce->addValue("Chinese-Traditional"); -#endif -#ifdef LANG_HR ce->addValue("Croatian"); -#endif -#ifdef LANG_CZ ce->addValue("Czech"); -#endif -#ifdef LANG_DK ce->addValue("Danish"); -#endif -#ifdef LANG_NL ce->addValue("Dutch"); -#endif ce->addValue("English"); -#ifdef LANG_FI ce->addValue("Finnish"); -#endif -#ifdef LANG_FR ce->addValue("French"); -#endif -#ifdef LANG_DE ce->addValue("German"); -#endif -#ifdef LANG_GR ce->addValue("Greek"); -#endif -#ifdef LANG_HU ce->addValue("Hungarian"); -#endif -#ifdef LANG_IT ce->addValue("Italian"); -#endif -#ifdef LANG_JP ce->addValue("Japanese"); ce->addValue("Japanese-en"); -#endif -#ifdef LANG_KR ce->addValue("Korean"); ce->addValue("Korean-en"); -#endif -#ifdef LANG_LI - ce->addValue("Lithuanian"); -#endif -#ifdef LANG_NO ce->addValue("Norwegian"); -#endif -#ifdef LANG_MK - ce->addValue("Macedonian"); -#endif -#ifdef LANG_FA ce->addValue("Farsi"); ce->addValue("Persian"); -#endif -#ifdef LANG_PL ce->addValue("Polish"); -#endif -#ifdef LANG_PT ce->addValue("Portuguese"); -#endif -#ifdef LANG_RO ce->addValue("Romanian"); -#endif -#ifdef LANG_RU ce->addValue("Russian"); -#endif -#ifdef LANG_SR ce->addValue("Serbian"); -#endif -#ifdef LANG_SC - ce->addValue("Serbian-Cyrilic"); -#endif -#ifdef LANG_SK ce->addValue("Slovak"); -#endif -#ifdef LANG_SI ce->addValue("Slovene"); -#endif -#ifdef LANG_ES ce->addValue("Spanish"); -#endif -#ifdef LANG_SE ce->addValue("Swedish"); -#endif -#ifdef LANG_UA ce->addValue("Ukrainian"); -#endif - -#if 0 - cb = cfg->addBool( - "USE_WINDOWS_ENCODING", - "This tag can be used to specify the encoding used in the generated output. \n" - "The encoding is not always determined by the language that is chosen, \n" - "but also whether or not the output is meant for Windows or non-Windows users. \n" - "In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES \n" - "forces the Windows encoding (this is the default for the Windows binary), \n" - "whereas setting the tag to NO uses a Unix-style encoding (the default for \n" - "all platforms other than Windows).\n", -#if defined(_WIN32) || defined(__CYGWIN__) - TRUE -#else - FALSE -#endif - ); -#endif - //---- - cfg->addObsolete("USE_WINDOWS_ENCODING"); - //---- cb = cfg->addBool( - "BRIEF_MEMBER_DESC", - "If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will \n" - "include brief member descriptions after the members that are listed in \n" - "the file and class documentation (similar to JavaDoc). \n" - "Set to NO to disable this. \n", - TRUE - ); + "BRIEF_MEMBER_DESC", + "If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will \n" + "include brief member descriptions after the members that are listed in \n" + "the file and class documentation (similar to JavaDoc). \n" + "Set to NO to disable this.", + TRUE + ); //---- cb = cfg->addBool( - "REPEAT_BRIEF", - "If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend \n" - "the brief description of a member or function before the detailed description. \n" - "Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the \n" - "brief descriptions will be completely suppressed. \n", - TRUE - ); + "REPEAT_BRIEF", + "If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend \n" + "the brief description of a member or function before the detailed description. \n" + "Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the \n" + "brief descriptions will be completely suppressed.", + TRUE + ); //---- cl = cfg->addList( - "ABBREVIATE_BRIEF", - "This tag implements a quasi-intelligent brief description abbreviator \n" - "that is used to form the text in various listings. Each string \n" - "in this list, if found as the leading text of the brief description, will be \n" - "stripped from the text and the result after processing the whole list, is \n" - "used as the annotated text. Otherwise, the brief description is used as-is. \n" - "If left blank, the following values are used (\"$name\" is automatically \n" - "replaced with the name of the entity): \"The $name class\" \"The $name widget\" \n" - "\"The $name file\" \"is\" \"provides\" \"specifies\" \"contains\" \n" - "\"represents\" \"a\" \"an\" \"the\"\n" - ); - //---- - cb = cfg->addBool( - "ALWAYS_DETAILED_SEC", - "If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then \n" - "Doxygen will generate a detailed section even if there is only a brief \n" - "description. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "INLINE_INHERITED_MEMB", - "If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all \n" - "inherited members of a class in the documentation of that class as if those \n" - "members were ordinary class members. Constructors, destructors and assignment \n" - "operators of the base classes will not be shown. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "FULL_PATH_NAMES", - "If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full \n" - "path before files name in the file list and in the header files. If set \n" - "to NO the shortest path that makes the file name unique will be used. \n", - TRUE - ); + "ABBREVIATE_BRIEF", + "This tag implements a quasi-intelligent brief description abbreviator \n" + "that is used to form the text in various listings. Each string \n" + "in this list, if found as the leading text of the brief description, will be \n" + "stripped from the text and the result after processing the whole list, is \n" + "used as the annotated text. Otherwise, the brief description is used as-is. \n" + "If left blank, the following values are used (\"$name\" is automatically \n" + "replaced with the name of the entity): \"The $name class\" \"The $name widget\" \n" + "\"The $name file\" \"is\" \"provides\" \"specifies\" \"contains\" \n" + "\"represents\" \"a\" \"an\" \"the\"" + ); + cl->addValue("The $name class"); + cl->addValue("The $name widget"); + cl->addValue("The $name file"); + cl->addValue("is"); + cl->addValue("provides"); + cl->addValue("specifies"); + cl->addValue("contains"); + cl->addValue("represents"); + cl->addValue("a"); + cl->addValue("an"); + cl->addValue("the"); + //---- + cb = cfg->addBool( + "ALWAYS_DETAILED_SEC", + "If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then \n" + "Doxygen will generate a detailed section even if there is only a brief \n" + "description.", + FALSE + ); //---- - cl = cfg->addList( - "STRIP_FROM_PATH", - "If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag \n" - "can be used to strip a user-defined part of the path. Stripping is \n" - "only done if one of the specified strings matches the left-hand part of \n" - "the path. The tag can be used to show relative paths in the file list. \n" - "If left blank the directory from which doxygen is run is used as the \n" - "path to strip. \n" - ); + cb = cfg->addBool( + "INLINE_INHERITED_MEMB", + "If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all \n" + "inherited members of a class in the documentation of that class as if those \n" + "members were ordinary class members. Constructors, destructors and assignment \n" + "operators of the base classes will not be shown.", + FALSE + ); //---- + cb = cfg->addBool( + "FULL_PATH_NAMES", + "If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full \n" + "path before files name in the file list and in the header files. If set \n" + "to NO the shortest path that makes the file name unique will be used.", + TRUE + ); + //---- + cl = cfg->addList( + "STRIP_FROM_PATH", + "If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag \n" + "can be used to strip a user-defined part of the path. Stripping is \n" + "only done if one of the specified strings matches the left-hand part of \n" + "the path. The tag can be used to show relative paths in the file list. \n" + "If left blank the directory from which doxygen is run is used as the \n" + "path to strip." + ); + cl->addValue("/Users/dimitri/doxygen/mail/1.5.7/doxywizard/"); cl->addDependency("FULL_PATH_NAMES"); + //---- cl = cfg->addList( - "STRIP_FROM_INC_PATH", - "The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of \n" - "the path mentioned in the documentation of a class, which tells \n" - "the reader which header file to include in order to use a class. \n" - "If left blank only the name of the header file containing the class \n" - "definition is used. Otherwise one should specify the include paths that \n" - "are normally passed to the compiler using the -I flag.\n" - ); - //---- - cb = cfg->addBool( - "SHORT_NAMES", - "If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter \n" - "(but less readable) file names. This can be useful is your file systems \n" - "doesn't support long names like on DOS, Mac, or CD-ROM. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "JAVADOC_AUTOBRIEF", - "If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen \n" - "will interpret the first line (until the first dot) of a JavaDoc-style \n" - "comment as the brief description. If set to NO, the JavaDoc \n" - "comments will behave just like regular Qt-style comments \n" - "(thus requiring an explicit @brief command for a brief description.) \n", - FALSE - ); - //---- - cb = cfg->addBool( - "QT_AUTOBRIEF", - "If the QT_AUTOBRIEF tag is set to YES then Doxygen will \n" - "interpret the first line (until the first dot) of a Qt-style \n" - "comment as the brief description. If set to NO, the comments \n" - "will behave just like regular Qt-style comments (thus requiring \n" - "an explicit \\brief command for a brief description.) \n", - FALSE - ); - //---- - cb = cfg->addBool( - "MULTILINE_CPP_IS_BRIEF", - "The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen \n" - "treat a multi-line C++ special comment block (i.e. a block of //! or /// \n" - "comments) as a brief description. This used to be the default behaviour. \n" - "The new default is to treat a multi-line C++ comment block as a detailed \n" - "description. Set this tag to YES if you prefer the old behaviour instead. \n", - FALSE - ); - //---- - //cb = cfg->addBool( - // "DETAILS_AT_TOP", - // "If the DETAILS_AT_TOP tag is set to YES then Doxygen \n" - // "will output the detailed description near the top, like JavaDoc.\n" - // "If set to NO, the detailed description appears after the member \n" - // "documentation. \n", - // FALSE - // ); - cb = cfg->addBool( - "INHERIT_DOCS", - "If the INHERIT_DOCS tag is set to YES (the default) then an undocumented \n" - "member inherits the documentation from any documented member that it \n" - "re-implements. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "SEPARATE_MEMBER_PAGES", - "If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce \n" - "a new page for each member. If set to NO, the documentation of a member will \n" - "be part of the file/class/namespace that contains it.\n", - FALSE - ); + "STRIP_FROM_INC_PATH", + "The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of \n" + "the path mentioned in the documentation of a class, which tells \n" + "the reader which header file to include in order to use a class. \n" + "If left blank only the name of the header file containing the class \n" + "definition is used. Otherwise one should specify the include paths that \n" + "are normally passed to the compiler using the -I flag." + ); + //---- + cb = cfg->addBool( + "SHORT_NAMES", + "If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter \n" + "(but less readable) file names. This can be useful is your file systems \n" + "doesn't support long names like on DOS, Mac, or CD-ROM.", + FALSE + ); + //---- + cb = cfg->addBool( + "JAVADOC_AUTOBRIEF", + "If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen \n" + "will interpret the first line (until the first dot) of a JavaDoc-style \n" + "comment as the brief description. If set to NO, the JavaDoc \n" + "comments will behave just like regular Qt-style comments \n" + "(thus requiring an explicit @brief command for a brief description.)", + FALSE + ); + //---- + cb = cfg->addBool( + "QT_AUTOBRIEF", + "If the QT_AUTOBRIEF tag is set to YES then Doxygen will \n" + "interpret the first line (until the first dot) of a Qt-style \n" + "comment as the brief description. If set to NO, the comments \n" + "will behave just like regular Qt-style comments (thus requiring \n" + "an explicit \\brief command for a brief description.)", + FALSE + ); + //---- + cb = cfg->addBool( + "MULTILINE_CPP_IS_BRIEF", + "The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen \n" + "treat a multi-line C++ special comment block (i.e. a block of //! or /// \n" + "comments) as a brief description. This used to be the default behaviour. \n" + "The new default is to treat a multi-line C++ comment block as a detailed \n" + "description. Set this tag to YES if you prefer the old behaviour instead.", + FALSE + ); + //---- + cb = cfg->addBool( + "INHERIT_DOCS", + "If the INHERIT_DOCS tag is set to YES (the default) then an undocumented \n" + "member inherits the documentation from any documented member that it \n" + "re-implements.", + TRUE + ); + //---- + cb = cfg->addBool( + "SEPARATE_MEMBER_PAGES", + "If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce \n" + "a new page for each member. If set to NO, the documentation of a member will \n" + "be part of the file/class/namespace that contains it.", + FALSE + ); //---- ci = cfg->addInt( - "TAB_SIZE", - "The TAB_SIZE tag can be used to set the number of spaces in a tab. \n" - "Doxygen uses this value to replace tabs by spaces in code fragments. \n", - 1,16,8 - ); + "TAB_SIZE", + "The TAB_SIZE tag can be used to set the number of spaces in a tab. \n" + "Doxygen uses this value to replace tabs by spaces in code fragments.", + 1,16,8 + ); + //---- + cl = cfg->addList( + "ALIASES", + "This tag can be used to specify a number of aliases that acts \n" + "as commands in the documentation. An alias has the form \"name=value\". \n" + "For example adding \"sideeffect=\\par Side Effects:\\n\" will allow you to \n" + "put the command \\sideeffect (or @sideeffect) in the documentation, which \n" + "will result in a user-defined paragraph with heading \"Side Effects:\". \n" + "You can put \\n's in the value part of an alias to insert newlines." + ); + //---- + cb = cfg->addBool( + "OPTIMIZE_OUTPUT_FOR_C", + "Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C \n" + "sources only. Doxygen will then generate output that is more tailored for C. \n" + "For instance, some of the names that are used will be different. The list \n" + "of all members will be omitted, etc.", + FALSE + ); + //---- + cb = cfg->addBool( + "OPTIMIZE_OUTPUT_JAVA", + "Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java \n" + "sources only. Doxygen will then generate output that is more tailored for \n" + "Java. For instance, namespaces will be presented as packages, qualified \n" + "scopes will look different, etc.", + FALSE + ); + //---- + cb = cfg->addBool( + "OPTIMIZE_FOR_FORTRAN", + "Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran \n" + "sources only. Doxygen will then generate output that is more tailored for \n" + "Fortran.", + FALSE + ); + //---- + cb = cfg->addBool( + "OPTIMIZE_OUTPUT_VHDL", + "Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL \n" + "sources. Doxygen will then generate output that is tailored for \n" + "VHDL.", + FALSE + ); //---- cl = cfg->addList( - "ALIASES", - "This tag can be used to specify a number of aliases that acts \n" - "as commands in the documentation. An alias has the form \"name=value\". \n" - "For example adding \"sideeffect=\\par Side Effects:\\n\" will allow you to \n" - "put the command \\sideeffect (or @sideeffect) in the documentation, which \n" - "will result in a user-defined paragraph with heading \"Side Effects:\". \n" - "You can put \\n's in the value part of an alias to insert newlines. \n" - ); - //---- - cb = cfg->addBool( - "OPTIMIZE_OUTPUT_FOR_C", - "Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C \n" - "sources only. Doxygen will then generate output that is more tailored for C. \n" - "For instance, some of the names that are used will be different. The list \n" - "of all members will be omitted, etc. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "OPTIMIZE_OUTPUT_JAVA", - "Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java \n" - "sources only. Doxygen will then generate output that is more tailored for \n" - "Java. For instance, namespaces will be presented as packages, qualified \n" - "scopes will look different, etc. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "OPTIMIZE_FOR_FORTRAN", - "Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran \n" - "sources only. Doxygen will then generate output that is more tailored for \n" - "Fortran. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "OPTIMIZE_OUTPUT_VHDL", - "Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL \n" - "sources. Doxygen will then generate output that is tailored for \n" - "VHDL. \n", - FALSE - ); - //---- - cl = cfg->addList( "EXTENSION_MAPPING", - "Doxygen selects the parser to use depending on the extension of the files it parses. \n" - "With this tag you can assign which parser to use for a given extension. \n" - "Doxygen has a built-in mapping, but you can override or extend it using this tag. \n" - "The format is ext=language, where ext is a file extension, and language is one of \n" - "the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, \n" - "Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat \n" - ".inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), \n" - "use: inc=Fortran f=C\n" - ); - //---- - cb = cfg->addBool( - "BUILTIN_STL_SUPPORT", - "If you use STL classes (i.e. std::string, std::vector, etc.) but do not want \n" - "to include (a tag file for) the STL sources as input, then you should \n" - "set this tag to YES in order to let doxygen match functions declarations and \n" - "definitions whose arguments contain STL classes (e.g. func(std::string); v.s. \n" - "func(std::string) {}). This also make the inheritance and collaboration \n" - "diagrams that involve STL classes more complete and accurate. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "CPP_CLI_SUPPORT", - "If you use Microsoft's C++/CLI language, you should set this option to YES to\n" - "enable parsing support.\n", - FALSE - ); - //---- - cb = cfg->addBool( - "SIP_SUPPORT", - "Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. \n" - "Doxygen will parse them like normal C++ but will assume all classes use public \n" - "instead of private inheritance when no explicit protection keyword is present. \n", - FALSE - ); - //---- - cb = cfg->addBool( "IDL_PROPERTY_SUPPORT", - "For Microsoft's IDL there are propget and propput attributes to indicate getter \n" - "and setter methods for a property. Setting this option to YES (the default) \n" - "will make doxygen to replace the get and set methods by a property in the \n" - "documentation. This will only work if the methods are indeed getting or \n" - "setting a simple type. If this is not the case, or you want to show the \n" - "methods anyway, you should set this option to NO. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "DISTRIBUTE_GROUP_DOC", - "If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC \n" - "tag is set to YES, then doxygen will reuse the documentation of the first \n" - "member in the group (if any) for the other members of the group. By default \n" - "all members of a group must be documented explicitly.\n", - FALSE - ); - //---- - cb = cfg->addBool( - "SUBGROUPING", - "Set the SUBGROUPING tag to YES (the default) to allow class member groups of \n" - "the same type (for instance a group of public functions) to be put as a \n" - "subgroup of that type (e.g. under the Public Functions section). Set it to \n" - "NO to prevent subgrouping. Alternatively, this can be done per class using \n" - "the \\nosubgrouping command. \n", - TRUE - ); - //---- - cb = cfg->addBool( "TYPEDEF_HIDES_STRUCT", - "When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum \n" - "is documented as struct, union, or enum with the name of the typedef. So \n" - "typedef struct TypeS {} TypeT, will appear in the documentation as a struct \n" - "with name TypeT. When disabled the typedef will appear as a member of a file, \n" - "namespace, or class. And the struct will be named TypeS. This can typically \n" - "be useful for C code in case the coding convention dictates that all compound \n" - "types are typedef'ed and only the typedef is referenced, never the tag name.\n", - FALSE + "EXTENSION_MAPPING", + "Doxygen selects the parser to use depending on the extension of the files it parses. \n" + "With this tag you can assign which parser to use for a given extension. \n" + "Doxygen has a built-in mapping, but you can override or extend it using this tag. \n" + "The format is ext=language, where ext is a file extension, and language is one of \n" + "the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, \n" + "Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat \n" + ".inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), \n" + "use: inc=Fortran f=C" + ); + //---- + cb = cfg->addBool( + "BUILTIN_STL_SUPPORT", + "If you use STL classes (i.e. std::string, std::vector, etc.) but do not want \n" + "to include (a tag file for) the STL sources as input, then you should \n" + "set this tag to YES in order to let doxygen match functions declarations and \n" + "definitions whose arguments contain STL classes (e.g. func(std::string); v.s. \n" + "func(std::string) {}). This also make the inheritance and collaboration \n" + "diagrams that involve STL classes more complete and accurate.", + FALSE + ); + //---- + cb = cfg->addBool( + "CPP_CLI_SUPPORT", + "If you use Microsoft's C++/CLI language, you should set this option to YES to \n" + "enable parsing support.", + FALSE + ); + //---- + cb = cfg->addBool( + "SIP_SUPPORT", + "Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. \n" + "Doxygen will parse them like normal C++ but will assume all classes use public \n" + "instead of private inheritance when no explicit protection keyword is present.", + FALSE + ); + //---- + cb = cfg->addBool( + "IDL_PROPERTY_SUPPORT", + "For Microsoft's IDL there are propget and propput attributes to indicate getter \n" + "and setter methods for a property. Setting this option to YES (the default) \n" + "will make doxygen to replace the get and set methods by a property in the \n" + "documentation. This will only work if the methods are indeed getting or \n" + "setting a simple type. If this is not the case, or you want to show the \n" + "methods anyway, you should set this option to NO.", + TRUE + ); + //---- + cb = cfg->addBool( + "DISTRIBUTE_GROUP_DOC", + "If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC \n" + "tag is set to YES, then doxygen will reuse the documentation of the first \n" + "member in the group (if any) for the other members of the group. By default \n" + "all members of a group must be documented explicitly.", + FALSE + ); + //---- + cb = cfg->addBool( + "SUBGROUPING", + "Set the SUBGROUPING tag to YES (the default) to allow class member groups of \n" + "the same type (for instance a group of public functions) to be put as a \n" + "subgroup of that type (e.g. under the Public Functions section). Set it to \n" + "NO to prevent subgrouping. Alternatively, this can be done per class using \n" + "the \\nosubgrouping command.", + TRUE + ); + //---- + cb = cfg->addBool( + "TYPEDEF_HIDES_STRUCT", + "When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum \n" + "is documented as struct, union, or enum with the name of the typedef. So \n" + "typedef struct TypeS {} TypeT, will appear in the documentation as a struct \n" + "with name TypeT. When disabled the typedef will appear as a member of a file, \n" + "namespace, or class. And the struct will be named TypeS. This can typically \n" + "be useful for C code in case the coding convention dictates that all compound \n" + "types are typedef'ed and only the typedef is referenced, never the tag name.", + FALSE ); //---- ci = cfg->addInt( - "SYMBOL_CACHE_SIZE", - "The SYMBOL_CACHE_SIZE determines the size of the internal cache use to \n" - "determine which symbols to keep in memory and which to flush to disk.\n" - "When the cache is full, less often used symbols will be written to disk.\n" - "For small to medium size projects (<1000 input files) the default value is \n" - "probably good enough. For larger projects a too small cache size can cause \n" - "doxygen to be busy swapping symbols to and from disk most of the time \n" - "causing a significant performance penality. \n" - "If the system has enough physical memory increasing the cache will improve the \n" - "performance by keeping more symbols in memory. Note that the value works on \n" - "a logarithmic scale so increasing the size by one will rougly double the \n" - "memory usage. The cache size is given by this formula: \n" - "2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, \n" - "corresponding to a cache size of 2^16 = 65536 symbols\n", - 0,9,0 - ); - - //----------------------------------------------------------------------------------------------- + "SYMBOL_CACHE_SIZE", + "The SYMBOL_CACHE_SIZE determines the size of the internal cache use to \n" + "determine which symbols to keep in memory and which to flush to disk. \n" + "When the cache is full, less often used symbols will be written to disk. \n" + "For small to medium size projects (<1000 input files) the default value is \n" + "probably good enough. For larger projects a too small cache size can cause \n" + "doxygen to be busy swapping symbols to and from disk most of the time \n" + "causing a significant performance penality. \n" + "If the system has enough physical memory increasing the cache will improve the \n" + "performance by keeping more symbols in memory. Note that the value works on \n" + "a logarithmic scale so increasing the size by one will rougly double the \n" + "memory usage. The cache size is given by this formula: \n" + "2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, \n" + "corresponding to a cache size of 2^16 = 65536 symbols", + 0,9,0 + ); + //--------------------------------------------------------------------------- cfg->addInfo("Build","Build related configuration options"); - //----------------------------------------------------------------------------------------------- - cb = cfg->addBool( - "EXTRACT_ALL", - "If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in \n" - "documentation are documented, even if no documentation was available. \n" - "Private class members and static file members will be hidden unless \n" - "the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES \n", - FALSE - ); - //---- - cb = cfg->addBool( - "EXTRACT_PRIVATE", - "If the EXTRACT_PRIVATE tag is set to YES all private members of a class \n" - "will be included in the documentation. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "EXTRACT_STATIC", - "If the EXTRACT_STATIC tag is set to YES all static members of a file \n" - "will be included in the documentation. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "EXTRACT_LOCAL_CLASSES", - "If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) \n" - "defined locally in source files will be included in the documentation. \n" - "If set to NO only classes defined in header files are included. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "EXTRACT_LOCAL_METHODS", - "This flag is only useful for Objective-C code. When set to YES local \n" - "methods, which are defined in the implementation section but not in \n" - "the interface are included in the documentation. \n" - "If set to NO (the default) only methods in the interface are included. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "EXTRACT_ANON_NSPACES", - "If this flag is set to YES, the members of anonymous namespaces will be \n" - "extracted and appear in the documentation as a namespace called \n" - "'anonymous_namespace{file}', where file will be replaced with the base \n" - "name of the file that contains the anonymous namespace. By default \n" - "anonymous namespace are hidden. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "HIDE_UNDOC_MEMBERS", - "If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all \n" - "undocumented members of documented classes, files or namespaces. \n" - "If set to NO (the default) these members will be included in the \n" - "various overviews, but no documentation section is generated. \n" - "This option has no effect if EXTRACT_ALL is enabled. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "HIDE_UNDOC_CLASSES", - "If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all \n" - "undocumented classes that are normally visible in the class hierarchy. \n" - "If set to NO (the default) these classes will be included in the various \n" - "overviews. This option has no effect if EXTRACT_ALL is enabled. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "HIDE_FRIEND_COMPOUNDS", - "If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all \n" - "friend (class|struct|union) declarations. \n" - "If set to NO (the default) these declarations will be included in the \n" - "documentation. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "HIDE_IN_BODY_DOCS", - "If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any \n" - "documentation blocks found inside the body of a function. \n" - "If set to NO (the default) these blocks will be appended to the \n" - "function's detailed documentation block. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "INTERNAL_DOCS", - "The INTERNAL_DOCS tag determines if documentation \n" - "that is typed after a \\internal command is included. If the tag is set \n" - "to NO (the default) then the documentation will be excluded. \n" - "Set it to YES to include the internal documentation. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "CASE_SENSE_NAMES", - "If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate \n" - "file names in lower-case letters. If set to YES upper-case letters are also \n" - "allowed. This is useful if you have classes or files whose names only differ \n" - "in case and if your file system supports case sensitive file names. Windows \n" - "and Mac users are advised to set this option to NO.\n", - portable_fileSystemIsCaseSensitive() - ); - //---- - cb = cfg->addBool( - "HIDE_SCOPE_NAMES", - "If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen \n" - "will show members with their full class and namespace scopes in the \n" - "documentation. If set to YES the scope will be hidden. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "SHOW_INCLUDE_FILES", - "If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen \n" - "will put a list of the files that are included by a file in the documentation \n" - "of that file. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "INLINE_INFO", - "If the INLINE_INFO tag is set to YES (the default) then a tag [inline] \n" - "is inserted in the documentation for inline members. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "SORT_MEMBER_DOCS", - "If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen \n" - "will sort the (detailed) documentation of file and class members \n" - "alphabetically by member name. If set to NO the members will appear in \n" - "declaration order. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "SORT_BRIEF_DOCS", - "If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the \n" - "brief documentation of file, namespace and class members alphabetically \n" - "by member name. If set to NO (the default) the members will appear in \n" - "declaration order. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "SORT_GROUP_NAMES", - "If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the \n" - "hierarchy of group names into alphabetical order. If set to NO (the default) \n" - "the group names will appear in their defined order. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "SORT_BY_SCOPE_NAME", - "If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be \n" - "sorted by fully-qualified names, including namespaces. If set to \n" - "NO (the default), the class list will be sorted only by class name, \n" - "not including the namespace part. \n" - "Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\n" - "Note: This option applies only to the class list, not to the \n" - "alphabetical list.\n", - FALSE - ); + //--------------------------------------------------------------------------- //---- cb = cfg->addBool( - "GENERATE_TODOLIST", - "The GENERATE_TODOLIST tag can be used to enable (YES) or \n" - "disable (NO) the todo list. This list is created by putting \\todo \n" - "commands in the documentation.\n", - TRUE - ); + "EXTRACT_ALL", + "If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in \n" + "documentation are documented, even if no documentation was available. \n" + "Private class members and static file members will be hidden unless \n" + "the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES", + FALSE + ); + //---- + cb = cfg->addBool( + "EXTRACT_PRIVATE", + "If the EXTRACT_PRIVATE tag is set to YES all private members of a class \n" + "will be included in the documentation.", + FALSE + ); + //---- + cb = cfg->addBool( + "EXTRACT_STATIC", + "If the EXTRACT_STATIC tag is set to YES all static members of a file \n" + "will be included in the documentation.", + FALSE + ); + //---- + cb = cfg->addBool( + "EXTRACT_LOCAL_CLASSES", + "If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) \n" + "defined locally in source files will be included in the documentation. \n" + "If set to NO only classes defined in header files are included.", + TRUE + ); + //---- + cb = cfg->addBool( + "EXTRACT_LOCAL_METHODS", + "This flag is only useful for Objective-C code. When set to YES local \n" + "methods, which are defined in the implementation section but not in \n" + "the interface are included in the documentation. \n" + "If set to NO (the default) only methods in the interface are included.", + FALSE + ); + //---- + cb = cfg->addBool( + "EXTRACT_ANON_NSPACES", + "If this flag is set to YES, the members of anonymous namespaces will be \n" + "extracted and appear in the documentation as a namespace called \n" + "'anonymous_namespace{file}', where file will be replaced with the base \n" + "name of the file that contains the anonymous namespace. By default \n" + "anonymous namespace are hidden.", + FALSE + ); + //---- + cb = cfg->addBool( + "HIDE_UNDOC_MEMBERS", + "If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all \n" + "undocumented members of documented classes, files or namespaces. \n" + "If set to NO (the default) these members will be included in the \n" + "various overviews, but no documentation section is generated. \n" + "This option has no effect if EXTRACT_ALL is enabled.", + FALSE + ); + //---- + cb = cfg->addBool( + "HIDE_UNDOC_CLASSES", + "If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all \n" + "undocumented classes that are normally visible in the class hierarchy. \n" + "If set to NO (the default) these classes will be included in the various \n" + "overviews. This option has no effect if EXTRACT_ALL is enabled.", + FALSE + ); + //---- + cb = cfg->addBool( + "HIDE_FRIEND_COMPOUNDS", + "If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all \n" + "friend (class|struct|union) declarations. \n" + "If set to NO (the default) these declarations will be included in the \n" + "documentation.", + FALSE + ); + //---- + cb = cfg->addBool( + "HIDE_IN_BODY_DOCS", + "If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any \n" + "documentation blocks found inside the body of a function. \n" + "If set to NO (the default) these blocks will be appended to the \n" + "function's detailed documentation block.", + FALSE + ); + //---- + cb = cfg->addBool( + "INTERNAL_DOCS", + "The INTERNAL_DOCS tag determines if documentation \n" + "that is typed after a \\internal command is included. If the tag is set \n" + "to NO (the default) then the documentation will be excluded. \n" + "Set it to YES to include the internal documentation.", + FALSE + ); + //---- + cb = cfg->addBool( + "CASE_SENSE_NAMES", + "If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate \n" + "file names in lower-case letters. If set to YES upper-case letters are also \n" + "allowed. This is useful if you have classes or files whose names only differ \n" + "in case and if your file system supports case sensitive file names. Windows \n" + "and Mac users are advised to set this option to NO.", + portable_fileSystemIsCaseSensitive() + ); //---- cb = cfg->addBool( - "GENERATE_TESTLIST", - "The GENERATE_TESTLIST tag can be used to enable (YES) or \n" - "disable (NO) the test list. This list is created by putting \\test \n" - "commands in the documentation.\n", - TRUE - ); + "HIDE_SCOPE_NAMES", + "If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen \n" + "will show members with their full class and namespace scopes in the \n" + "documentation. If set to YES the scope will be hidden.", + FALSE + ); //---- cb = cfg->addBool( - "GENERATE_BUGLIST", - "The GENERATE_BUGLIST tag can be used to enable (YES) or \n" - "disable (NO) the bug list. This list is created by putting \\bug \n" - "commands in the documentation.\n", - TRUE - ); + "SHOW_INCLUDE_FILES", + "If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen \n" + "will put a list of the files that are included by a file in the documentation \n" + "of that file.", + TRUE + ); + //---- + cb = cfg->addBool( + "INLINE_INFO", + "If the INLINE_INFO tag is set to YES (the default) then a tag [inline] \n" + "is inserted in the documentation for inline members.", + TRUE + ); //---- cb = cfg->addBool( - "GENERATE_DEPRECATEDLIST", - "The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or \n" - "disable (NO) the deprecated list. This list is created by putting \n" - "\\deprecated commands in the documentation.\n", - TRUE - ); + "SORT_MEMBER_DOCS", + "If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen \n" + "will sort the (detailed) documentation of file and class members \n" + "alphabetically by member name. If set to NO the members will appear in \n" + "declaration order.", + TRUE + ); + //---- + cb = cfg->addBool( + "SORT_BRIEF_DOCS", + "If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the \n" + "brief documentation of file, namespace and class members alphabetically \n" + "by member name. If set to NO (the default) the members will appear in \n" + "declaration order.", + FALSE + ); + //---- + cb = cfg->addBool( + "SORT_GROUP_NAMES", + "If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the \n" + "hierarchy of group names into alphabetical order. If set to NO (the default) \n" + "the group names will appear in their defined order.", + FALSE + ); + //---- + cb = cfg->addBool( + "SORT_BY_SCOPE_NAME", + "If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be \n" + "sorted by fully-qualified names, including namespaces. If set to \n" + "NO (the default), the class list will be sorted only by class name, \n" + "not including the namespace part. \n" + "Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. \n" + "Note: This option applies only to the class list, not to the \n" + "alphabetical list.", + FALSE + ); + //---- + cb = cfg->addBool( + "GENERATE_TODOLIST", + "The GENERATE_TODOLIST tag can be used to enable (YES) or \n" + "disable (NO) the todo list. This list is created by putting \\todo \n" + "commands in the documentation.", + TRUE + ); + //---- + cb = cfg->addBool( + "GENERATE_TESTLIST", + "The GENERATE_TESTLIST tag can be used to enable (YES) or \n" + "disable (NO) the test list. This list is created by putting \\test \n" + "commands in the documentation.", + TRUE + ); + //---- + cb = cfg->addBool( + "GENERATE_BUGLIST", + "The GENERATE_BUGLIST tag can be used to enable (YES) or \n" + "disable (NO) the bug list. This list is created by putting \\bug \n" + "commands in the documentation.", + TRUE + ); + //---- + cb = cfg->addBool( + "GENERATE_DEPRECATEDLIST", + "The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or \n" + "disable (NO) the deprecated list. This list is created by putting \n" + "\\deprecated commands in the documentation.", + TRUE + ); //---- cl = cfg->addList( - "ENABLED_SECTIONS", - "The ENABLED_SECTIONS tag can be used to enable conditional \n" - "documentation sections, marked by \\if sectionname ... \\endif. \n" - ); + "ENABLED_SECTIONS", + "The ENABLED_SECTIONS tag can be used to enable conditional \n" + "documentation sections, marked by \\if sectionname ... \\endif." + ); //---- ci = cfg->addInt( - "MAX_INITIALIZER_LINES", - "The MAX_INITIALIZER_LINES tag determines the maximum number of lines \n" - "the initial value of a variable or define consists of for it to appear in \n" - "the documentation. If the initializer consists of more lines than specified \n" - "here it will be hidden. Use a value of 0 to hide initializers completely. \n" - "The appearance of the initializer of individual variables and defines in the \n" - "documentation can be controlled using \\showinitializer or \\hideinitializer \n" - "command in the documentation regardless of this setting. \n", - 0,10000,30 - ); - //---- - cb = cfg->addBool( - "SHOW_USED_FILES", - "Set the SHOW_USED_FILES tag to NO to disable the list of files generated \n" - "at the bottom of the documentation of classes and structs. If set to YES the \n" - "list will mention the files that were used to generate the documentation. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "SHOW_DIRECTORIES", - "If the sources in your project are distributed over multiple directories \n" - "then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy \n" - "in the documentation. The default is NO.\n", - FALSE - ); - //---- - cb = cfg->addBool( - "SHOW_FILES", - "Set the SHOW_FILES tag to NO to disable the generation of the Files page.\n" - "This will remove the Files entry from the Quick Index and from the \n" - "Folder Tree View (if specified). The default is YES.\n", - TRUE - ); - //---- - cb = cfg->addBool( - "SHOW_NAMESPACES", - "Set the SHOW_NAMESPACES tag to NO to disable the generation of the \n" - "Namespaces page. This will remove the Namespaces entry from the Quick Index\n" - "and from the Folder Tree View (if specified). The default is YES.\n", - TRUE - ); - //---- - cs = cfg->addString( "FILE_VERSION_FILTER", - "The FILE_VERSION_FILTER tag can be used to specify a program or script that \n" - "doxygen should invoke to get the current version for each file (typically from \n" - "the version control system). Doxygen will invoke the program by executing (via \n" - "popen()) the command <command> <input-file>, where <command> is the value of \n" - "the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file \n" - "provided by doxygen. Whatever the program writes to standard output \n" - "is used as the file version. See the manual for examples. \n" - ); - cs->setWidgetType(ConfigString::File); + "MAX_INITIALIZER_LINES", + "The MAX_INITIALIZER_LINES tag determines the maximum number of lines \n" + "the initial value of a variable or define consists of for it to appear in \n" + "the documentation. If the initializer consists of more lines than specified \n" + "here it will be hidden. Use a value of 0 to hide initializers completely. \n" + "The appearance of the initializer of individual variables and defines in the \n" + "documentation can be controlled using \\showinitializer or \\hideinitializer \n" + "command in the documentation regardless of this setting.", + 0,10000,30 + ); + //---- + cb = cfg->addBool( + "SHOW_USED_FILES", + "Set the SHOW_USED_FILES tag to NO to disable the list of files generated \n" + "at the bottom of the documentation of classes and structs. If set to YES the \n" + "list will mention the files that were used to generate the documentation.", + TRUE + ); //---- - cs = cfg->addString( "LAYOUT_FILE", - "The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by \n" - "doxygen. The layout file controls the global structure of the generated output files \n" - "in an output format independent way. The create the layout file that represents \n" - "doxygen's defaults, run doxygen with the -l option. You can optionally specify a \n" - "file name after the option, if omitted DoxygenLayout.xml will be used as the name \n" - "of the layout file.\n" - ); + cb = cfg->addBool( + "SHOW_DIRECTORIES", + "If the sources in your project are distributed over multiple directories \n" + "then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy \n" + "in the documentation. The default is NO.", + FALSE + ); + //---- + cb = cfg->addBool( + "SHOW_FILES", + "Set the SHOW_FILES tag to NO to disable the generation of the Files page. \n" + "This will remove the Files entry from the Quick Index and from the \n" + "Folder Tree View (if specified). The default is YES.", + TRUE + ); + //---- + cb = cfg->addBool( + "SHOW_NAMESPACES", + "Set the SHOW_NAMESPACES tag to NO to disable the generation of the \n" + "Namespaces page. \n" + "This will remove the Namespaces entry from the Quick Index \n" + "and from the Folder Tree View (if specified). The default is YES.", + TRUE + ); + //---- + cs = cfg->addString( + "FILE_VERSION_FILTER", + "The FILE_VERSION_FILTER tag can be used to specify a program or script that \n" + "doxygen should invoke to get the current version for each file (typically from \n" + "the version control system). Doxygen will invoke the program by executing (via \n" + "popen()) the command <command> <input-file>, where <command> is the value of \n" + "the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file \n" + "provided by doxygen. Whatever the program writes to standard output \n" + "is used as the file version. See the manual for examples." + ); cs->setWidgetType(ConfigString::File); //---- - cfg->addObsolete("DETAILS_AT_TOP"); - - - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Messages","configuration options related to warning and progress messages"); - //----------------------------------------------------------------------------------------------- + cs = cfg->addString( + "LAYOUT_FILE", + "The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by \n" + "doxygen. The layout file controls the global structure of the generated output files \n" + "in an output format independent way. The create the layout file that represents \n" + "doxygen's defaults, run doxygen with the -l option. You can optionally specify a \n" + "file name after the option, if omitted DoxygenLayout.xml will be used as the name \n" + "of the layout file." + ); + cs->setWidgetType(ConfigString::File); + //--------------------------------------------------------------------------- + cfg->addInfo("Messages","configuration options related to warning and progress messages"); + //--------------------------------------------------------------------------- + //---- + cb = cfg->addBool( + "QUIET", + "The QUIET tag can be used to turn on/off the messages that are generated \n" + "by doxygen. Possible values are YES and NO. If left blank NO is used.", + FALSE + ); + //---- cb = cfg->addBool( - "QUIET", - "The QUIET tag can be used to turn on/off the messages that are generated \n" - "by doxygen. Possible values are YES and NO. If left blank NO is used. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "WARNINGS", - "The WARNINGS tag can be used to turn on/off the warning messages that are \n" - "generated by doxygen. Possible values are YES and NO. If left blank \n" - "NO is used. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "WARN_IF_UNDOCUMENTED", - "If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings \n" - "for undocumented members. If EXTRACT_ALL is set to YES then this flag will \n" - "automatically be disabled. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "WARN_IF_DOC_ERROR", - "If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for \n" - "potential errors in the documentation, such as not documenting some \n" - "parameters in a documented function, or documenting parameters that \n" - "don't exist or using markup commands wrongly. \n", - TRUE - ); - //---- - cb = cfg->addBool( "WARN_NO_PARAMDOC", - "This WARN_NO_PARAMDOC option can be abled to get warnings for \n" - "functions that are documented, but have no documentation for their parameters \n" - "or return value. If set to NO (the default) doxygen will only warn about \n" - "wrong or incomplete parameter documentation, but not about the absence of \n" - "documentation.\n", - FALSE - ); + "WARNINGS", + "The WARNINGS tag can be used to turn on/off the warning messages that are \n" + "generated by doxygen. Possible values are YES and NO. If left blank \n" + "NO is used.", + TRUE + ); + //---- + cb = cfg->addBool( + "WARN_IF_UNDOCUMENTED", + "If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings \n" + "for undocumented members. If EXTRACT_ALL is set to YES then this flag will \n" + "automatically be disabled.", + TRUE + ); + //---- + cb = cfg->addBool( + "WARN_IF_DOC_ERROR", + "If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for \n" + "potential errors in the documentation, such as not documenting some \n" + "parameters in a documented function, or documenting parameters that \n" + "don't exist or using markup commands wrongly.", + TRUE + ); + //---- + cb = cfg->addBool( + "WARN_NO_PARAMDOC", + "This WARN_NO_PARAMDOC option can be abled to get warnings for \n" + "functions that are documented, but have no documentation for their parameters \n" + "or return value. If set to NO (the default) doxygen will only warn about \n" + "wrong or incomplete parameter documentation, but not about the absence of \n" + "documentation.", + FALSE + ); //---- cs = cfg->addString( - "WARN_FORMAT", - "The WARN_FORMAT tag determines the format of the warning messages that \n" - "doxygen can produce. The string should contain the $file, $line, and $text \n" - "tags, which will be replaced by the file and line number from which the \n" - "warning originated and the warning text. Optionally the format may contain \n" - "$version, which will be replaced by the version of the file (if it could \n" - "be obtained via FILE_VERSION_FILTER)\n" - ); + "WARN_FORMAT", + "The WARN_FORMAT tag determines the format of the warning messages that \n" + "doxygen can produce. The string should contain the $file, $line, and $text \n" + "tags, which will be replaced by the file and line number from which the \n" + "warning originated and the warning text. Optionally the format may contain \n" + "$version, which will be replaced by the version of the file (if it could \n" + "be obtained via FILE_VERSION_FILTER)" + ); cs->setDefaultValue("$file:$line: $text"); //---- cs = cfg->addString( - "WARN_LOGFILE", - "The WARN_LOGFILE tag can be used to specify a file to which warning \n" - "and error messages should be written. If left blank the output is written \n" - "to stderr. \n" - ); + "WARN_LOGFILE", + "The WARN_LOGFILE tag can be used to specify a file to which warning \n" + "and error messages should be written. If left blank the output is written \n" + "to stderr." + ); cs->setWidgetType(ConfigString::File); - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Input","configuration options related to the input files"); - //----------------------------------------------------------------------------------------------- + //--------------------------------------------------------------------------- + cfg->addInfo("Input","configuration options related to the input files"); + //--------------------------------------------------------------------------- + + //---- cl = cfg->addList( - "INPUT", - "The INPUT tag can be used to specify the files and/or directories that contain \n" - "documented source files. You may enter file names like \"myfile.cpp\" or \n" - "directories like \"/usr/src/myproject\". Separate the files or directories \n" - "with spaces. \n" - ); + "INPUT", + "The INPUT tag can be used to specify the files and/or directories that contain \n" + "documented source files. You may enter file names like \"myfile.cpp\" or \n" + "directories like \"/usr/src/myproject\". Separate the files or directories \n" + "with spaces." + ); + cl->addValue("/Users/dimitri/doxygen/mail/1.5.7/doxywizard"); cl->setWidgetType(ConfigList::FileAndDir); //---- - cs = cfg->addString( "INPUT_ENCODING", - "This tag can be used to specify the character encoding of the source files \n" - "that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is \n" - "also the default input encoding. Doxygen uses libiconv (or the iconv built \n" - "into libc) for the transcoding. See http://www.gnu.org/software/libiconv for \n" - "the list of possible encodings.\n" + cs = cfg->addString( + "INPUT_ENCODING", + "This tag can be used to specify the character encoding of the source files \n" + "that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is \n" + "also the default input encoding. Doxygen uses libiconv (or the iconv built \n" + "into libc) for the transcoding. See http://www.gnu.org/software/libiconv for \n" + "the list of possible encodings." ); cs->setDefaultValue("UTF-8"); //---- cl = cfg->addList( - "FILE_PATTERNS", - "If the value of the INPUT tag contains directories, you can use the \n" - "FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \n" - "and *.h) to filter out the source-files in the directories. If left \n" - "blank the following patterns are tested: \n" - "*.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx \n" - "*.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90\n" - ); - //---- - cb = cfg->addBool( - "RECURSIVE", - "The RECURSIVE tag can be used to turn specify whether or not subdirectories \n" - "should be searched for input files as well. Possible values are YES and NO. \n" - "If left blank NO is used. \n", - FALSE - ); + "FILE_PATTERNS", + "If the value of the INPUT tag contains directories, you can use the \n" + "FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \n" + "and *.h) to filter out the source-files in the directories. If left \n" + "blank the following patterns are tested: \n" + "*.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx \n" + "*.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90" + ); + cl->addValue("*.c"); + cl->addValue("*.cc"); + cl->addValue("*.cxx"); + cl->addValue("*.cpp"); + cl->addValue("*.c++"); + cl->addValue("*.d"); + cl->addValue("*.java"); + cl->addValue("*.ii"); + cl->addValue("*.ixx"); + cl->addValue("*.ipp"); + cl->addValue("*.i++"); + cl->addValue("*.inl"); + cl->addValue("*.h"); + cl->addValue("*.hh"); + cl->addValue("*.hxx"); + cl->addValue("*.hpp"); + cl->addValue("*.h++"); + cl->addValue("*.idl"); + cl->addValue("*.odl"); + cl->addValue("*.cs"); + cl->addValue("*.php"); + cl->addValue("*.php3"); + cl->addValue("*.inc"); + cl->addValue("*.m"); + cl->addValue("*.mm"); + cl->addValue("*.dox"); + cl->addValue("*.py"); + cl->addValue("*.f90"); + cl->addValue("*.f"); + cl->addValue("*.vhd"); + cl->addValue("*.vhdl"); + //---- + cb = cfg->addBool( + "RECURSIVE", + "The RECURSIVE tag can be used to turn specify whether or not subdirectories \n" + "should be searched for input files as well. Possible values are YES and NO. \n" + "If left blank NO is used.", + FALSE + ); //---- cl = cfg->addList( - "EXCLUDE", - "The EXCLUDE tag can be used to specify files and/or directories that should \n" - "excluded from the INPUT source files. This way you can easily exclude a \n" - "subdirectory from a directory tree whose root is specified with the INPUT tag. \n" - ); - //---- - cb = cfg->addBool( - "EXCLUDE_SYMLINKS", - "The EXCLUDE_SYMLINKS tag can be used select whether or not files or \n" - "directories that are symbolic links (a Unix filesystem feature) are excluded \n" - "from the input. \n", - FALSE - ); + "EXCLUDE", + "The EXCLUDE tag can be used to specify files and/or directories that should \n" + "excluded from the INPUT source files. This way you can easily exclude a \n" + "subdirectory from a directory tree whose root is specified with the INPUT tag." + ); cl->setWidgetType(ConfigList::FileAndDir); //---- + cb = cfg->addBool( + "EXCLUDE_SYMLINKS", + "The EXCLUDE_SYMLINKS tag can be used select whether or not files or \n" + "directories that are symbolic links (a Unix filesystem feature) are excluded \n" + "from the input.", + FALSE + ); + //---- cl = cfg->addList( - "EXCLUDE_PATTERNS", - "If the value of the INPUT tag contains directories, you can use the \n" - "EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude \n" - "certain files from those directories. Note that the wildcards are matched \n" - "against the file with absolute path, so to exclude all test directories \n" - "for example use the pattern */test/* \n" - ); + "EXCLUDE_PATTERNS", + "If the value of the INPUT tag contains directories, you can use the \n" + "EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude \n" + "certain files from those directories. Note that the wildcards are matched \n" + "against the file with absolute path, so to exclude all test directories \n" + "for example use the pattern */test/*" + ); //---- cl = cfg->addList( - "EXCLUDE_SYMBOLS", - "The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names \n" - "(namespaces, classes, functions, etc.) that should be excluded from the \n" - "output. The symbol name can be a fully qualified name, a word, or if the \n" - "wildcard * is used, a substring. Examples: ANamespace, AClass, \n" - "AClass::ANamespace, ANamespace::*Test \n" - ); + "EXCLUDE_SYMBOLS", + "The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names \n" + "(namespaces, classes, functions, etc.) that should be excluded from the \n" + "output. The symbol name can be a fully qualified name, a word, or if the \n" + "wildcard * is used, a substring. Examples: ANamespace, AClass, \n" + "AClass::ANamespace, ANamespace::*Test" + ); //---- cl = cfg->addList( - "EXAMPLE_PATH", - "The EXAMPLE_PATH tag can be used to specify one or more files or \n" - "directories that contain example code fragments that are included (see \n" - "the \\include command). \n" - ); + "EXAMPLE_PATH", + "The EXAMPLE_PATH tag can be used to specify one or more files or \n" + "directories that contain example code fragments that are included (see \n" + "the \\include command)." + ); cl->setWidgetType(ConfigList::Dir); //---- cl = cfg->addList( - "EXAMPLE_PATTERNS", - "If the value of the EXAMPLE_PATH tag contains directories, you can use the \n" - "EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \n" - "and *.h) to filter out the source-files in the directories. If left \n" - "blank all files are included. \n" - ); - //---- - cb = cfg->addBool( - "EXAMPLE_RECURSIVE", - "If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be \n" - "searched for input files to be used with the \\include or \\dontinclude \n" - "commands irrespective of the value of the RECURSIVE tag. \n" - "Possible values are YES and NO. If left blank NO is used. \n", - FALSE - ); + "EXAMPLE_PATTERNS", + "If the value of the EXAMPLE_PATH tag contains directories, you can use the \n" + "EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp \n" + "and *.h) to filter out the source-files in the directories. If left \n" + "blank all files are included." + ); + cl->addValue("*"); + //---- + cb = cfg->addBool( + "EXAMPLE_RECURSIVE", + "If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be \n" + "searched for input files to be used with the \\include or \\dontinclude \n" + "commands irrespective of the value of the RECURSIVE tag. \n" + "Possible values are YES and NO. If left blank NO is used.", + FALSE + ); //---- cl = cfg->addList( - "IMAGE_PATH", - "The IMAGE_PATH tag can be used to specify one or more files or \n" - "directories that contain image that are included in the documentation (see \n" - "the \\image command). \n" - ); + "IMAGE_PATH", + "The IMAGE_PATH tag can be used to specify one or more files or \n" + "directories that contain image that are included in the documentation (see \n" + "the \\image command)." + ); cl->setWidgetType(ConfigList::Dir); //---- cs = cfg->addString( - "INPUT_FILTER", - "The INPUT_FILTER tag can be used to specify a program that doxygen should \n" - "invoke to filter for each input file. Doxygen will invoke the filter program \n" - "by executing (via popen()) the command <filter> <input-file>, where <filter> \n" - "is the value of the INPUT_FILTER tag, and <input-file> is the name of an \n" - "input file. Doxygen will then use the output that the filter program writes \n" - "to standard output. If FILTER_PATTERNS is specified, this tag will be \n" - "ignored. \n" - ); + "INPUT_FILTER", + "The INPUT_FILTER tag can be used to specify a program that doxygen should \n" + "invoke to filter for each input file. Doxygen will invoke the filter program \n" + "by executing (via popen()) the command <filter> <input-file>, where <filter> \n" + "is the value of the INPUT_FILTER tag, and <input-file> is the name of an \n" + "input file. Doxygen will then use the output that the filter program writes \n" + "to standard output. \n" + "If FILTER_PATTERNS is specified, this tag will be \n" + "ignored." + ); cs->setWidgetType(ConfigString::File); //---- cl = cfg->addList( - "FILTER_PATTERNS", - "The FILTER_PATTERNS tag can be used to specify filters on a per file pattern \n" - "basis. Doxygen will compare the file name with each pattern and apply the \n" - "filter if there is a match. The filters are a list of the form: \n" - "pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further \n" - "info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER \n" - "is applied to all files. \n" - ); + "FILTER_PATTERNS", + "The FILTER_PATTERNS tag can be used to specify filters on a per file pattern \n" + "basis. \n" + "Doxygen will compare the file name with each pattern and apply the \n" + "filter if there is a match. \n" + "The filters are a list of the form: \n" + "pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further \n" + "info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER \n" + "is applied to all files." + ); cl->setWidgetType(ConfigList::File); //---- cb = cfg->addBool( - "FILTER_SOURCE_FILES", - "If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using \n" - "INPUT_FILTER) will be used to filter the input files when producing source \n" - "files to browse (i.e. when SOURCE_BROWSER is set to YES). \n", - FALSE - ); - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Source Browser","configuration options related to source browsing"); - //----------------------------------------------------------------------------------------------- - cb = cfg->addBool( - "SOURCE_BROWSER", - "If the SOURCE_BROWSER tag is set to YES then a list of source files will \n" - "be generated. Documented entities will be cross-referenced with these sources. \n" - "Note: To get rid of all source code in the generated output, make sure also \n" - "VERBATIM_HEADERS is set to NO. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "INLINE_SOURCES", - "Setting the INLINE_SOURCES tag to YES will include the body \n" - "of functions and classes directly in the documentation. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "STRIP_CODE_COMMENTS", - "Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct \n" - "doxygen to hide any special comment blocks from generated source code \n" - "fragments. Normal C and C++ comments will always remain visible. \n", - TRUE - ); - //---- - cb = cfg->addBool( "REFERENCED_BY_RELATION", - "If the REFERENCED_BY_RELATION tag is set to YES \n" - "then for each documented function all documented \n" - "functions referencing it will be listed. \n", - FALSE - ); - //---- - cb = cfg->addBool( "REFERENCES_RELATION", - "If the REFERENCES_RELATION tag is set to YES \n" - "then for each documented function all documented entities \n" - "called/used by that function will be listed. \n", - FALSE - ); - //---- - cb = cfg->addBool( "REFERENCES_LINK_SOURCE", - "If the REFERENCES_LINK_SOURCE tag is set to YES (the default)\n" - "and SOURCE_BROWSER tag is set to YES, then the hyperlinks from\n" - "functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will\n" - "link to the source code. Otherwise they will link to the documentstion.\n", - TRUE - ); - //---- - cb = cfg->addBool( - "USE_HTAGS", - "If the USE_HTAGS tag is set to YES then the references to source code \n" - "will point to the HTML generated by the htags(1) tool instead of doxygen \n" - "built-in source browser. The htags tool is part of GNU's global source \n" - "tagging system (see http://www.gnu.org/software/global/global.html). You \n" - "will need version 4.8.6 or higher. \n", - FALSE - ); + "FILTER_SOURCE_FILES", + "If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using \n" + "INPUT_FILTER) will be used to filter the input files when producing source \n" + "files to browse (i.e. when SOURCE_BROWSER is set to YES).", + FALSE + ); + //--------------------------------------------------------------------------- + cfg->addInfo("Source Browser","configuration options related to source browsing"); + //--------------------------------------------------------------------------- + + //---- + cb = cfg->addBool( + "SOURCE_BROWSER", + "If the SOURCE_BROWSER tag is set to YES then a list of source files will \n" + "be generated. Documented entities will be cross-referenced with these sources. \n" + "Note: To get rid of all source code in the generated output, make sure also \n" + "VERBATIM_HEADERS is set to NO.", + FALSE + ); + //---- + cb = cfg->addBool( + "INLINE_SOURCES", + "Setting the INLINE_SOURCES tag to YES will include the body \n" + "of functions and classes directly in the documentation.", + FALSE + ); + //---- + cb = cfg->addBool( + "STRIP_CODE_COMMENTS", + "Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct \n" + "doxygen to hide any special comment blocks from generated source code \n" + "fragments. Normal C and C++ comments will always remain visible.", + TRUE + ); + //---- + cb = cfg->addBool( + "REFERENCED_BY_RELATION", + "If the REFERENCED_BY_RELATION tag is set to YES \n" + "then for each documented function all documented \n" + "functions referencing it will be listed.", + FALSE + ); + //---- + cb = cfg->addBool( + "REFERENCES_RELATION", + "If the REFERENCES_RELATION tag is set to YES \n" + "then for each documented function all documented entities \n" + "called/used by that function will be listed.", + FALSE + ); + //---- + cb = cfg->addBool( + "REFERENCES_LINK_SOURCE", + "If the REFERENCES_LINK_SOURCE tag is set to YES (the default) \n" + "and SOURCE_BROWSER tag is set to YES, then the hyperlinks from \n" + "functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will \n" + "link to the source code. \n" + "Otherwise they will link to the documentation.", + TRUE + ); + //---- + cb = cfg->addBool( + "USE_HTAGS", + "If the USE_HTAGS tag is set to YES then the references to source code \n" + "will point to the HTML generated by the htags(1) tool instead of doxygen \n" + "built-in source browser. The htags tool is part of GNU's global source \n" + "tagging system (see http://www.gnu.org/software/global/global.html). You \n" + "will need version 4.8.6 or higher.", + FALSE + ); cb->addDependency("SOURCE_BROWSER"); //---- cb = cfg->addBool( - "VERBATIM_HEADERS", - "If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen \n" - "will generate a verbatim copy of the header file for each class for \n" - "which an include is specified. Set to NO to disable this. \n", - TRUE - ); - - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Index","configuration options related to the alphabetical class index"); - //----------------------------------------------------------------------------------------------- - - cb = cfg->addBool( - "ALPHABETICAL_INDEX", - "If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index \n" - "of all compounds will be generated. Enable this if the project \n" - "contains a lot of classes, structs, unions or interfaces. \n", - FALSE - ); + "VERBATIM_HEADERS", + "If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen \n" + "will generate a verbatim copy of the header file for each class for \n" + "which an include is specified. Set to NO to disable this.", + TRUE + ); + //--------------------------------------------------------------------------- + cfg->addInfo("Index","configuration options related to the alphabetical class index"); + //--------------------------------------------------------------------------- + + //---- + cb = cfg->addBool( + "ALPHABETICAL_INDEX", + "If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index \n" + "of all compounds will be generated. Enable this if the project \n" + "contains a lot of classes, structs, unions or interfaces.", + FALSE + ); //---- ci = cfg->addInt( - "COLS_IN_ALPHA_INDEX", - "If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then \n" - "the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns \n" - "in which this list will be split (can be a number in the range [1..20]) \n", - 1,20,5 + "COLS_IN_ALPHA_INDEX", + "If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then \n" + "the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns \n" + "in which this list will be split (can be a number in the range [1..20])", + 1,20,5 ); //---- cl = cfg->addList( - "IGNORE_PREFIX", - "In case all classes in a project start with a common prefix, all \n" - "classes will be put under the same header in the alphabetical index. \n" - "The IGNORE_PREFIX tag can be used to specify one or more prefixes that \n" - "should be ignored while generating the index headers. \n" - ); - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "HTML","configuration options related to the HTML output"); - //----------------------------------------------------------------------------------------------- - cb = cfg->addBool( - "GENERATE_HTML", - "If the GENERATE_HTML tag is set to YES (the default) Doxygen will \n" - "generate HTML output. \n", - TRUE - ); + "IGNORE_PREFIX", + "In case all classes in a project start with a common prefix, all \n" + "classes will be put under the same header in the alphabetical index. \n" + "The IGNORE_PREFIX tag can be used to specify one or more prefixes that \n" + "should be ignored while generating the index headers." + ); + //--------------------------------------------------------------------------- + cfg->addInfo("HTML","configuration options related to the HTML output"); + //--------------------------------------------------------------------------- + + //---- + cb = cfg->addBool( + "GENERATE_HTML", + "If the GENERATE_HTML tag is set to YES (the default) Doxygen will \n" + "generate HTML output.", + TRUE + ); //---- cs = cfg->addString( - "HTML_OUTPUT", - "The HTML_OUTPUT tag is used to specify where the HTML docs will be put. \n" - "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" - "put in front of it. If left blank `html' will be used as the default path. \n" - ); + "HTML_OUTPUT", + "The HTML_OUTPUT tag is used to specify where the HTML docs will be put. \n" + "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" + "put in front of it. If left blank `html' will be used as the default path." + ); cs->setDefaultValue("html"); cs->setWidgetType(ConfigString::Dir); cs->addDependency("GENERATE_HTML"); //---- cs = cfg->addString( - "HTML_FILE_EXTENSION", - "The HTML_FILE_EXTENSION tag can be used to specify the file extension for \n" - "each generated HTML page (for example: .htm,.php,.asp). If it is left blank \n" - "doxygen will generate files with .html extension.\n" - ); + "HTML_FILE_EXTENSION", + "The HTML_FILE_EXTENSION tag can be used to specify the file extension for \n" + "each generated HTML page (for example: .htm,.php,.asp). If it is left blank \n" + "doxygen will generate files with .html extension." + ); cs->setDefaultValue(".html"); cs->addDependency("GENERATE_HTML"); //---- cs = cfg->addString( - "HTML_HEADER", - "The HTML_HEADER tag can be used to specify a personal HTML header for \n" - "each generated HTML page. If it is left blank doxygen will generate a \n" - "standard header.\n" - ); + "HTML_HEADER", + "The HTML_HEADER tag can be used to specify a personal HTML header for \n" + "each generated HTML page. If it is left blank doxygen will generate a \n" + "standard header." + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_HTML"); //---- cs = cfg->addString( - "HTML_FOOTER", - "The HTML_FOOTER tag can be used to specify a personal HTML footer for \n" - "each generated HTML page. If it is left blank doxygen will generate a \n" - "standard footer.\n" - ); + "HTML_FOOTER", + "The HTML_FOOTER tag can be used to specify a personal HTML footer for \n" + "each generated HTML page. If it is left blank doxygen will generate a \n" + "standard footer." + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_HTML"); //---- cs = cfg->addString( - "HTML_STYLESHEET", - "The HTML_STYLESHEET tag can be used to specify a user-defined cascading \n" - "style sheet that is used by each HTML page. It can be used to \n" - "fine-tune the look of the HTML output. If the tag is left blank doxygen \n" - "will generate a default style sheet. Note that doxygen will try to copy \n" - "the style sheet file to the HTML output directory, so don't put your own \n" - "stylesheet in the HTML output directory as well, or it will be erased! \n" - ); + "HTML_STYLESHEET", + "The HTML_STYLESHEET tag can be used to specify a user-defined cascading \n" + "style sheet that is used by each HTML page. It can be used to \n" + "fine-tune the look of the HTML output. If the tag is left blank doxygen \n" + "will generate a default style sheet. Note that doxygen will try to copy \n" + "the style sheet file to the HTML output directory, so don't put your own \n" + "stylesheet in the HTML output directory as well, or it will be erased!" + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_HTML"); //---- - cb = cfg->addBool( - "HTML_ALIGN_MEMBERS", - "If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, \n" - "files or namespaces will be aligned in HTML using tables. If set to \n" - "NO a bullet list will be used. \n", - TRUE - ); + cb = cfg->addBool( + "HTML_ALIGN_MEMBERS", + "If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, \n" + "files or namespaces will be aligned in HTML using tables. If set to \n" + "NO a bullet list will be used.", + TRUE + ); cb->addDependency("GENERATE_HTML"); //---- cb = cfg->addBool( - "HTML_DYNAMIC_SECTIONS", - "If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML \n" - "documentation will contain sections that can be hidden and shown after the \n" - "page has loaded. For this to work a browser that supports \n" - "JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox \n" - "Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). \n", - FALSE - ); + "HTML_DYNAMIC_SECTIONS", + "If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML \n" + "documentation will contain sections that can be hidden and shown after the \n" + "page has loaded. For this to work a browser that supports \n" + "JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox \n" + "Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).", + FALSE + ); cb->addDependency("GENERATE_HTML"); - - ///////////////////////////////////////////////////////// - // Docsets ////////////////////////////////////////////// - ///////////////////////////////////////////////////////// - - cb = cfg->addBool( "GENERATE_DOCSET", - "If the GENERATE_DOCSET tag is set to YES, additional index files \n" - "will be generated that can be used as input for Apple's Xcode 3 \n" - "integrated development environment, introduced with OSX 10.5 (Leopard). \n" - "To create a documentation set, doxygen will generate a Makefile in the \n" - "HTML output directory. Running make will produce the docset in that \n" - "directory and running \"make install\" will install the docset in \n" - "~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find \n" - "it at startup. \n" - "See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html " - "for more information. \n", - FALSE - ); + //---- + cb = cfg->addBool( + "GENERATE_DOCSET", + "If the GENERATE_DOCSET tag is set to YES, additional index files \n" + "will be generated that can be used as input for Apple's Xcode 3 \n" + "integrated development environment, introduced with OSX 10.5 (Leopard). \n" + "To create a documentation set, doxygen will generate a Makefile in the \n" + "HTML output directory. Running make will produce the docset in that \n" + "directory and running \"make install\" will install the docset in \n" + "~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find \n" + "it at startup. \n" + "See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.", + FALSE + ); cb->addDependency("GENERATE_HTML"); //---- cs = cfg->addString( - "DOCSET_FEEDNAME", - "When GENERATE_DOCSET tag is set to YES, this tag determines the name of the \n" - "feed. A documentation feed provides an umbrella under which multiple \n" - "documentation sets from a single provider (such as a company or product suite) \n" - "can be grouped. \n" + "DOCSET_FEEDNAME", + "When GENERATE_DOCSET tag is set to YES, this tag determines the name of the \n" + "feed. A documentation feed provides an umbrella under which multiple \n" + "documentation sets from a single provider (such as a company or product suite) \n" + "can be grouped." ); cs->setDefaultValue("Doxygen generated docs"); cs->addDependency("GENERATE_DOCSET"); //---- cs = cfg->addString( - "DOCSET_BUNDLE_ID", - "When GENERATE_DOCSET tag is set to YES, this tag specifies a string that \n" - "should uniquely identify the documentation set bundle. This should be a \n" - "reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen \n" - "will append .docset to the name. \n" - ); + "DOCSET_BUNDLE_ID", + "When GENERATE_DOCSET tag is set to YES, this tag specifies a string that \n" + "should uniquely identify the documentation set bundle. This should be a \n" + "reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen \n" + "will append .docset to the name." + ); cs->setDefaultValue("org.doxygen.Project"); cs->addDependency("GENERATE_DOCSET"); - - ///////////////////////////////////////////////////////// - // HTMLHELP ///////////////////////////////////////////// - ///////////////////////////////////////////////////////// - + //---- cb = cfg->addBool( - "GENERATE_HTMLHELP", - "If the GENERATE_HTMLHELP tag is set to YES, additional index files \n" - "will be generated that can be used as input for tools like the \n" - "Microsoft HTML help workshop to generate a compiled HTML help file (.chm) \n" - "of the generated HTML documentation. \n", - FALSE - ); + "GENERATE_HTMLHELP", + "If the GENERATE_HTMLHELP tag is set to YES, additional index files \n" + "will be generated that can be used as input for tools like the \n" + "Microsoft HTML help workshop to generate a compiled HTML help file (.chm) \n" + "of the generated HTML documentation.", + FALSE + ); cb->addDependency("GENERATE_HTML"); //---- cs = cfg->addString( - "CHM_FILE", - "If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can \n" - "be used to specify the file name of the resulting .chm file. You \n" - "can add a path in front of the file if the result should not be \n" - "written to the html output directory. \n" - ); + "CHM_FILE", + "If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can \n" + "be used to specify the file name of the resulting .chm file. You \n" + "can add a path in front of the file if the result should not be \n" + "written to the html output directory." + ); cs->setWidgetType(ConfigString::File); - cs->addDependency("GENERATE_HTML"); + cs->addDependency("GENERATE_HTMLHELP"); //---- cs = cfg->addString( - "HHC_LOCATION", - "If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can \n" - "be used to specify the location (absolute path including file name) of \n" - "the HTML help compiler (hhc.exe). If non-empty doxygen will try to run \n" - "the HTML help compiler on the generated index.hhp.\n" - ); + "HHC_LOCATION", + "If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can \n" + "be used to specify the location (absolute path including file name) of \n" + "the HTML help compiler (hhc.exe). If non-empty doxygen will try to run \n" + "the HTML help compiler on the generated index.hhp." + ); cs->setWidgetType(ConfigString::File); - cs->addDependency("GENERATE_HTML"); - //---- - cfg->addObsolete("QTHELP_FILE"); - //---- - cfg->addObsolete("QTHELP_CONFIG"); - //---- - cfg->addObsolete("DOXYGEN2QTHELP_LOC"); + cs->addDependency("GENERATE_HTMLHELP"); //---- cb = cfg->addBool( - "GENERATE_CHI", - "If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag \n" - "controls if a separate .chi index file is generated (YES) or that \n" - "it should be included in the master .chm file (NO).\n", - FALSE - ); - cb->addDependency("GENERATE_HTML"); + "GENERATE_CHI", + "If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag \n" + "controls if a separate .chi index file is generated (YES) or that \n" + "it should be included in the master .chm file (NO).", + FALSE + ); + cb->addDependency("GENERATE_HTMLHELP"); //---- cs = cfg->addString( - "CHM_INDEX_ENCODING", - "If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING\n" - "is used to encode HtmlHelp index (hhk), content (hhc) and project file\n" - "content.\n" - ); - cs->addDependency("GENERATE_HTML"); + "CHM_INDEX_ENCODING", + "If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING \n" + "is used to encode HtmlHelp index (hhk), content (hhc) and project file \n" + "content." + ); + cs->addDependency("GENERATE_HTMLHELP"); //---- cb = cfg->addBool( - "BINARY_TOC", - "If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag \n" - "controls whether a binary table of contents is generated (YES) or a \n" - "normal table of contents (NO) in the .chm file.\n", - FALSE - ); - cb->addDependency("GENERATE_HTML"); + "BINARY_TOC", + "If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag \n" + "controls whether a binary table of contents is generated (YES) or a \n" + "normal table of contents (NO) in the .chm file.", + FALSE + ); + cb->addDependency("GENERATE_HTMLHELP"); //---- cb = cfg->addBool( - "TOC_EXPAND", - "The TOC_EXPAND flag can be set to YES to add extra items for group members \n" - "to the contents of the HTML help documentation and to the tree view. \n", - FALSE - ); - cb->addDependency("GENERATE_HTML"); - - ///////////////////////////////////////////////////////// - // QT HELP ////////////////////////////////////////////// - ///////////////////////////////////////////////////////// - + "TOC_EXPAND", + "The TOC_EXPAND flag can be set to YES to add extra items for group members \n" + "to the contents of the HTML help documentation and to the tree view.", + FALSE + ); + cb->addDependency("GENERATE_HTMLHELP"); + //---- cb = cfg->addBool( - "GENERATE_QHP", - "If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER \n" - "are set, an additional index file will be generated that can be used as input for \n" - "Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated \n" - "HTML documentation. \n", - FALSE - ); + "GENERATE_QHP", + "If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER \n" + "are set, an additional index file will be generated that can be used as input for \n" + "Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated \n" + "HTML documentation.", + FALSE + ); cb->addDependency("GENERATE_HTML"); //---- cs = cfg->addString( - "QCH_FILE", - "If the QHG_LOCATION tag is specified, the QCH_FILE tag can \n" - "be used to specify the file name of the resulting .qch file. \n" - "The path specified is relative to the HTML output folder. \n" - ); + "QCH_FILE", + "If the QHG_LOCATION tag is specified, the QCH_FILE tag can \n" + "be used to specify the file name of the resulting .qch file. \n" + "The path specified is relative to the HTML output folder." + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_QHP"); //---- cs = cfg->addString( - "QHP_NAMESPACE", - "The QHP_NAMESPACE tag specifies the namespace to use when generating \n" - "Qt Help Project output. For more information please see \n" - "http://doc.trolltech.com/qthelpproject.html#namespace \n" - ); + "QHP_NAMESPACE", + "The QHP_NAMESPACE tag specifies the namespace to use when generating \n" + "Qt Help Project output. For more information please see \n" + "http://doc.trolltech.com/qthelpproject.html#namespace" + ); cs->addDependency("GENERATE_QHP"); //---- cs = cfg->addString( - "QHP_VIRTUAL_FOLDER", - "The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating \n" - "Qt Help Project output. For more information please see \n" - "http://doc.trolltech.com/qthelpproject.html#virtual-folders \n" - ); + "QHP_VIRTUAL_FOLDER", + "The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating \n" + "Qt Help Project output. For more information please see \n" + "http://doc.trolltech.com/qthelpproject.html#virtual-folders" + ); cs->setDefaultValue("doc"); cs->addDependency("GENERATE_QHP"); //---- - cs = cfg->addString( - "QHP_CUST_FILTER_NAME", - "If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. \n" - "For more information please see \n" - "http://doc.trolltech.com/qthelpproject.html#custom-filters \n" - ); + "QHP_CUST_FILTER_NAME", + "If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. \n" + "For more information please see \n" + "http://doc.trolltech.com/qthelpproject.html#custom-filters" + ); cs->addDependency("GENERATE_QHP"); //---- - cs = cfg->addString( - "QHP_CUST_FILTER_ATTRS", - "The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add." - "For more information please see \n" - "<a href=\"http://doc.trolltech.com/qthelpproject.html#custom-filters\">Qt Help Project / Custom Filters</a>. \n" - ); + "QHP_CUST_FILTER_ATTRS", + "The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see \n" + "<a href=\"http://doc.trolltech.com/qthelpproject.html#custom-filters\">Qt Help Project / Custom Filters</a>." + ); cs->addDependency("GENERATE_QHP"); //---- - cs = cfg->addString( - "QHP_SECT_FILTER_ATTRS", - "The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's \n" - "filter section matches. \n" - "<a href=\"http://doc.trolltech.com/qthelpproject.html#filter-attributes\">Qt Help Project / Filter Attributes</a>. \n" - ); + "QHP_SECT_FILTER_ATTRS", + "The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's \n" + "filter section matches. \n" + "<a href=\"http://doc.trolltech.com/qthelpproject.html#filter-attributes\">Qt Help Project / Filter Attributes</a>." + ); cs->addDependency("GENERATE_QHP"); //---- - cs = cfg->addString( - "QHG_LOCATION", - "If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can \n" - "be used to specify the location of Qt's qhelpgenerator. \n" - "If non-empty doxygen will try to run qhelpgenerator on the generated \n" - ".qhp file .\n" - ); + "QHG_LOCATION", + "If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can \n" + "be used to specify the location of Qt's qhelpgenerator. \n" + "If non-empty doxygen will try to run qhelpgenerator on the generated \n" + ".qhp file." + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_QHP"); - - ///////////////////////////////////////////////////////// - // MISC ///////////////////////////////////////////////// - ///////////////////////////////////////////////////////// - + //---- cb = cfg->addBool( - "DISABLE_INDEX", - "The DISABLE_INDEX tag can be used to turn on/off the condensed index at \n" - "top of each HTML page. The value NO (the default) enables the index and \n" - "the value YES disables it. \n", - FALSE - ); + "DISABLE_INDEX", + "The DISABLE_INDEX tag can be used to turn on/off the condensed index at \n" + "top of each HTML page. The value NO (the default) enables the index and \n" + "the value YES disables it.", + FALSE + ); cb->addDependency("GENERATE_HTML"); //---- ci = cfg->addInt( - "ENUM_VALUES_PER_LINE", - "This tag can be used to set the number of enum values (range [1..20]) \n" - "that doxygen will group on one line in the generated HTML documentation. \n", - 1,20,4 + "ENUM_VALUES_PER_LINE", + "This tag can be used to set the number of enum values (range [1..20]) \n" + "that doxygen will group on one line in the generated HTML documentation.", + 1,20,4 ); ci->addDependency("GENERATE_HTML"); //---- ce = cfg->addEnum( - "GENERATE_TREEVIEW", - "The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\n" - "structure should be generated to display hierarchical information.\n" - "If the tag value is set to FRAME, a side panel will be generated\n" - "containing a tree-like index structure (just like the one that \n" - "is generated for HTML Help). For this to work a browser that supports \n" - "JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, \n" - "Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are \n" - "probably better off using the HTML help feature. Other possible values \n" - "for this tag are: HIERARCHIES, which will generate the Groups, Directories,\n" - "and Class Hierarchy pages using a tree view instead of an ordered list;\n" - "ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which\n" - "disables this behavior completely. For backwards compatibility with previous\n" - "releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE\n" - "respectively.\n", - "NONE" - ); + "GENERATE_TREEVIEW", + "The GENERATE_TREEVIEW tag is used to specify whether a tree-like index \n" + "structure should be generated to display hierarchical information. \n" + "If the tag value is set to FRAME, a side panel will be generated \n" + "containing a tree-like index structure (just like the one that \n" + "is generated for HTML Help). For this to work a browser that supports \n" + "JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, \n" + "Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are \n" + "probably better off using the HTML help feature. Other possible values \n" + "for this tag are: HIERARCHIES, which will generate the Groups, Directories, \n" + "and Class Hierarchy pages using a tree view instead of an ordered list; \n" + "ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which \n" + "disables this behavior completely. For backwards compatibility with previous \n" + "releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE \n" + "respectively.", + "NONE" + ); ce->addValue("NONE"); ce->addValue("FRAME"); ce->addValue("HIERARCHIES"); @@ -1389,90 +1312,81 @@ void addConfigOptions(Config *cfg) ce->addDependency("GENERATE_HTML"); //---- ci = cfg->addInt( - "TREEVIEW_WIDTH", - "If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be \n" - "used to set the initial width (in pixels) of the frame in which the tree \n" - "is shown. \n", - 0,1500,250 - ); + "TREEVIEW_WIDTH", + "If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be \n" + "used to set the initial width (in pixels) of the frame in which the tree \n" + "is shown.", + 0,1500,250 + ); ci->addDependency("GENERATE_HTML"); //---- ci = cfg->addInt( - "FORMULA_FONTSIZE", - "Use this tag to change the font size of Latex formulas included \n" - "as images in the HTML documentation. The default is 10. Note that \n" - "when you change the font size after a successful doxygen run you need \n" - "to manually remove any form_*.png images from the HTML output directory \n" - "to force them to be regenerated. \n", - 8,50,10 - ); + "FORMULA_FONTSIZE", + "Use this tag to change the font size of Latex formulas included \n" + "as images in the HTML documentation. The default is 10. Note that \n" + "when you change the font size after a successful doxygen run you need \n" + "to manually remove any form_*.png images from the HTML output directory \n" + "to force them to be regenerated.", + 8,50,10 + ); ci->addDependency("GENERATE_HTML"); + //--------------------------------------------------------------------------- + cfg->addInfo("LaTeX","configuration options related to the LaTeX output"); + //--------------------------------------------------------------------------- - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "LaTeX","configuration options related to the LaTeX output"); - //----------------------------------------------------------------------------------------------- + //---- cb = cfg->addBool( - "GENERATE_LATEX", - "If the GENERATE_LATEX tag is set to YES (the default) Doxygen will \n" - "generate Latex output. \n", - TRUE - ); + "GENERATE_LATEX", + "If the GENERATE_LATEX tag is set to YES (the default) Doxygen will \n" + "generate Latex output.", + TRUE + ); //---- cs = cfg->addString( - "LATEX_OUTPUT", - "The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. \n" - "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" - "put in front of it. If left blank `latex' will be used as the default path. \n" - ); + "LATEX_OUTPUT", + "The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. \n" + "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" + "put in front of it. If left blank `latex' will be used as the default path." + ); cs->setDefaultValue("latex"); cs->setWidgetType(ConfigString::Dir); cs->addDependency("GENERATE_LATEX"); //---- -#if 0 - cs = cfg->addString( "LATEX_OUTPUT_ENCODING", - "The LATEX_OUTPUT_ENCODING specifies the character encoding of the LaTeX output.\n" - "produced by doxygen. If left blank ISO-8859-1 will be used. Doxygen uses \n" - "libiconv for the transcoding. See http://www.gnu.org/software/libiconv for \n" - "the list of possible encodings.\n" - ); - cs->setDefaultValue("ISO-8859-1"); - cs->addDependency("GENERATE_LATEX"); -#endif cs = cfg->addString( - "LATEX_CMD_NAME", - "The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be \n" - "invoked. If left blank `latex' will be used as the default command name. \n" - ); + "LATEX_CMD_NAME", + "The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be \n" + "invoked. If left blank `latex' will be used as the default command name." + ); cs->setDefaultValue("latex"); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_LATEX"); //---- cs = cfg->addString( - "MAKEINDEX_CMD_NAME", - "The MAKEINDEX_CMD_NAME tag can be used to specify the command name to \n" - "generate index for LaTeX. If left blank `makeindex' will be used as the \n" - "default command name. \n" - ); + "MAKEINDEX_CMD_NAME", + "The MAKEINDEX_CMD_NAME tag can be used to specify the command name to \n" + "generate index for LaTeX. If left blank `makeindex' will be used as the \n" + "default command name." + ); cs->setDefaultValue("makeindex"); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_LATEX"); //---- cb = cfg->addBool( - "COMPACT_LATEX", - "If the COMPACT_LATEX tag is set to YES Doxygen generates more compact \n" - "LaTeX documents. This may be useful for small projects and may help to \n" - "save some trees in general. \n", - FALSE - ); + "COMPACT_LATEX", + "If the COMPACT_LATEX tag is set to YES Doxygen generates more compact \n" + "LaTeX documents. This may be useful for small projects and may help to \n" + "save some trees in general.", + FALSE + ); cb->addDependency("GENERATE_LATEX"); //---- ce = cfg->addEnum( - "PAPER_TYPE", - "The PAPER_TYPE tag can be used to set the paper type that is used \n" - "by the printer. Possible values are: a4, a4wide, letter, legal and \n" - "executive. If left blank a4wide will be used. \n", - "a4wide" - ); + "PAPER_TYPE", + "The PAPER_TYPE tag can be used to set the paper type that is used \n" + "by the printer. Possible values are: a4, a4wide, letter, legal and \n" + "executive. If left blank a4wide will be used.", + "a4wide" + ); ce->addValue("a4"); ce->addValue("a4wide"); ce->addValue("letter"); @@ -1481,686 +1395,708 @@ void addConfigOptions(Config *cfg) ce->addDependency("GENERATE_LATEX"); //---- cl = cfg->addList( - "EXTRA_PACKAGES", - "The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX \n" - "packages that should be included in the LaTeX output. \n" - ); + "EXTRA_PACKAGES", + "The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX \n" + "packages that should be included in the LaTeX output." + ); cl->addDependency("GENERATE_LATEX"); //---- cs = cfg->addString( - "LATEX_HEADER", - "The LATEX_HEADER tag can be used to specify a personal LaTeX header for \n" - "the generated latex document. The header should contain everything until \n" - "the first chapter. If it is left blank doxygen will generate a \n" - "standard header. Notice: only use this tag if you know what you are doing! \n" - ); + "LATEX_HEADER", + "The LATEX_HEADER tag can be used to specify a personal LaTeX header for \n" + "the generated latex document. The header should contain everything until \n" + "the first chapter. If it is left blank doxygen will generate a \n" + "standard header. Notice: only use this tag if you know what you are doing!" + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_LATEX"); //---- cb = cfg->addBool( - "PDF_HYPERLINKS", - "If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated \n" - "is prepared for conversion to pdf (using ps2pdf). The pdf file will \n" - "contain links (just like the HTML output) instead of page references \n" - "This makes the output suitable for online browsing using a pdf viewer. \n", - TRUE - ); + "PDF_HYPERLINKS", + "If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated \n" + "is prepared for conversion to pdf (using ps2pdf). The pdf file will \n" + "contain links (just like the HTML output) instead of page references \n" + "This makes the output suitable for online browsing using a pdf viewer.", + TRUE + ); cb->addDependency("GENERATE_LATEX"); //---- cb = cfg->addBool( - "USE_PDFLATEX", - "If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of \n" - "plain latex in the generated Makefile. Set this option to YES to get a \n" - "higher quality PDF documentation. \n", - TRUE - ); + "USE_PDFLATEX", + "If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of \n" + "plain latex in the generated Makefile. Set this option to YES to get a \n" + "higher quality PDF documentation.", + TRUE + ); cb->addDependency("GENERATE_LATEX"); //---- cb = cfg->addBool( - "LATEX_BATCHMODE", - "If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\\\batchmode. \n" - "command to the generated LaTeX files. This will instruct LaTeX to keep \n" - "running if errors occur, instead of asking the user for help. \n" - "This option is also used when generating formulas in HTML. \n", - FALSE - ); + "LATEX_BATCHMODE", + "If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\\\batchmode. \n" + "command to the generated LaTeX files. This will instruct LaTeX to keep \n" + "running if errors occur, instead of asking the user for help. \n" + "This option is also used when generating formulas in HTML.", + FALSE + ); cb->addDependency("GENERATE_LATEX"); //---- cb = cfg->addBool( - "LATEX_HIDE_INDICES", - "If LATEX_HIDE_INDICES is set to YES then doxygen will not \n" - "include the index chapters (such as File Index, Compound Index, etc.) \n" - "in the output. \n", - FALSE - ); + "LATEX_HIDE_INDICES", + "If LATEX_HIDE_INDICES is set to YES then doxygen will not \n" + "include the index chapters (such as File Index, Compound Index, etc.) \n" + "in the output.", + FALSE + ); cb->addDependency("GENERATE_LATEX"); - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "RTF","configuration options related to the RTF output"); - //----------------------------------------------------------------------------------------------- + //--------------------------------------------------------------------------- + cfg->addInfo("RTF","configuration options related to the RTF output"); + //--------------------------------------------------------------------------- + + //---- cb = cfg->addBool( - "GENERATE_RTF", - "If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output \n" - "The RTF output is optimized for Word 97 and may not look very pretty with \n" - "other RTF readers or editors.\n", - FALSE - ); + "GENERATE_RTF", + "If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output \n" + "The RTF output is optimized for Word 97 and may not look very pretty with \n" + "other RTF readers or editors.", + FALSE + ); //---- cs = cfg->addString( - "RTF_OUTPUT", - "The RTF_OUTPUT tag is used to specify where the RTF docs will be put. \n" - "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" - "put in front of it. If left blank `rtf' will be used as the default path. \n" - ); + "RTF_OUTPUT", + "The RTF_OUTPUT tag is used to specify where the RTF docs will be put. \n" + "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" + "put in front of it. If left blank `rtf' will be used as the default path." + ); cs->setDefaultValue("rtf"); cs->setWidgetType(ConfigString::Dir); cs->addDependency("GENERATE_RTF"); //---- -#if 0 - cs = cfg->addString( "RTF_OUTPUT_ENCODING", - "The RTF_OUTPUT_ENCODING specifies the character encoding of the RTF output.\n" - "produced by doxygen. If left blank ISO-8859-1 will be used. Doxygen uses \n" - "libiconv for the transcoding. See http://www.gnu.org/software/libiconv for \n" - "the list of possible encodings.\n" + cb = cfg->addBool( + "COMPACT_RTF", + "If the COMPACT_RTF tag is set to YES Doxygen generates more compact \n" + "RTF documents. This may be useful for small projects and may help to \n" + "save some trees in general.", + FALSE ); - cs->setDefaultValue("ISO-8859-1"); - cs->addDependency("GENERATE_RTF"); -#endif - cb = cfg->addBool( - "COMPACT_RTF", - "If the COMPACT_RTF tag is set to YES Doxygen generates more compact \n" - "RTF documents. This may be useful for small projects and may help to \n" - "save some trees in general. \n", - FALSE - ); cb->addDependency("GENERATE_RTF"); //---- cb = cfg->addBool( - "RTF_HYPERLINKS", - "If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated \n" - "will contain hyperlink fields. The RTF file will \n" - "contain links (just like the HTML output) instead of page references. \n" - "This makes the output suitable for online browsing using WORD or other \n" - "programs which support those fields. \n" - "Note: wordpad (write) and others do not support links. \n", - FALSE - ); + "RTF_HYPERLINKS", + "If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated \n" + "will contain hyperlink fields. The RTF file will \n" + "contain links (just like the HTML output) instead of page references. \n" + "This makes the output suitable for online browsing using WORD or other \n" + "programs which support those fields. \n" + "Note: wordpad (write) and others do not support links.", + FALSE + ); cb->addDependency("GENERATE_RTF"); //---- cs = cfg->addString( - "RTF_STYLESHEET_FILE", - "Load stylesheet definitions from file. Syntax is similar to doxygen's \n" - "config file, i.e. a series of assignments. You only have to provide \n" - "replacements, missing definitions are set to their default value. \n" - ); + "RTF_STYLESHEET_FILE", + "Load stylesheet definitions from file. Syntax is similar to doxygen's \n" + "config file, i.e. a series of assignments. You only have to provide \n" + "replacements, missing definitions are set to their default value." + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_RTF"); //---- cs = cfg->addString( - "RTF_EXTENSIONS_FILE", - "Set optional variables used in the generation of an rtf document. \n" - "Syntax is similar to doxygen's config file.\n" - ); + "RTF_EXTENSIONS_FILE", + "Set optional variables used in the generation of an rtf document. \n" + "Syntax is similar to doxygen's config file." + ); cs->setWidgetType(ConfigString::File); cs->addDependency("GENERATE_RTF"); + //--------------------------------------------------------------------------- + cfg->addInfo("Man","configuration options related to the man page output"); + //--------------------------------------------------------------------------- - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Man","configuration options related to the man page output"); - //----------------------------------------------------------------------------------------------- + //---- cb = cfg->addBool( - "GENERATE_MAN", - "If the GENERATE_MAN tag is set to YES (the default) Doxygen will \n" - "generate man pages \n", - FALSE - ); + "GENERATE_MAN", + "If the GENERATE_MAN tag is set to YES (the default) Doxygen will \n" + "generate man pages", + FALSE + ); //---- cs = cfg->addString( - "MAN_OUTPUT", - "The MAN_OUTPUT tag is used to specify where the man pages will be put. \n" - "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" - "put in front of it. If left blank `man' will be used as the default path. \n" - ); + "MAN_OUTPUT", + "The MAN_OUTPUT tag is used to specify where the man pages will be put. \n" + "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" + "put in front of it. If left blank `man' will be used as the default path." + ); cs->setDefaultValue("man"); cs->setWidgetType(ConfigString::Dir); cs->addDependency("GENERATE_MAN"); //---- cs = cfg->addString( - "MAN_EXTENSION", - "The MAN_EXTENSION tag determines the extension that is added to \n" - "the generated man pages (default is the subroutine's section .3) \n" - ); + "MAN_EXTENSION", + "The MAN_EXTENSION tag determines the extension that is added to \n" + "the generated man pages (default is the subroutine's section .3)" + ); cs->setDefaultValue(".3"); cs->addDependency("GENERATE_MAN"); //---- cb = cfg->addBool( - "MAN_LINKS", - "If the MAN_LINKS tag is set to YES and Doxygen generates man output, \n" - "then it will generate one additional man file for each entity \n" - "documented in the real man page(s). These additional files \n" - "only source the real man page, but without them the man command \n" - "would be unable to find the correct page. The default is NO. \n", - FALSE - ); + "MAN_LINKS", + "If the MAN_LINKS tag is set to YES and Doxygen generates man output, \n" + "then it will generate one additional man file for each entity \n" + "documented in the real man page(s). These additional files \n" + "only source the real man page, but without them the man command \n" + "would be unable to find the correct page. The default is NO.", + FALSE + ); cb->addDependency("GENERATE_MAN"); - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "XML","configuration options related to the XML output"); - //----------------------------------------------------------------------------------------------- - cb = cfg->addBool( - "GENERATE_XML", - "If the GENERATE_XML tag is set to YES Doxygen will \n" - "generate an XML file that captures the structure of \n" - "the code including all documentation. \n", - FALSE - ); + //--------------------------------------------------------------------------- + cfg->addInfo("XML","configuration options related to the XML output"); + //--------------------------------------------------------------------------- + + //---- + cb = cfg->addBool( + "GENERATE_XML", + "If the GENERATE_XML tag is set to YES Doxygen will \n" + "generate an XML file that captures the structure of \n" + "the code including all documentation.", + FALSE + ); //---- cs = cfg->addString( - "XML_OUTPUT", - "The XML_OUTPUT tag is used to specify where the XML pages will be put. \n" - "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" - "put in front of it. If left blank `xml' will be used as the default path. \n" - ); + "XML_OUTPUT", + "The XML_OUTPUT tag is used to specify where the XML pages will be put. \n" + "If a relative path is entered the value of OUTPUT_DIRECTORY will be \n" + "put in front of it. If left blank `xml' will be used as the default path." + ); cs->setDefaultValue("xml"); cs->setWidgetType(ConfigString::Dir); cs->addDependency("GENERATE_XML"); //---- cs = cfg->addString( - "XML_SCHEMA", - "The XML_SCHEMA tag can be used to specify an XML schema, \n" - "which can be used by a validating XML parser to check the \n" - "syntax of the XML files. \n" - ); + "XML_SCHEMA", + "The XML_SCHEMA tag can be used to specify an XML schema, \n" + "which can be used by a validating XML parser to check the \n" + "syntax of the XML files." + ); cs->addDependency("GENERATE_XML"); //---- cs = cfg->addString( - "XML_DTD", - "The XML_DTD tag can be used to specify an XML DTD, \n" - "which can be used by a validating XML parser to check the \n" - "syntax of the XML files. \n" - ); + "XML_DTD", + "The XML_DTD tag can be used to specify an XML DTD, \n" + "which can be used by a validating XML parser to check the \n" + "syntax of the XML files." + ); cs->addDependency("GENERATE_XML"); //---- cb = cfg->addBool( - "XML_PROGRAMLISTING", - "If the XML_PROGRAMLISTING tag is set to YES Doxygen will \n" - "dump the program listings (including syntax highlighting \n" - "and cross-referencing information) to the XML output. Note that \n" - "enabling this will significantly increase the size of the XML output. \n", - TRUE - ); + "XML_PROGRAMLISTING", + "If the XML_PROGRAMLISTING tag is set to YES Doxygen will \n" + "dump the program listings (including syntax highlighting \n" + "and cross-referencing information) to the XML output. Note that \n" + "enabling this will significantly increase the size of the XML output.", + TRUE + ); cb->addDependency("GENERATE_XML"); + //--------------------------------------------------------------------------- + cfg->addInfo("DEF","configuration options for the AutoGen Definitions output"); + //--------------------------------------------------------------------------- - //-------------------------------------------------------------------------- - cfg->addInfo( "DEF","configuration options for the AutoGen Definitions output"); - //-------------------------------------------------------------------------- - cb = cfg->addBool( "GENERATE_AUTOGEN_DEF", + //---- + cb = cfg->addBool( + "GENERATE_AUTOGEN_DEF", + "If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will \n" + "generate an AutoGen Definitions (see autogen.sf.net) file \n" + "that captures the structure of the code including all \n" + "documentation. Note that this feature is still experimental \n" + "and incomplete at the moment.", + FALSE + ); + //--------------------------------------------------------------------------- + cfg->addInfo("PerlMod","configuration options related to the Perl module output"); + //--------------------------------------------------------------------------- - "If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will \n" - "generate an AutoGen Definitions (see autogen.sf.net) file \n" - "that captures the structure of the code including all \n" - "documentation. Note that this feature is still experimental \n" - "and incomplete at the moment. \n", - FALSE ); - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "PerlMod","configuration options related to the Perl module output"); - //----------------------------------------------------------------------------------------------- - cb = cfg->addBool( - "GENERATE_PERLMOD", - "If the GENERATE_PERLMOD tag is set to YES Doxygen will \n" - "generate a Perl module file that captures the structure of \n" - "the code including all documentation. Note that this \n" - "feature is still experimental and incomplete at the \n" - "moment. \n", - FALSE - ); - //---- - cb = cfg->addBool( - "PERLMOD_LATEX", - "If the PERLMOD_LATEX tag is set to YES Doxygen will generate \n" - "the necessary Makefile rules, Perl scripts and LaTeX code to be able \n" - "to generate PDF and DVI output from the Perl module output. \n", - FALSE - ); + //---- + cb = cfg->addBool( + "GENERATE_PERLMOD", + "If the GENERATE_PERLMOD tag is set to YES Doxygen will \n" + "generate a Perl module file that captures the structure of \n" + "the code including all documentation. Note that this \n" + "feature is still experimental and incomplete at the \n" + "moment.", + FALSE + ); + //---- + cb = cfg->addBool( + "PERLMOD_LATEX", + "If the PERLMOD_LATEX tag is set to YES Doxygen will generate \n" + "the necessary Makefile rules, Perl scripts and LaTeX code to be able \n" + "to generate PDF and DVI output from the Perl module output.", + FALSE + ); cb->addDependency("GENERATE_PERLMOD"); //---- - cb = cfg->addBool( - "PERLMOD_PRETTY", - "If the PERLMOD_PRETTY tag is set to YES the Perl module output will be \n" - "nicely formatted so it can be parsed by a human reader. This is useful \n" - "if you want to understand what is going on. On the other hand, if this \n" - "tag is set to NO the size of the Perl module output will be much smaller \n" - "and Perl will parse it just the same. \n", - TRUE - ); + cb = cfg->addBool( + "PERLMOD_PRETTY", + "If the PERLMOD_PRETTY tag is set to YES the Perl module output will be \n" + "nicely formatted so it can be parsed by a human reader. \n" + "This is useful \n" + "if you want to understand what is going on. \n" + "On the other hand, if this \n" + "tag is set to NO the size of the Perl module output will be much smaller \n" + "and Perl will parse it just the same.", + TRUE + ); cb->addDependency("GENERATE_PERLMOD"); //---- - cs = cfg->addString( - "PERLMOD_MAKEVAR_PREFIX", - "The names of the make variables in the generated doxyrules.make file \n" - "are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. \n" - "This is useful so different doxyrules.make files included by the same \n" - "Makefile don't overwrite each other's variables." - ); + cs = cfg->addString( + "PERLMOD_MAKEVAR_PREFIX", + "The names of the make variables in the generated doxyrules.make file \n" + "are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. \n" + "This is useful so different doxyrules.make files included by the same \n" + "Makefile don't overwrite each other's variables." + ); cs->addDependency("GENERATE_PERLMOD"); + //--------------------------------------------------------------------------- + cfg->addInfo("Preprocessor","Configuration options related to the preprocessor "); + //--------------------------------------------------------------------------- - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Preprocessor","Configuration options related to the preprocessor "); - //----------------------------------------------------------------------------------------------- - cb = cfg->addBool( - "ENABLE_PREPROCESSING", - "If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will \n" - "evaluate all C-preprocessor directives found in the sources and include \n" - "files. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "MACRO_EXPANSION", - "If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro \n" - "names in the source code. If set to NO (the default) only conditional \n" - "compilation will be performed. Macro expansion can be done in a controlled \n" - "way by setting EXPAND_ONLY_PREDEF to YES. \n", - FALSE - ); + //---- + cb = cfg->addBool( + "ENABLE_PREPROCESSING", + "If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will \n" + "evaluate all C-preprocessor directives found in the sources and include \n" + "files.", + TRUE + ); + //---- + cb = cfg->addBool( + "MACRO_EXPANSION", + "If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro \n" + "names in the source code. If set to NO (the default) only conditional \n" + "compilation will be performed. Macro expansion can be done in a controlled \n" + "way by setting EXPAND_ONLY_PREDEF to YES.", + FALSE + ); cb->addDependency("ENABLE_PREPROCESSING"); //---- cb = cfg->addBool( - "EXPAND_ONLY_PREDEF", - "If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES \n" - "then the macro expansion is limited to the macros specified with the \n" - "PREDEFINED and EXPAND_AS_DEFINED tags. \n", - FALSE - ); + "EXPAND_ONLY_PREDEF", + "If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES \n" + "then the macro expansion is limited to the macros specified with the \n" + "PREDEFINED and EXPAND_AS_DEFINED tags.", + FALSE + ); cb->addDependency("ENABLE_PREPROCESSING"); //---- cb = cfg->addBool( - "SEARCH_INCLUDES", - "If the SEARCH_INCLUDES tag is set to YES (the default) the includes files \n" - "in the INCLUDE_PATH (see below) will be search if a #include is found. \n", - TRUE - ); + "SEARCH_INCLUDES", + "If the SEARCH_INCLUDES tag is set to YES (the default) the includes files \n" + "in the INCLUDE_PATH (see below) will be search if a #include is found.", + TRUE + ); cb->addDependency("ENABLE_PREPROCESSING"); //---- cl = cfg->addList( - "INCLUDE_PATH", - "The INCLUDE_PATH tag can be used to specify one or more directories that \n" - "contain include files that are not input files but should be processed by \n" - "the preprocessor.\n" - ); - cl->setWidgetType(ConfigList::Dir); + "INCLUDE_PATH", + "The INCLUDE_PATH tag can be used to specify one or more directories that \n" + "contain include files that are not input files but should be processed by \n" + "the preprocessor." + ); cl->addDependency("ENABLE_PREPROCESSING"); + cl->setWidgetType(ConfigList::Dir); //---- cl = cfg->addList( - "INCLUDE_FILE_PATTERNS", - "You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard \n" - "patterns (like *.h and *.hpp) to filter out the header-files in the \n" - "directories. If left blank, the patterns specified with FILE_PATTERNS will \n" - "be used. \n" - ); + "INCLUDE_FILE_PATTERNS", + "You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard \n" + "patterns (like *.h and *.hpp) to filter out the header-files in the \n" + "directories. If left blank, the patterns specified with FILE_PATTERNS will \n" + "be used." + ); cl->addDependency("ENABLE_PREPROCESSING"); //---- cl = cfg->addList( - "PREDEFINED", - "The PREDEFINED tag can be used to specify one or more macro names that \n" - "are defined before the preprocessor is started (similar to the -D option of \n" - "gcc). The argument of the tag is a list of macros of the form: name \n" - "or name=definition (no spaces). If the definition and the = are \n" - "omitted =1 is assumed. To prevent a macro definition from being \n" - "undefined via #undef or recursively expanded use the := operator \n" - "instead of the = operator.\n" - ); + "PREDEFINED", + "The PREDEFINED tag can be used to specify one or more macro names that \n" + "are defined before the preprocessor is started (similar to the -D option of \n" + "gcc). The argument of the tag is a list of macros of the form: name \n" + "or name=definition (no spaces). If the definition and the = are \n" + "omitted =1 is assumed. To prevent a macro definition from being \n" + "undefined via #undef or recursively expanded use the := operator \n" + "instead of the = operator." + ); cl->addDependency("ENABLE_PREPROCESSING"); //---- cl = cfg->addList( - "EXPAND_AS_DEFINED", - "If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then \n" - "this tag can be used to specify a list of macro names that should be expanded. \n" - "The macro definition that is found in the sources will be used. \n" - "Use the PREDEFINED tag if you want to use a different macro definition. \n" - ); + "EXPAND_AS_DEFINED", + "If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then \n" + "this tag can be used to specify a list of macro names that should be expanded. \n" + "The macro definition that is found in the sources will be used. \n" + "Use the PREDEFINED tag if you want to use a different macro definition." + ); cl->addDependency("ENABLE_PREPROCESSING"); //---- cb = cfg->addBool( - "SKIP_FUNCTION_MACROS", - "If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then \n" - "doxygen's preprocessor will remove all function-like macros that are alone \n" - "on a line, have an all uppercase name, and do not end with a semicolon. Such \n" - "function macros are typically used for boiler-plate code, and will confuse \n" - "the parser if not removed. \n", - TRUE - ); + "SKIP_FUNCTION_MACROS", + "If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then \n" + "doxygen's preprocessor will remove all function-like macros that are alone \n" + "on a line, have an all uppercase name, and do not end with a semicolon. Such \n" + "function macros are typically used for boiler-plate code, and will confuse \n" + "the parser if not removed.", + TRUE + ); cb->addDependency("ENABLE_PREPROCESSING"); - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "External","Configuration::additions related to external references "); - //----------------------------------------------------------------------------------------------- + //--------------------------------------------------------------------------- + cfg->addInfo("External","Configuration::additions related to external references "); + //--------------------------------------------------------------------------- + + //---- cl = cfg->addList( - "TAGFILES", - "The TAGFILES option can be used to specify one or more tagfiles. \n" - "Optionally an initial location of the external documentation \n" - "can be added for each tagfile. The format of a tag file without \n" - "this location is as follows: \n" - " TAGFILES = file1 file2 ... \n" - "Adding location for the tag files is done as follows: \n" - " TAGFILES = file1=loc1 \"file2 = loc2\" ... \n" - "where \"loc1\" and \"loc2\" can be relative or absolute paths or \n" - "URLs. If a location is present for each tag, the installdox tool \n" - "does not have to be run to correct the links.\n" - "Note that each tag file must have a unique name\n" - "(where the name does NOT include the path)\n" - "If a tag file is not located in the directory in which doxygen \n" - "is run, you must also specify the path to the tagfile here. \n" - ); + "TAGFILES", + "The TAGFILES option can be used to specify one or more tagfiles. \n" + "Optionally an initial location of the external documentation \n" + "can be added for each tagfile. The format of a tag file without \n" + "this location is as follows: \n" + " \n" + "TAGFILES = file1 file2 ... \n" + "Adding location for the tag files is done as follows: \n" + " \n" + "TAGFILES = file1=loc1 \"file2 = loc2\" ... \n" + "where \"loc1\" and \"loc2\" can be relative or absolute paths or \n" + "URLs. If a location is present for each tag, the installdox tool \n" + "does not have to be run to correct the links. \n" + "Note that each tag file must have a unique name \n" + "(where the name does NOT include the path) \n" + "If a tag file is not located in the directory in which doxygen \n" + "is run, you must also specify the path to the tagfile here." + ); cl->setWidgetType(ConfigList::File); //---- cs = cfg->addString( - "GENERATE_TAGFILE", - "When a file name is specified after GENERATE_TAGFILE, doxygen will create \n" - "a tag file that is based on the input files it reads. \n" - ); + "GENERATE_TAGFILE", + "When a file name is specified after GENERATE_TAGFILE, doxygen will create \n" + "a tag file that is based on the input files it reads." + ); cs->setWidgetType(ConfigString::File); //---- cb = cfg->addBool( - "ALLEXTERNALS", - "If the ALLEXTERNALS tag is set to YES all external classes will be listed \n" - "in the class index. If set to NO only the inherited external classes \n" - "will be listed. \n", - FALSE - ); + "ALLEXTERNALS", + "If the ALLEXTERNALS tag is set to YES all external classes will be listed \n" + "in the class index. If set to NO only the inherited external classes \n" + "will be listed.", + FALSE + ); //---- cb = cfg->addBool( - "EXTERNAL_GROUPS", - "If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed \n" - "in the modules index. If set to NO, only the current project's groups will \n" - "be listed. \n", - TRUE - ); + "EXTERNAL_GROUPS", + "If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed \n" + "in the modules index. If set to NO, only the current project's groups will \n" + "be listed.", + TRUE + ); //---- cs = cfg->addString( - "PERL_PATH", - "The PERL_PATH should be the absolute path and name of the perl script \n" - "interpreter (i.e. the result of `which perl'). \n" - ); + "PERL_PATH", + "The PERL_PATH should be the absolute path and name of the perl script \n" + "interpreter (i.e. the result of `which perl')." + ); cs->setDefaultValue("/usr/bin/perl"); cs->setWidgetType(ConfigString::Dir); + //--------------------------------------------------------------------------- + cfg->addInfo("Dot","Configuration options related to the dot tool "); + //--------------------------------------------------------------------------- - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Dot","Configuration options related to the dot tool "); - //----------------------------------------------------------------------------------------------- - cb = cfg->addBool( - "CLASS_DIAGRAMS", - "If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will \n" - "generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base \n" - "or super classes. Setting the tag to NO turns the diagrams off. Note that \n" - "this option is superseded by the HAVE_DOT option below. This is only a \n" - "fallback. It is recommended to install and use dot, since it yields more \n" - "powerful graphs. \n", - TRUE - ); - //---- - cs = cfg->addString( "MSCGEN_PATH", - "You can define message sequence charts within doxygen comments using the \\msc \n" - "command. Doxygen will then run the mscgen tool (see \n" - "http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the \n" - "documentation. The MSCGEN_PATH tag allows you to specify the directory where \n" - "the mscgen tool resides. If left empty the tool is assumed to be found in the \n" - "default search path. \n" - ); - //---- - cb = cfg->addBool( - "HIDE_UNDOC_RELATIONS", - "If set to YES, the inheritance and collaboration graphs will hide \n" - "inheritance and usage relations if the target is undocumented \n" - "or is not a class. \n", - TRUE - ); - //---- - cb = cfg->addBool( - "HAVE_DOT", - "If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is \n" - "available from the path. This tool is part of Graphviz, a graph visualization \n" - "toolkit from AT&T and Lucent Bell Labs. The other options in this section \n" - "have no effect if this option is set to NO (the default) \n", - FALSE - ); - //---- - cs = cfg->addString( "DOT_FONTNAME", - "By default doxygen will write a font called FreeSans.ttf to the output \n" - "directory and reference it in all dot files that doxygen generates. This \n" - "font does not include all possible unicode characters however, so when you need \n" - "these (or just want a differently looking font) you can specify the font name \n" - "using DOT_FONTNAME. You need need to make sure dot is able to find the font, \n" - "which can be done by putting it in a standard location or by setting the \n" - "DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory \n" - "containing the font. \n" - ); + //---- + cb = cfg->addBool( + "CLASS_DIAGRAMS", + "If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will \n" + "generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base \n" + "or super classes. Setting the tag to NO turns the diagrams off. Note that \n" + "this option is superseded by the HAVE_DOT option below. This is only a \n" + "fallback. It is recommended to install and use dot, since it yields more \n" + "powerful graphs.", + TRUE + ); + //---- + cs = cfg->addString( + "MSCGEN_PATH", + "You can define message sequence charts within doxygen comments using the \\msc \n" + "command. Doxygen will then run the mscgen tool (see \n" + "http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the \n" + "documentation. The MSCGEN_PATH tag allows you to specify the directory where \n" + "the mscgen tool resides. If left empty the tool is assumed to be found in the \n" + "default search path." + ); + //---- + cb = cfg->addBool( + "HIDE_UNDOC_RELATIONS", + "If set to YES, the inheritance and collaboration graphs will hide \n" + "inheritance and usage relations if the target is undocumented \n" + "or is not a class.", + TRUE + ); + //---- + cb = cfg->addBool( + "HAVE_DOT", + "If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is \n" + "available from the path. This tool is part of Graphviz, a graph visualization \n" + "toolkit from AT&T and Lucent Bell Labs. The other options in this section \n" + "have no effect if this option is set to NO (the default)", + FALSE + ); + //---- + cs = cfg->addString( + "DOT_FONTNAME", + "By default doxygen will write a font called FreeSans.ttf to the output \n" + "directory and reference it in all dot files that doxygen generates. This \n" + "font does not include all possible unicode characters however, so when you need \n" + "these (or just want a differently looking font) you can specify the font name \n" + "using DOT_FONTNAME. You need need to make sure dot is able to find the font, \n" + "which can be done by putting it in a standard location or by setting the \n" + "DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory \n" + "containing the font." + ); cs->setDefaultValue("FreeSans"); cs->addDependency("HAVE_DOT"); //---- - ci = cfg->addInt( "DOT_FONTSIZE", - "The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. \n" - "The default size is 10pt. \n", - 4,24,10 - ); + ci = cfg->addInt( + "DOT_FONTSIZE", + "The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. \n" + "The default size is 10pt.", + 4,24,10 + ); ci->addDependency("HAVE_DOT"); //---- - cs = cfg->addString( "DOT_FONTPATH", - "By default doxygen will tell dot to use the output directory to look for the \n" - "FreeSans.ttf font (which doxygen will put there itself). If you specify a \n" - "different font using DOT_FONTNAME you can set the path where dot \n" - "can find it using this tag. \n" + cs = cfg->addString( + "DOT_FONTPATH", + "By default doxygen will tell dot to use the output directory to look for the \n" + "FreeSans.ttf font (which doxygen will put there itself). If you specify a \n" + "different font using DOT_FONTNAME you can set the path where dot \n" + "can find it using this tag." ); cs->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "CLASS_GRAPH", - "If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen \n" - "will generate a graph for each documented class showing the direct and \n" - "indirect inheritance relations. Setting this tag to YES will force the \n" - "the CLASS_DIAGRAMS tag to NO.\n", - TRUE - ); + "CLASS_GRAPH", + "If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen \n" + "will generate a graph for each documented class showing the direct and \n" + "indirect inheritance relations. Setting this tag to YES will force the \n" + "the CLASS_DIAGRAMS tag to NO.", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "COLLABORATION_GRAPH", - "If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen \n" - "will generate a graph for each documented class showing the direct and \n" - "indirect implementation dependencies (inheritance, containment, and \n" - "class references variables) of the class with other documented classes. \n", - TRUE - ); + "COLLABORATION_GRAPH", + "If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen \n" + "will generate a graph for each documented class showing the direct and \n" + "indirect implementation dependencies (inheritance, containment, and \n" + "class references variables) of the class with other documented classes.", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "GROUP_GRAPHS", - "If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen \n" - "will generate a graph for groups, showing the direct groups dependencies\n", - TRUE - ); + "GROUP_GRAPHS", + "If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen \n" + "will generate a graph for groups, showing the direct groups dependencies", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "UML_LOOK", - "If the UML_LOOK tag is set to YES doxygen will generate inheritance and \n" - "collaboration diagrams in a style similar to the OMG's Unified Modeling \n" - "Language. \n", - FALSE - ); + "UML_LOOK", + "If the UML_LOOK tag is set to YES doxygen will generate inheritance and \n" + "collaboration diagrams in a style similar to the OMG's Unified Modeling \n" + "Language.", + FALSE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "TEMPLATE_RELATIONS", - "If set to YES, the inheritance and collaboration graphs will show the \n" - "relations between templates and their instances. \n", - FALSE - ); + "TEMPLATE_RELATIONS", + "If set to YES, the inheritance and collaboration graphs will show the \n" + "relations between templates and their instances.", + FALSE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "INCLUDE_GRAPH", - "If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT \n" - "tags are set to YES then doxygen will generate a graph for each documented \n" - "file showing the direct and indirect include dependencies of the file with \n" - "other documented files. \n", - TRUE - ); + "INCLUDE_GRAPH", + "If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT \n" + "tags are set to YES then doxygen will generate a graph for each documented \n" + "file showing the direct and indirect include dependencies of the file with \n" + "other documented files.", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "INCLUDED_BY_GRAPH", - "If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and \n" - "HAVE_DOT tags are set to YES then doxygen will generate a graph for each \n" - "documented header file showing the documented files that directly or \n" - "indirectly include this file. \n", - TRUE - ); + "INCLUDED_BY_GRAPH", + "If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and \n" + "HAVE_DOT tags are set to YES then doxygen will generate a graph for each \n" + "documented header file showing the documented files that directly or \n" + "indirectly include this file.", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "CALL_GRAPH", - "If the CALL_GRAPH and HAVE_DOT options are set to YES then \n" - "doxygen will generate a call dependency graph for every global function \n" - "or class method. Note that enabling this option will significantly increase \n" - "the time of a run. So in most cases it will be better to enable call graphs \n" - "for selected functions only using the \\callgraph command.\n", - FALSE - ); + "CALL_GRAPH", + "If the CALL_GRAPH and HAVE_DOT options are set to YES then \n" + "doxygen will generate a call dependency graph for every global function \n" + "or class method. Note that enabling this option will significantly increase \n" + "the time of a run. So in most cases it will be better to enable call graphs \n" + "for selected functions only using the \\callgraph command.", + FALSE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "CALLER_GRAPH", - "If the CALLER_GRAPH and HAVE_DOT tags are set to YES then \n" - "doxygen will generate a caller dependency graph for every global function \n" - "or class method. Note that enabling this option will significantly increase \n" - "the time of a run. So in most cases it will be better to enable caller \n" - "graphs for selected functions only using the \\callergraph command.\n", - FALSE - ); + "CALLER_GRAPH", + "If the CALLER_GRAPH and HAVE_DOT tags are set to YES then \n" + "doxygen will generate a caller dependency graph for every global function \n" + "or class method. Note that enabling this option will significantly increase \n" + "the time of a run. So in most cases it will be better to enable caller \n" + "graphs for selected functions only using the \\callergraph command.", + FALSE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "GRAPHICAL_HIERARCHY", - "If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen \n" - "will graphical hierarchy of all classes instead of a textual one. \n", - TRUE - ); + "GRAPHICAL_HIERARCHY", + "If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen \n" + "will graphical hierarchy of all classes instead of a textual one.", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- - cb = cfg->addBool( - "DIRECTORY_GRAPH", - "If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES \n" - "then doxygen will show the dependencies a directory has on other directories \n" - "in a graphical way. The dependency relations are determined by the #include\n" - "relations between the files in the directories.\n", - TRUE - ); + cb = cfg->addBool( + "DIRECTORY_GRAPH", + "If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES \n" + "then doxygen will show the dependencies a directory has on other directories \n" + "in a graphical way. The dependency relations are determined by the #include \n" + "relations between the files in the directories.", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- ce = cfg->addEnum( - "DOT_IMAGE_FORMAT", - "The DOT_IMAGE_FORMAT tag can be used to set the image format of the images \n" - "generated by dot. Possible values are png, jpg, or gif\n" - "If left blank png will be used. \n", - "png" - ); + "DOT_IMAGE_FORMAT", + "The DOT_IMAGE_FORMAT tag can be used to set the image format of the images \n" + "generated by dot. Possible values are png, jpg, or gif \n" + "If left blank png will be used.", + "png" + ); ce->addValue("png"); ce->addValue("jpg"); ce->addValue("gif"); ce->addDependency("HAVE_DOT"); //---- cs = cfg->addString( - "DOT_PATH", - "The tag DOT_PATH can be used to specify the path where the dot tool can be \n" - "found. If left blank, it is assumed the dot tool can be found in the path. \n" - ); + "DOT_PATH", + "The tag DOT_PATH can be used to specify the path where the dot tool can be \n" + "found. If left blank, it is assumed the dot tool can be found in the path." + ); cs->setWidgetType(ConfigString::Dir); cs->addDependency("HAVE_DOT"); //---- cl = cfg->addList( - "DOTFILE_DIRS", - "The DOTFILE_DIRS tag can be used to specify one or more directories that \n" - "contain dot files that are included in the documentation (see the \n" - "\\dotfile command). \n" - ); - cl->setWidgetType(ConfigList::Dir); + "DOTFILE_DIRS", + "The DOTFILE_DIRS tag can be used to specify one or more directories that \n" + "contain dot files that are included in the documentation (see the \n" + "\\dotfile command)." + ); cl->addDependency("HAVE_DOT"); + cl->setWidgetType(ConfigList::Dir); //---- ci = cfg->addInt( - "DOT_GRAPH_MAX_NODES", - "The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of \n" - "nodes that will be shown in the graph. If the number of nodes in a graph \n" - "becomes larger than this value, doxygen will truncate the graph, which is \n" - "visualized by representing a node as a red box. Note that doxygen if the \n" - "number of direct children of the root node in a graph is already larger than \n" - "DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note \n" - "that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. \n", - 0,10000, 50 + "DOT_GRAPH_MAX_NODES", + "The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of \n" + "nodes that will be shown in the graph. If the number of nodes in a graph \n" + "becomes larger than this value, doxygen will truncate the graph, which is \n" + "visualized by representing a node as a red box. Note that doxygen if the \n" + "number of direct children of the root node in a graph is already larger than \n" + "DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note \n" + "that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.", + 0,10000,50 ); ci->addDependency("HAVE_DOT"); //---- ci = cfg->addInt( - "MAX_DOT_GRAPH_DEPTH", - "The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the \n" - "graphs generated by dot. A depth value of 3 means that only nodes reachable \n" - "from the root by following a path via at most 3 edges will be shown. Nodes \n" - "that lay further from the root node will be omitted. Note that setting this \n" - "option to 1 or 2 may greatly reduce the computation time needed for large \n" - "code bases. Also note that the size of a graph can be further restricted by \n" - "DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.\n", - 0,1000,0 + "MAX_DOT_GRAPH_DEPTH", + "The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the \n" + "graphs generated by dot. A depth value of 3 means that only nodes reachable \n" + "from the root by following a path via at most 3 edges will be shown. Nodes \n" + "that lay further from the root node will be omitted. Note that setting this \n" + "option to 1 or 2 may greatly reduce the computation time needed for large \n" + "code bases. Also note that the size of a graph can be further restricted by \n" + "DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.", + 0,1000,0 ); ci->addDependency("HAVE_DOT"); //---- - cfg->addObsolete("MAX_DOT_GRAPH_WIDTH"); - //---- - cfg->addObsolete("MAX_DOT_GRAPH_HEIGHT"); - //---- cb = cfg->addBool( - "DOT_TRANSPARENT", - "Set the DOT_TRANSPARENT tag to YES to generate images with a transparent \n" - "background. This is disabled by default, because dot on Windows does not \n" - "seem to support this out of the box. Warning: Depending on the platform used, \n" - "enabling this option may lead to badly anti-aliased labels on the edges of \n" - "a graph (i.e. they become hard to read). \n", - FALSE - ); + "DOT_TRANSPARENT", + "Set the DOT_TRANSPARENT tag to YES to generate images with a transparent \n" + "background. This is disabled by default, because dot on Windows does not \n" + "seem to support this out of the box. Warning: Depending on the platform used, \n" + "enabling this option may lead to badly anti-aliased labels on the edges of \n" + "a graph (i.e. they become hard to read).", + FALSE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "DOT_MULTI_TARGETS", - "Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output \n" - "files in one run (i.e. multiple -o and -T options on the command line). This \n" - "makes dot run faster, but since only newer versions of dot (>1.8.10) \n" - "support this, this feature is disabled by default. \n", - FALSE - ); + "DOT_MULTI_TARGETS", + "Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output \n" + "files in one run (i.e. multiple -o and -T options on the command line). This \n" + "makes dot run faster, but since only newer versions of dot (>1.8.10) \n" + "support this, this feature is disabled by default.", + FALSE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "GENERATE_LEGEND", - "If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will \n" - "generate a legend page explaining the meaning of the various boxes and \n" - "arrows in the dot generated graphs. \n", - TRUE - ); + "GENERATE_LEGEND", + "If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will \n" + "generate a legend page explaining the meaning of the various boxes and \n" + "arrows in the dot generated graphs.", + TRUE + ); cb->addDependency("HAVE_DOT"); //---- cb = cfg->addBool( - "DOT_CLEANUP", - "If the DOT_CLEANUP tag is set to YES (the default) Doxygen will \n" - "remove the intermediate dot files that are used to generate \n" - "the various graphs. \n", - TRUE - ); + "DOT_CLEANUP", + "If the DOT_CLEANUP tag is set to YES (the default) Doxygen will \n" + "remove the intermediate dot files that are used to generate \n" + "the various graphs.", + TRUE + ); cb->addDependency("HAVE_DOT"); + //--------------------------------------------------------------------------- + cfg->addInfo("Search","Options related to the search engine"); + //--------------------------------------------------------------------------- - //----------------------------------------------------------------------------------------------- - cfg->addInfo( "Search","Configuration::additions related to the search engine "); - //----------------------------------------------------------------------------------------------- + //---- cb = cfg->addBool( - "SEARCHENGINE", - "The SEARCHENGINE tag specifies whether or not a search engine should be \n" - "used. If set to NO the values of all tags below this one will be ignored. \n", - FALSE - ); + "SEARCHENGINE", + "The SEARCHENGINE tag specifies whether or not a search engine should be \n" + "used. If set to NO the values of all tags below this one will be ignored.", + FALSE + ); + //---- + cfg->addObsolete("USE_WINDOWS_ENCODING"); + //---- + cfg->addObsolete("DETAILS_AT_TOP"); + //---- + cfg->addObsolete("QTHELP_FILE"); + //---- + cfg->addObsolete("QTHELP_CONFIG"); + //---- + cfg->addObsolete("DOXYGEN2QTHELP_LOC"); + //---- + cfg->addObsolete("MAX_DOT_GRAPH_WIDTH"); + //---- + cfg->addObsolete("MAX_DOT_GRAPH_HEIGHT"); //---- cfg->addObsolete("CGI_NAME"); //---- @@ -2173,7 +2109,4 @@ void addConfigOptions(Config *cfg) cfg->addObsolete("BIN_ABSPATH"); //---- cfg->addObsolete("EXT_DOC_PATHS"); - - // The IMAGE_PATTERNS tag is now officially obsolete. - } diff --git a/src/dot.cpp b/src/dot.cpp index 3f0a4ff..ece1638 100644 --- a/src/dot.cpp +++ b/src/dot.cpp @@ -1968,7 +1968,7 @@ QCString DotClassGraph::writeGraph(QTextStream &out, } else { - out << "\\includegraphics[width=" << width/2 << "pt]"; + out << "\\includegraphics[width=" << width << "pt]"; } out << "{" << baseName << "}\n" "\\end{center}\n" diff --git a/src/doxygen.cpp b/src/doxygen.cpp index b919521..03ef3ff 100644 --- a/src/doxygen.cpp +++ b/src/doxygen.cpp @@ -9295,13 +9295,17 @@ void readConfiguration(int argc, char **argv) if (genConfig) { - checkConfiguration(); - generateConfigFile(configName,shortList); if (g_dumpConfigAsXML) { + checkConfiguration(); + generateConfigFile(configName,shortList); dumpConfigAsXML(); exit(0); } + else + { + generateConfigFile(configName,shortList); + } cleanUpDoxygen(); exit(0); } diff --git a/src/doxygen.css b/src/doxygen.css index 7561c63..3767dc9 100644 --- a/src/doxygen.css +++ b/src/doxygen.css @@ -68,6 +68,10 @@ a.qindexHL { border: 1px double #9295C2; } +.contents a.qindexHL:visited { + color: #ffffff; +} + a.el { font-weight: bold; } diff --git a/src/doxygen_css.h b/src/doxygen_css.h index 591c2bf..99c7b5d 100644 --- a/src/doxygen_css.h +++ b/src/doxygen_css.h @@ -68,6 +68,10 @@ " border: 1px double #9295C2;\n" "}\n" "\n" +".contents a.qindexHL:visited {\n" +" color: #ffffff;\n" +"}\n" +"\n" "a.el {\n" " font-weight: bold;\n" "}\n" diff --git a/src/lang_cfg.h b/src/lang_cfg.h index 2855c93..e955bb0 100644 --- a/src/lang_cfg.h +++ b/src/lang_cfg.h @@ -33,3 +33,4 @@ #define LANG_AR #define LANG_FA #define LANG_VI +#define LANG_TR diff --git a/src/language.cpp b/src/language.cpp index ec9a9c7..f5485a4 100644 --- a/src/language.cpp +++ b/src/language.cpp @@ -137,6 +137,9 @@ #ifdef LANG_VI #include "translator_vi.h" #endif +#ifdef LANG_TR +#include "translator_tr.h" +#endif #endif // !ENGLISH_ONLY #define L_EQUAL(a) !stricmp(langName,a) @@ -382,6 +385,12 @@ bool setTranslator(const char *langName) theTranslator=new TranslatorVietnamese; } #endif +#ifdef LANG_TR + else if (L_EQUAL("turkish")) + { + theTranslator=new TranslatorTurkish; + } +#endif #endif // ENGLISH_ONLY else // use the default language (i.e. english) { @@ -24,6 +24,7 @@ #include <stdio.h> #include <assert.h> #include <ctype.h> +#include <errno.h> #include "qtbc.h" #include <qarray.h> @@ -53,6 +54,8 @@ struct FileState { int lineNr; FILE *filePtr; + FILE *oldYYin; + bool isPlainFile; YY_BUFFER_STATE bufState; QCString fileName; }; @@ -171,9 +174,9 @@ static Define *isDefined(const char *name) return 0; } -static FILE *checkAndOpenFile(const QCString &fileName) +static FileState *checkAndOpenFile(const QCString &fileName) { - FILE *f = 0; + FileState *fs = 0; //printf("checkAndOpenFile(%s)\n",absName.data()); QFileInfo fi(fileName); if (fi.exists() && fi.isFile()) @@ -183,7 +186,6 @@ static FILE *checkAndOpenFile(const QCString &fileName) QStack<FileState> tmpStack; g_includeStack.setAutoDelete(FALSE); - FileState *fs; bool alreadyIncluded=FALSE; while ((fs=g_includeStack.pop())) { @@ -198,24 +200,33 @@ static FILE *checkAndOpenFile(const QCString &fileName) if (alreadyIncluded) return 0; + fs = new FileState; QCString filterName = getFileFilter(absName); if (!filterName.isEmpty()) { + fs->isPlainFile = FALSE; QCString cmd = filterName+" \""+absName+"\""; - f=portable_popen(cmd,"r"); - if (!f) err("Error: could not execute filter %s\n",cmd.data()); + fs->filePtr=portable_popen(cmd,"r"); + if (!fs->filePtr) err("Error: could not execute filter %s\n",cmd.data()); } else { - f=fopen(absName,"r"); - if (!f) err("Error: could not open file %s for reading\n",absName.data()); + fs->isPlainFile = TRUE; + fs->filePtr=fopen(absName,"r"); + if (!fs->filePtr) err("Error: could not open file %s for reading\n",absName.data()); + } + if (!fs->filePtr) // error -> cleanup + { + delete fs; + fs=0; } + fs->oldYYin = preYYin; } - return f; + return fs; } -static FILE *findFile(const char *fileName,bool localInclude) +static FileState *findFile(const char *fileName,bool localInclude) { //printf("** findFile(%s,%d) g_yyFileName=%s\n",fileName,localInclude,g_yyFileName.data()); if (localInclude && !g_yyFileName.isEmpty()) @@ -224,12 +235,12 @@ static FILE *findFile(const char *fileName,bool localInclude) if (fi.exists()) { QCString absName = QCString(fi.dirPath(TRUE).data())+"/"+fileName; - FILE *f = checkAndOpenFile(absName); - if (f) + FileState *fs = checkAndOpenFile(absName); + if (fs) { setFileName(absName); g_yyLineNr=1; - return f; + return fs; } } } @@ -241,12 +252,12 @@ static FILE *findFile(const char *fileName,bool localInclude) while (s) { QCString absName = (QCString)s+"/"+fileName; - FILE *f = checkAndOpenFile(absName); - if (f) + FileState *fs = checkAndOpenFile(absName); + if (fs) { setFileName(absName); g_yyLineNr=1; - return f; + return fs; } s=g_pathList->next(); @@ -1116,14 +1127,14 @@ static void readIncludeFile(const QCString &inc) // extract include path+name QCString incFileName=inc.mid(s,i-s).stripWhiteSpace(); - FILE *f; QCString oldFileName = g_yyFileName.copy(); FileDef *oldFileDef = g_yyFileDef; int oldLineNr = g_yyLineNr; //printf("Searching for `%s'\n",incFileName.data()); // findFile will overwrite g_yyFileDef if found - if ((f=findFile(incFileName,localInclude))) // see if the include file can be found + FileState *fs; + if ((fs=findFile(incFileName,localInclude))) // see if the include file can be found { //printf("Found include file!\n"); if (Debug::isFlagSet(Debug::Preprocessor)) @@ -1142,11 +1153,9 @@ static void readIncludeFile(const QCString &inc) g_yyFileDef->addIncludedByDependency(oldFileDef,oldFileDef->docName(),localInclude,g_isImported); } } - FileState *fs=new FileState; fs->bufState=YY_CURRENT_BUFFER; fs->lineNr=oldLineNr; fs->fileName=oldFileName; - fs->filePtr=f; // push the state on the stack g_includeStack.push(fs); // set the scanner to the include file @@ -1158,7 +1167,7 @@ static void readIncludeFile(const QCString &inc) outputArray(lineStr.data(),lineStr.length()); //fprintf(stderr,"Switching to include file %s\n",incFileName.data()); - preYYin=f; + preYYin=fs->filePtr; yy_switch_to_buffer(yy_create_buffer(preYYin, YY_BUF_SIZE)); } else @@ -1253,7 +1262,7 @@ static char resolveTrigraph(char c) static int yyread(char *buf,int max_size) { - int len = fread( buf, 1, max_size, yyin ); + int len = fread( buf, 1, max_size, preYYin ); if (len==0 && ferror( yyin )) { yy_fatal_error( "input in flex scanner failed" ); @@ -2175,14 +2184,27 @@ CHARLIT (("'"\\[0-7]{1,3}"'")|("'"\\."'")|("'"[^'\\\n]{1,4}"'")) { FileState *fs=g_includeStack.pop(); //fileDefineCache->merge(g_yyFileName,fs->fileName); - if (getFileFilter(fs->fileName.data()).isEmpty()) - fclose(fs->filePtr); + if (fs->isPlainFile) + { + if (fs->filePtr && fclose(fs->filePtr)!=0) + { + err("Error: could not close file %s: %s\n",fs->fileName.data(),strerror(errno)); + } + fs->filePtr=0; + } else - portable_pclose(fs->filePtr); + { + if (fs->filePtr && portable_pclose(fs->filePtr)!=0) + { + err("Error: could not close pipe: %s\n",strerror(errno)); + } + fs->filePtr=0; + } YY_BUFFER_STATE oldBuf = YY_CURRENT_BUFFER; yy_switch_to_buffer( fs->bufState ); yy_delete_buffer( oldBuf ); g_yyLineNr=fs->lineNr; + preYYin = fs->oldYYin; setFileName(fs->fileName.copy()); //fprintf(stderr,"######## FileName %s\n",g_yyFileName.data()); diff --git a/src/scanner.l b/src/scanner.l index 7704ef8..58c43fc 100644 --- a/src/scanner.l +++ b/src/scanner.l @@ -4700,7 +4700,7 @@ TYPEDEFPREFIX (("typedef"{BN}+)?)((("volatile"|"const"){BN}+)?) current->args += ' '; current->args += name; } -<ClassVar,Bases>\n/{BN}* { +<ClassVar,Bases>\n/{BN}*[^{,] { if (!insideObjC) { REJECT; @@ -4708,7 +4708,7 @@ TYPEDEFPREFIX (("typedef"{BN}+)?)((("volatile"|"const"){BN}+)?) else { yyLineNr++; - //unput('{'); + unput('{'); } } <ClassVar,Bases>"@end" { // empty ObjC interface diff --git a/src/translator_tr.h b/src/translator_tr.h new file mode 100644 index 0000000..131e1c4 --- /dev/null +++ b/src/translator_tr.h @@ -0,0 +1,1781 @@ +/****************************************************************************** + * + * + * + * Copyright (C) 1997-2008 by Dimitri van Heesch. + * + * Permission to use, copy, modify, and distribute this software and its + * documentation under the terms of the GNU General Public License is hereby + * granted. No representations are made about the suitability of this software + * for any purpose. It is provided "as is" without express or implied warranty. + * See the GNU General Public License for more details. + * + * Documents produced by Doxygen are derivative works derived from the + * input used in their production; they are not affected by this license. + * + */ + +#ifndef TRANSLATOR_TR_H +#define TRANSLATOR_TR_H + +/*! + When defining a translator class for the new language, follow + the description in the documentation. One of the steps says + that you should copy the translator_en.h (this) file to your + translator_xx.h new file. Your new language should use the + Translator class as the base class. This means that you need to + implement exactly the same (pure virtual) methods as the + TranslatorEnglish does. Because of this, it is a good idea to + start with the copy of TranslatorEnglish and replace the strings + one by one. + + It is not necessary to include "translator.h" or + "translator_adapter.h" here. The files are included in the + language.cpp correctly. Not including any of the mentioned + files frees the maintainer from thinking about whether the + first, the second, or both files should be included or not, and + why. This holds namely for localized translators because their + base class is changed occasionaly to adapter classes when the + Translator class changes the interface, or back to the + Translator class (by the local maintainer) when the localized + translator is made up-to-date again. +*/ +class TranslatorTurkish : public Translator +{ + public: + + // --- Language control methods ------------------- + + /*! Used for identification of the language. The identification + * should not be translated. It should be replaced by the name + * of the language in English using lower-case characters only + * (e.g. "czech", "japanese", "russian", etc.). It should be equal to + * the identification used in language.cpp. + */ + virtual QCString idLanguage() + { return "turkish"; } + + /*! Used to get the LaTeX command(s) for the language support. + * This method should return string with commands that switch + * LaTeX to the desired language. For example + * <pre>"\\usepackage[german]{babel}\n" + * </pre> + * or + * <pre>"\\usepackage{polski}\n" + * "\\usepackage[latin2]{inputenc}\n" + * "\\usepackage[T1]{fontenc}\n" + * </pre> + * + * The English LaTeX does not use such commands. Because of this + * the empty string is returned in this implementation. + */ + virtual QCString latexLanguageSupportCommand() + { + return ""; + } + + /*! return the language charset. This will be used for the HTML output */ + virtual QCString idLanguageCharset() + { + return "iso-8859-9"; + } + + // --- Language translation methods ------------------- + + /*! used in the compound documentation before a list of related fonksiyonlar. */ + virtual QCString trRelatedFunctions() + { return "İlgili Fonksiyonlar"; } + + /*! subscript for the related fonksiyonlar. */ + virtual QCString trRelatedSubscript() + { return "(Not: Bu fonksiyonlar üye fonksiyon değildir.)"; } + + /*! header that is put before the detailed description of files, classes and namespaces. */ + virtual QCString trDetailedDescription() + { return "Ayrıntılı tanımlama"; } + + /*! header that is put before the list of typedefs. */ + virtual QCString trMemberTypedefDocumentation() + { return "Üye Typedef Dokümantasyonu"; } + + /*! header that is put before the list of enumerations. */ + virtual QCString trMemberEnumerationDocumentation() + { return "Üye Enümerasyon Dokümantasyonu"; } + + /*! header that is put before the list of member fonksiyonlar. */ + virtual QCString trMemberFunctionDocumentation() + { return "Üye Fonksiyon Dokümantasyonu"; } + + /*! header that is put before the list of member attributes. */ + virtual QCString trMemberDataDocumentation() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Alan Dokümantasyonu"; + } + else + { + return "Üye Veri Dokümantasyonu"; + } + } + + /*! this is the text of a link put after brief descriptions. */ + virtual QCString trMore() + { return "Ayrıntılar..."; } + + /*! put in the class documentation */ + virtual QCString trListOfAllMembers() + { return "Tüm üyelerin listesi."; } + + /*! used as the title of the "list of all members" page of a class */ + virtual QCString trMemberList() + { return "Üye Listesi"; } + + /*! this is the first part of a sentence that is followed by a class name */ + virtual QCString trThisIsTheListOfAllMembers() + { return "Şu sınıfın tüm üyelerinin listesidir: "; } + + /*! this is the remainder of the sentence after the class name */ + virtual QCString trIncludingInheritedMembers() + { return " (kalıtımla gelen üyeleri de içerir)."; } + + /*! this is put at the author sections at the bottom of man pages. + * parameter s is name of the project name. + */ + virtual QCString trGeneratedAutomatically(const char *s) + { QCString result="Doxygen tarafından"; + if (s) result+=s+(QCString)" için "; + result+=" kaynak koddan otomatik üretilmiştir."; + return result; + } + + /*! put after an enum name in the list of all members */ + virtual QCString trEnumName() + { return "enum adı"; } + + /*! put after an enum value in the list of all members */ + virtual QCString trEnumValue() + { return "enum değeri"; } + + /*! put after an undocumented member in the list of all members */ + virtual QCString trDefinedIn() + { return "tanımlandığı yer"; } + + // quick reference sections + + /*! This is put above each page as a link to the list of all groups of + * compounds or files (see the \\group command). + */ + virtual QCString trModules() + { return "Modüller"; } + + /*! This is put above each page as a link to the class hierarchy */ + virtual QCString trClassHierarchy() + { return "Sınıf Hiyerarşisi"; } + + /*! This is put above each page as a link to the list of annotated classes */ + virtual QCString trCompoundList() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Veri Yapıları"; + } + else + { + return "Sınıf Listesi"; + } + } + + /*! This is put above each page as a link to the list of documented files */ + virtual QCString trFileList() + { return "Dosya Listesi"; } + + /*! This is put above each page as a link to all members of compounds. */ + virtual QCString trCompoundMembers() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Veri Alanları"; + } + else + { + return "Sınıf Üyeleri"; + } + } + + /*! This is put above each page as a link to all members of files. */ + virtual QCString trFileMembers() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Globaller"; + } + else + { + return "Dosya Üyeleri"; + } + } + + /*! This is put above each page as a link to all related pages. */ + virtual QCString trRelatedPages() + { return "İlgili Sayfalar"; } + + /*! This is put above each page as a link to all examples. */ + virtual QCString trExamples() + { return "Örnekler"; } + + /*! This is put above each page as a link to the search engine. */ + virtual QCString trSearch() + { return "Ara"; } + + /*! This is an introduction to the class hierarchy. */ + virtual QCString trClassHierarchyDescription() + { return "Bu kalıtım listesi tamamen olmasa da yaklaşık " + "olarak alfabetik sıraya konulmuştur:"; + } + + /*! This is an introduction to the list with all files. */ + virtual QCString trFileListDescription(bool extractAll) + { + QCString result="Bu liste tüm "; + if (!extractAll) result+="dokümante edilmiş "; + result+="dosyaları kısa açıklamalarıyla göstermektedir:"; + return result; + } + + /*! This is an introduction to the annotated compound list. */ + virtual QCString trCompoundListDescription() + { + + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Kısa tanımlarıyla birlikte veri yapıları:"; + } + else + { + return "Kısa tanımlarıyla sınıflar, yapılar (struct), " + "birleşimler(union) ve arayüzler:"; + } + } + + /*! This is an introduction to the page with all class members. */ + virtual QCString trCompoundMembersDescription(bool extractAll) + { + QCString result="Bu liste tüm "; + if (!extractAll) + { + result+="dokümante edilmiş "; + } + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + result+="yapı(struct) ve birleşim(union) yapılarını içerir"; + } + else + { + result+="sınıf üyelerini içerir"; + } + result+=" ve "; + if (!extractAll) + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + result+="her alanı yapı(struct)/birleşim(union) dokümantasyonuna bağlar:"; + } + else + { + result+="her üye için sınıf dokümantasyonuna bağlar:"; + } + } + else + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + result+="ait olduğu yapı(struct)/birleşime(union) bağlar:"; + } + else + { + result+="ait olduğu sınıfa bağlar:"; + } + } + return result; + } + + /*! This is an introduction to the page with all file members. */ + virtual QCString trFileMembersDescription(bool extractAll) + { + QCString result="Bu liste tüm "; + if (!extractAll) result+="dokümante edilmiş "; + + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + result+="fonksiyonları, değişkenleri, makroları, enümerasyonları ve typedef\'leri içerir"; + } + else + { + result+="dosya üyelerini içerir"; + } + result+=" ve "; + if (extractAll) + result+="ait olduğu dosyalar bağlar:"; + else + result+="dokümantasyona bağlar:"; + return result; + } + + /*! This is an introduction to the page with the list of all examples */ + virtual QCString trExamplesDescription() + { return "Tüm örneklerin listesi aşağıdadır:"; } + + /*! This is an introduction to the page with the list of related pages */ + virtual QCString trRelatedPagesDescription() + { return "İlgili tüm dokümantasyon sayfalarının listesi aşağıdadır:"; } + + /*! This is an introduction to the page with the list of class/file groups */ + virtual QCString trModulesDescription() + { return "Tüm modüllerin listesi aşağıdadır:"; } + + // index titles (the project name is prepended for these) + + /*! This is used in HTML as the title of index.html. */ + virtual QCString trDocumentation() + { return "Dokümantasyonu"; } + + /*! This is used in LaTeX as the title of the chapter with the + * index of all groups. + */ + virtual QCString trModuleIndex() + { return "Modül İndeksi"; } + + /*! This is used in LaTeX as the title of the chapter with the + * class hierarchy. + */ + virtual QCString trHierarchicalIndex() + { return "Hiyerarşik İndeksi"; } + + /*! This is used in LaTeX as the title of the chapter with the + * annotated compound index. + */ + virtual QCString trCompoundIndex() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Veri Yapıları İndeksi"; + } + else + { + return "Sınıf İndeksi"; + } + } + + /*! This is used in LaTeX as the title of the chapter with the + * list of all files. + */ + virtual QCString trFileIndex() + { return "Dosya İndeksi"; } + + /*! This is used in LaTeX as the title of the chapter containing + * the documentation of all groups. + */ + virtual QCString trModuleDocumentation() + { return "Modül Dokümantasyonu"; } + + /*! This is used in LaTeX as the title of the chapter containing + * the documentation of all classes, structs and unions. + */ + virtual QCString trClassDocumentation() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Veri Yapıları Dokümantasyonu"; + } + else + { + return "Sınıf Dokümantasyonu"; + } + } + + /*! This is used in LaTeX as the title of the chapter containing + * the documentation of all files. + */ + virtual QCString trFileDocumentation() + { return "Dosya Dokümantasyonu"; } + + /*! This is used in LaTeX as the title of the chapter containing + * the documentation of all examples. + */ + virtual QCString trExampleDocumentation() + { return "Örnek Dokümantasyonu"; } + + /*! This is used in LaTeX as the title of the chapter containing + * the documentation of all related pages. + */ + virtual QCString trPageDocumentation() + { return "Sayfa Dokümantasyonu"; } + + /*! This is used in LaTeX as the title of the document */ + virtual QCString trReferenceManual() + { return "Referans Kitabı"; } + + /*! This is used in the documentation of a file as a header before the + * list of defines + */ + virtual QCString trDefines() + { return "Makrolar"; } + + /*! This is used in the documentation of a file as a header before the + * list of function prototypes + */ + virtual QCString trFuncProtos() + { return "Fonksiyon Prototipleri"; } + + /*! This is used in the documentation of a file as a header before the + * list of typedefs + */ + virtual QCString trTypedefs() + { return "Typedef\'ler"; } + + /*! This is used in the documentation of a file as a header before the + * list of enumerations + */ + virtual QCString trEnumerations() + { return "Enümerasyonlar"; } + + /*! This is used in the documentation of a file as a header before the + * list of (global) functions + */ + virtual QCString trFunctions() + { return "Fonksiyonlar"; } + + /*! This is used in the documentation of a file as a header before the + * list of (global) variables + */ + virtual QCString trVariables() + { return "Değişkenler"; } + + /*! This is used in the documentation of a file as a header before the + * list of (global) variables + */ + virtual QCString trEnumerationValues() + { return "Enümeratör"; } + + /*! This is used in the documentation of a file before the list of + * documentation blocks for defines + */ + virtual QCString trDefineDocumentation() + { return "Makro Dokümantasyonu"; } + + /*! This is used in the documentation of a file/namespace before the list + * of documentation blocks for function prototypes + */ + virtual QCString trFunctionPrototypeDocumentation() + { return "Fonksiyon Prototip Dokümantasyonu"; } + + /*! This is used in the documentation of a file/namespace before the list + * of documentation blocks for typedefs + */ + virtual QCString trTypedefDocumentation() + { return "Typedef Dokümantasyonu"; } + + /*! This is used in the documentation of a file/namespace before the list + * of documentation blocks for enumeration types + */ + virtual QCString trEnumerationTypeDocumentation() + { return "Enümerasyon Tipi Dokümantasyonu"; } + + /*! This is used in the documentation of a file/namespace before the list + * of documentation blocks for functions + */ + virtual QCString trFunctionDocumentation() + { return "Fonksiyon Dokümantasyonu"; } + + /*! This is used in the documentation of a file/namespace before the list + * of documentation blocks for variables + */ + virtual QCString trVariableDocumentation() + { return "Değişken Dokümantasyonu"; } + + /*! This is used in the documentation of a file/namespace/group before + * the list of links to documented compounds + */ + virtual QCString trCompounds() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Veri Yapıları"; + } + else + { + return "Sınıflar"; + } + } + + /*! This is used in the standard footer of each page and indicates when + * the page was generated + */ + virtual QCString trGeneratedAt(const char *date,const char *projName) + { + QCString result=projName+(QCString)" için "+date; + if (projName) result+=(QCString)" tarihinde "; + result+=(QCString)" üreten: "; + return result; + } + /*! This is part of the sentence used in the standard footer of each page. + */ + virtual QCString trWrittenBy() + { + return "yazan"; + } + + /*! this text is put before a class diagram */ + virtual QCString trClassDiagram(const char *clName) + { + return clName+(QCString)" için kalıtım şeması:"; + } + + /*! this text is generated when the \\internal command is used. */ + virtual QCString trForInternalUseOnly() + { return "İç kullanıma ayrılmıştır."; } + + /*! this text is generated when the \\warning command is used. */ + virtual QCString trWarning() + { return "Uyarı"; } + + /*! this text is generated when the \\version command is used. */ + virtual QCString trVersion() + { return "Sürüm"; } + + /*! this text is generated when the \\date command is used. */ + virtual QCString trDate() + { return "Tarih"; } + + /*! this text is generated when the \\return command is used. */ + virtual QCString trReturns() + { return "Döndürdüğü değer"; } + + /*! this text is generated when the \\sa command is used. */ + virtual QCString trSeeAlso() + { return "Ayrıca Bakınız"; } + + /*! this text is generated when the \\param command is used. */ + virtual QCString trParameters() + { return "Parametreler"; } + + /*! this text is generated when the \\exception command is used. */ + virtual QCString trExceptions() + { return "İstisnalar"; } + + /*! this text is used in the title page of a LaTeX document. */ + virtual QCString trGeneratedBy() + { return "Oluşturan"; } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-990307 +////////////////////////////////////////////////////////////////////////// + + /*! used as the title of page containing all the index of all namespaces. */ + virtual QCString trNamespaceList() + { return "Namespace Listesi"; } + + /*! used as an introduction to the namespace list */ + virtual QCString trNamespaceListDescription(bool extractAll) + { + QCString result="Tüm "; + if (!extractAll) result+="dokümante edilmiş "; + result+="namespace\'lerin kısa tanımlarıyla listesi aşağıdadır:"; + return result; + } + + /*! used in the class documentation as a header before the list of all + * friends of a class + */ + virtual QCString trFriends() + { return "Arkadaşları"; } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-990405 +////////////////////////////////////////////////////////////////////////// + + /*! used in the class documentation as a header before the list of all + * related classes + */ + virtual QCString trRelatedFunctionDocumentation() + { return "Arkadaş Ve İlgili Fonksiyon Dokümantasyonu"; } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-990425 +////////////////////////////////////////////////////////////////////////// + + /*! used as the title of the HTML page of a class/struct/union */ + virtual QCString trCompoundReference(const char *clName, + ClassDef::CompoundType compType, + bool isTemplate) + { + QCString result=(QCString)clName; + switch(compType) + { + case ClassDef::Class: result+=" Sınıf"; break; + case ClassDef::Struct: result+=" Yapı(Struct)"; break; + case ClassDef::Union: result+=" Birleşim(Union)"; break; + case ClassDef::Interface: result+=" Arayüz(Interface)"; break; + case ClassDef::Protocol: result+=" Protokol"; break; + case ClassDef::Category: result+=" Kategori"; break; + case ClassDef::Exception: result+=" İstisna"; break; + } + if (isTemplate) result+=" Şablon"; + result+=" Referans"; + return result; + } + + /*! used as the title of the HTML page of a file */ + virtual QCString trFileReference(const char *fileName) + { + QCString result=fileName; + result+=" Dosya Referansı"; + return result; + } + + /*! used as the title of the HTML page of a namespace */ + virtual QCString trNamespaceReference(const char *namespaceName) + { + QCString result=namespaceName; + result+=" Namespace Referansı"; + return result; + } + + virtual QCString trPublicMembers() + { return "Public Üye Fonksiyonlar"; } + virtual QCString trPublicSlots() + { return "Public Slotlar"; } + virtual QCString trSignals() + { return "Sinyaller"; } + virtual QCString trStaticPublicMembers() + { return "Statik Public Üye Fonksiyonlar"; } + virtual QCString trProtectedMembers() + { return "Korumalı Üye Fonksiyonlar"; } + virtual QCString trProtectedSlots() + { return "Korumalı Slotlar"; } + virtual QCString trStaticProtectedMembers() + { return "Statik Korumalı Üye Fonksiyonlar"; } + virtual QCString trPrivateMembers() + { return "Özel Üye Fonksiyonlar"; } + virtual QCString trPrivateSlots() + { return "Özel Slotlar"; } + virtual QCString trStaticPrivateMembers() + { return "Statik Özel Üye Fonksiyonlar"; } + + /*! this function is used to produce a comma-separated list of items. + * use generateMarker(i) to indicate where item i should be put. + */ + virtual QCString trWriteList(int numEntries) + { + QCString result; + int i; + // the inherits list contain `numEntries' classes + for (i=0;i<numEntries;i++) + { + // use generateMarker to generate placeholders for the class links! + result+=generateMarker(i); // generate marker for entry i in the list + // (order is left to right) + + if (i!=numEntries-1) // not the last entry, so we need a separator + { + if (i<numEntries-2) // not the fore last entry + result+=", "; + else // the fore last entry + result+=" ve "; + } + } + return result; + } + + /*! used in class documentation to produce a list of base classes, + * if class diagrams are disabled. + */ + virtual QCString trInheritsList(int numEntries) + { + return "Şu sınıflardan türemiştir : "+trWriteList(numEntries)+"."; + } + + /*! used in class documentation to produce a list of super classes, + * if class diagrams are disabled. + */ + virtual QCString trInheritedByList(int numEntries) + { + return "Şu sınıfların atasıdır : "+trWriteList(numEntries)+"."; + } + + /*! used in member documentation blocks to produce a list of + * members that are hidden by this one. + */ + virtual QCString trReimplementedFromList(int numEntries) + { + return "Şu üyeleri yeniden tanımlar : "+trWriteList(numEntries)+"."; + } + + /*! used in member documentation blocks to produce a list of + * all member that overwrite the implementation of this member. + */ + virtual QCString trReimplementedInList(int numEntries) + { + return "Şu üyeler tarafından yeniden tanımlanmıştır : "+trWriteList(numEntries)+"."; + } + + /*! This is put above each page as a link to all members of namespaces. */ + virtual QCString trNamespaceMembers() + { return "Namespace Üyeleri"; } + + /*! This is an introduction to the page with all namespace members */ + virtual QCString trNamespaceMemberDescription(bool extractAll) + { + QCString result="Bu liste tüm "; + if (!extractAll) result+="dokümante edilmiş "; + result+="namespace üyelerini listeler ve "; + if (extractAll) + result+="her üye için üye dokümantasyonuna bağlar:"; + else + result+="ait olduğu namespace\'lere bağlar:"; + return result; + } + /*! This is used in LaTeX as the title of the chapter with the + * index of all namespaces. + */ + virtual QCString trNamespaceIndex() + { return "Namespace İndeksi"; } + + /*! This is used in LaTeX as the title of the chapter containing + * the documentation of all namespaces. + */ + virtual QCString trNamespaceDocumentation() + { return "Namespace Dokümantasyonu"; } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-990522 +////////////////////////////////////////////////////////////////////////// + + /*! This is used in the documentation before the list of all + * namespaces in a file. + */ + virtual QCString trNamespaces() + { return "Namespace\'ler"; } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-990728 +////////////////////////////////////////////////////////////////////////// + + /*! This is put at the bottom of a class documentation page and is + * followed by a list of files that were used to generate the page. + */ + virtual QCString trGeneratedFromFiles(ClassDef::CompoundType compType, + bool single) + { // here s is one of " Class", " Struct" or " Union" + // single is true implies a single file + QCString result=(QCString)"Bu "; + switch(compType) + { + case ClassDef::Class: result+="sınıf"; break; + case ClassDef::Struct: result+="yapı(struct)"; break; + case ClassDef::Union: result+="birleşim(union)"; break; + case ClassDef::Interface: result+="arayüz(interface)"; break; + case ClassDef::Protocol: result+="protokol"; break; + case ClassDef::Category: result+="kategori"; break; + case ClassDef::Exception: result+="istisna"; break; + } + result+=" için dokümantasyon aşağıdaki dosya"; + if (single) result+=""; else result+="lar"; + result+="dan üretilmiştir:"; + return result; + } + + /*! This is in the (quick) index as a link to the alphabetical compound + * list. + */ + virtual QCString trAlphabeticalList() + { return "Alfabetik Liste"; } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-990901 +////////////////////////////////////////////////////////////////////////// + + /*! This is used as the heading text for the retval command. */ + virtual QCString trReturnValues() + { return "Döndürdüğü değerler"; } + + /*! This is in the (quick) index as a link to the main page (index.html) + */ + virtual QCString trMainPage() + { return "Ana Sayfa"; } + + /*! This is used in references to page that are put in the LaTeX + * documentation. It should be an abbreviation of the word page. + */ + virtual QCString trPageAbbreviation() + { return "sf."; } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-991003 +////////////////////////////////////////////////////////////////////////// + + virtual QCString trDefinedAtLineInSourceFile() + { + return "@1 dosyasının @0 numaralı satırında tanımlanmıştır."; + } + virtual QCString trDefinedInSourceFile() + { + return "@0 dosyasında tanımlanmıştır."; + } + +////////////////////////////////////////////////////////////////////////// +// new since 0.49-991205 +////////////////////////////////////////////////////////////////////////// + + virtual QCString trDeprecated() + { + return "Kullanımdan kalkmıştır"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.0.0 +////////////////////////////////////////////////////////////////////////// + + /*! this text is put before a collaboration diagram */ + virtual QCString trCollaborationDiagram(const char *clName) + { + return clName+(QCString)" için işbirliği (collaboration) şeması:"; + } + /*! this text is put before an include dependency graph */ + virtual QCString trInclDepGraph(const char *fName) + { + return fName+(QCString)" için içerme bağımlılık grafiği:"; + } + /*! header that is put before the list of constructor/destructors. */ + virtual QCString trConstructorDocumentation() + { + return "Constructor & Destructor Dokümantasyonu"; + } + /*! Used in the file documentation to point to the corresponding sources. */ + virtual QCString trGotoSourceCode() + { + return "Bu dosyanın kaynak koduna git."; + } + /*! Used in the file sources to point to the corresponding documentation. */ + virtual QCString trGotoDocumentation() + { + return "Bu dosyanın dokümantasyonuna git."; + } + /*! Text for the \\pre command */ + virtual QCString trPrecondition() + { + return "Ön şart"; + } + /*! Text for the \\post command */ + virtual QCString trPostcondition() + { + return "Son şart (Postcondition)"; + } + /*! Text for the \\invariant command */ + virtual QCString trInvariant() + { + return "Değişmez(Invariant)"; + } + /*! Text shown before a multi-line variable/enum initialization */ + virtual QCString trInitialValue() + { + return "İlk değer:"; + } + /*! Text used the source code in the file index */ + virtual QCString trCode() + { + return "kod"; + } + virtual QCString trGraphicalHierarchy() + { + return "Grafiksel Sınıf Hiyerarşisi"; + } + virtual QCString trGotoGraphicalHierarchy() + { + return "Grafiksel sınıf hiyerarşisine git"; + } + virtual QCString trGotoTextualHierarchy() + { + return "Metinsel sınıf hiyerarşisine git"; + } + virtual QCString trPageIndex() + { + return "Sayfa İndeksi"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.1.0 +////////////////////////////////////////////////////////////////////////// + + virtual QCString trNote() + { + return "Not"; + } + virtual QCString trPublicTypes() + { + return "Public Tipler"; + } + virtual QCString trPublicAttribs() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Veri Alanları"; + } + else + { + return "Public Özellikler(attribute)"; + } + } + virtual QCString trStaticPublicAttribs() + { + return "Statik Public Özellikler(attribute)"; + } + virtual QCString trProtectedTypes() + { + return "Korumalı Tipler"; + } + virtual QCString trProtectedAttribs() + { + return "Korumalı Özellikler(attribute)"; + } + virtual QCString trStaticProtectedAttribs() + { + return "Statik Korumalı Attributes"; + } + virtual QCString trPrivateTypes() + { + return "Özel Tipler"; + } + virtual QCString trPrivateAttribs() + { + return "Özel Özellikler(attribute)"; + } + virtual QCString trStaticPrivateAttribs() + { + return "Statik Özel Özellikler(attribute)"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.1.3 +////////////////////////////////////////////////////////////////////////// + + /*! Used as a marker that is put before a \\todo item */ + virtual QCString trTodo() + { + return "Yapılacak"; + } + /*! Used as the header of the todo list */ + virtual QCString trTodoList() + { + return "Yapılacaklar Listesi"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.1.4 +////////////////////////////////////////////////////////////////////////// + + virtual QCString trReferencedBy() + { + return "Referans veren"; + } + virtual QCString trRemarks() + { + return "Dipnotlar"; + } + virtual QCString trAttention() + { + return "Dikkat"; + } + virtual QCString trInclByDepGraph() + { + return "Bu şekil hangi dosyaların doğrudan ya da " + "dolaylı olarak bu dosyayı içerdiğini gösterir:"; + } + virtual QCString trSince() + { + return "Şu zamandan beri"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.1.5 +////////////////////////////////////////////////////////////////////////// + + /*! title of the graph legend page */ + virtual QCString trLegendTitle() + { + return "Şekil Lejantı"; + } + /*! page explaining how the dot graph's should be interpreted + * The %A in the text below are to prevent link to classes called "A". + */ + virtual QCString trLegendDocs() + { + return + "Bu dosya doxygen tarafından üretilen grafiklerin nasıl anlaşılacağını " + "açıklar.<p>\n" + "Aşağıdaki örneğe bakalım:\n" + "\\code\n" + "/*! Sadeleşme yüzünden görünmeyen sınıf */\n" + "class Invisible { };\n\n" + "/*! Sadeleşmiş sınıf, kalıtım ilişkisi gizli */\n" + "class Truncated : public Invisible { };\n\n" + "/* Doxygen yorumlarıyla dokümante edilmemiş sınıf */\n" + "class Undocumented { };\n\n" + "/*! Public kalıtımla türetilen sınıf */\n" + "class PublicBase : public Truncated { };\n\n" + "/*! Bir şablon sınıfı */\n" + "template<class T> class Templ { };\n\n" + "/*! Korumalı kalıtımla türetilen sınıf */\n" + "class ProtectedBase { };\n\n" + "/*! Özel kalıtımla türetilen sınıf */\n" + "class PrivateBase { };\n\n" + "/*! Türetilen sınıf tarafından kullanılan sınıf */\n" + "class Used { };\n\n" + "/*! Pekçok sınıftan türeyen bir sınıf */\n" + "class Inherited : public PublicBase,\n" + " protected ProtectedBase,\n" + " private PrivateBase,\n" + " public Undocumented,\n" + " public Templ<int>\n" + "{\n" + " private:\n" + " Used *m_usedClass;\n" + "};\n" + "\\endcode\n" + "Bu kod aşağıdaki şemayı oluşturur:" + "<p><center><img alt=\"\" src=\"graph_legend."+Config_getEnum("DOT_IMAGE_FORMAT")+"\"></center>\n" + "<p>\n" + "Yukarıdaki şemadaki kutular aşağıda açıklanmıştır:\n" + "<ul>\n" + "<li>%A dolu gri kutu şemanın ait olduğu yapı(struct) ya da sınıfı " + "gösterir.\n" + "<li>%A siyah çerçeveli bir kutu dokümante edilmiş bir yapı(struct) ya da sınıfı gösterir.\n" + "<li>%A gri çerçeveli bir kutu dokümante edilmemiş bir yapı(struct) ya da sınıfı gösterir.\n" + "<li>%A kırmızı çerçeveli bir kutu tüm kalıtım/içerme ilişkileri gösterilmemiş ve dokümante " + "edilmiş bir yapı(struct) ya da sınıfı gösterir. %A şema belirlenen sınırlara " + "sığmıyorsa sadeleştirilir.\n" + "</ul>\n" + "Okların anlamı aşağıdaki gibidir:\n" + "<ul>\n" + "<li>%A koyu mavi ok iki sınıf arasındaki public kalıtım ilişkisini " + "göstermekte kullanılır.\n" + "<li>%A koyu yeşil ok korumalı kalıtımı gösterir.\n" + "<li>%A koyu kırmızı ok özel kalıtımı gösterir.\n" + "<li>%A mor kesikli çizgi bir sınıfın diğeri tarafından içeriliyor ya da kullanılıyor " + "olduğunu gösterir. Ok işaret edilen sınıfın hangi değişken(ler) tarafından erişildiğini " + "gösteren etiketle işaretleniştir.\n" + "<li>%A Sarı kesikli çizgi şablondan üretilen bir sınıf ve ilgili şablon sınıfı " + "arasındaki ilişkiyi gösterir. Ok türeyen sınıfın şablon parametreleriyle " + "etiketlenmiştir.\n" + "</ul>\n"; + } + /*! text for the link to the legend page */ + virtual QCString trLegend() + { + return "lejant"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.0 +////////////////////////////////////////////////////////////////////////// + + /*! Used as a marker that is put before a test item */ + virtual QCString trTest() + { + return "Test"; + } + /*! Used as the header of the test list */ + virtual QCString trTestList() + { + return "Test Listesi"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.1 +////////////////////////////////////////////////////////////////////////// + + /*! Used as a section header for KDE-2 IDL methods */ + virtual QCString trDCOPMethods() + { + return "DCOP Üye Fonksiyonlar"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.2 +////////////////////////////////////////////////////////////////////////// + + /*! Used as a section header for IDL properties */ + virtual QCString trProperties() + { + return "Özellikler"; + } + /*! Used as a section header for IDL property documentation */ + virtual QCString trPropertyDocumentation() + { + return "Özellik Dokümantasyonu"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.4 +////////////////////////////////////////////////////////////////////////// + + /*! Used for Java classes in the summary section of Java packages */ + virtual QCString trClasses() + { + if (Config_getBool("OPTIMIZE_OUTPUT_FOR_C")) + { + return "Veri Yapıları"; + } + else + { + return "Sınıflar"; + } + } + /*! Used as the title of a Java package */ + virtual QCString trPackage(const char *name) + { + return (QCString)"Paket "+name; + } + /*! Title of the package index page */ + virtual QCString trPackageList() + { + return "Paket Listesi"; + } + /*! The description of the package index page */ + virtual QCString trPackageListDescription() + { + return "Paketler ve kısa tanımları (var ise):"; + } + /*! The link name in the Quick links header for each page */ + virtual QCString trPackages() + { + return "Paketler"; + } + /*! Text shown before a multi-line define */ + virtual QCString trDefineValue() + { + return "Değer:"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.5 +////////////////////////////////////////////////////////////////////////// + + /*! Used as a marker that is put before a \\bug item */ + virtual QCString trBug() + { + return "Hata"; + } + /*! Used as the header of the bug list */ + virtual QCString trBugList() + { + return "Hata Listesi"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.6 +////////////////////////////////////////////////////////////////////////// + + /*! Used as ansicpg for RTF file + * + * The following table shows the correlation of Charset name, Charset Value and + * <pre> + * Codepage number: + * Charset Name Charset Value(hex) Codepage number + * ------------------------------------------------------ + * DEFAULT_CHARSET 1 (x01) + * SYMBOL_CHARSET 2 (x02) + * OEM_CHARSET 255 (xFF) + * ANSI_CHARSET 0 (x00) 1252 + * RUSSIAN_CHARSET 204 (xCC) 1251 + * EE_CHARSET 238 (xEE) 1250 + * GREEK_CHARSET 161 (xA1) 1253 + * TURKISH_CHARSET 162 (xA2) 1254 + * BALTIC_CHARSET 186 (xBA) 1257 + * HEBREW_CHARSET 177 (xB1) 1255 + * ARABIC _CHARSET 178 (xB2) 1256 + * SHIFTJIS_CHARSET 128 (x80) 932 + * HANGEUL_CHARSET 129 (x81) 949 + * GB2313_CHARSET 134 (x86) 936 + * CHINESEBIG5_CHARSET 136 (x88) 950 + * </pre> + * + */ + virtual QCString trRTFansicp() + { + return "1254"; + } + + + /*! Used as ansicpg for RTF fcharset + * \see trRTFansicp() for a table of possible values. + */ + virtual QCString trRTFCharSet() + { + return "162"; + } + + /*! Used as header RTF general index */ + virtual QCString trRTFGeneralIndex() + { + return "İndeks"; + } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trClass(bool first_capital, bool singular) + { + QCString result((first_capital ? "Sınıf" : "sınıf")); + if (!singular) result+="lar"; + return result; + } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trFile(bool first_capital, bool singular) + { + QCString result((first_capital ? "Dosya" : "dosya")); + if (!singular) result+="lar"; + return result; + } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trNamespace(bool first_capital, bool singular) + { + QCString result((first_capital ? "Namespace" : "namespace")); + if (!singular) result+="\'ler"; + return result; + } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trGroup(bool first_capital, bool singular) + { + QCString result((first_capital ? "Grup" : "grup")); + if (!singular) result+="lar"; + return result; + } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trPage(bool first_capital, bool singular) + { + QCString result((first_capital ? "Sayfa" : "sayfa")); + if (!singular) result+="lar"; + return result; + } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trMember(bool first_capital, bool singular) + { + QCString result((first_capital ? "Üye" : "üye")); + if (!singular) result+="ler"; + return result; + } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trGlobal(bool first_capital, bool singular) + { + QCString result((first_capital ? "Global değişken" : "global değişken")); + if (!singular) result+="ler"; + return result; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.7 +////////////////////////////////////////////////////////////////////////// + + /*! This text is generated when the \\author command is used and + * for the author section in man pages. */ + virtual QCString trAuthor(bool first_capital, bool singular) + { + QCString result((first_capital ? "Yazar" : "yazar")); + if (!singular) result+="lar"; + return result; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.11 +////////////////////////////////////////////////////////////////////////// + + /*! This text is put before the list of members referenced by a member + */ + virtual QCString trReferences() + { + return "Referanslar"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.13 +////////////////////////////////////////////////////////////////////////// + + /*! used in member documentation blocks to produce a list of + * members that are implemented by this one. + */ + virtual QCString trImplementedFromList(int numEntries) + { + return "Şu üyeleri gerçekler: "+trWriteList(numEntries)+"."; + } + + /*! used in member documentation blocks to produce a list of + * all members that implement this abstract member. + */ + virtual QCString trImplementedInList(int numEntries) + { + return "Şu üyelerce gerçeklenir: "+trWriteList(numEntries)+"."; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.16 +////////////////////////////////////////////////////////////////////////// + + /*! used in RTF documentation as a heading for the Table + * of Contents. + */ + virtual QCString trRTFTableOfContents() + { + return "İçindekiler"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.17 +////////////////////////////////////////////////////////////////////////// + + /*! Used as the header of the list of item that have been + * flagged deprecated + */ + virtual QCString trDeprecatedList() + { + return "Kullanımdan Kalkanlar Listesl"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.2.18 +////////////////////////////////////////////////////////////////////////// + + /*! Used as a header for declaration section of the events found in + * a C# program + */ + virtual QCString trEvents() + { + return "Olaylar"; + } + /*! Header used for the documentation section of a class' events. */ + virtual QCString trEventDocumentation() + { + return "Olay Dokümantasyonu"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.3 +////////////////////////////////////////////////////////////////////////// + + /*! Used as a heading for a list of Java class types with package scope. + */ + virtual QCString trPackageTypes() + { + return "Paket Tipleri"; + } + /*! Used as a heading for a list of Java class fonksiyonlar with package + * scope. + */ + virtual QCString trPackageMembers() + { + return "Paket Fonksiyonlar"; + } + /*! Used as a heading for a list of static Java class fonksiyonlar with + * package scope. + */ + virtual QCString trStaticPackageMembers() + { + return "Static Pakat Fonksiyonları"; + } + /*! Used as a heading for a list of Java class variables with package + * scope. + */ + virtual QCString trPackageAttribs() + { + return "Packet Özellikleri(attribute)"; + } + /*! Used as a heading for a list of static Java class variables with + * package scope. + */ + virtual QCString trStaticPackageAttribs() + { + return "Statik Packet Özellikleri(attribute)"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.3.1 +////////////////////////////////////////////////////////////////////////// + + /*! Used in the quick index of a class/file/namespace member list page + * to link to the unfiltered list of all members. + */ + virtual QCString trAll() + { + return "Tümü"; + } + /*! Put in front of the call graph for a function. */ + virtual QCString trCallGraph() + { + return "Bu fonksiyon için çağırılma şeması:"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.3.3 +////////////////////////////////////////////////////////////////////////// + + /*! When the search engine is enabled this text is put in the header + * of each page before the field where one can enter the text to search + * for. + */ + virtual QCString trSearchForIndex() + { + return "Arama yapılacak metin"; + } + /*! This string is used as the title for the page listing the search + * results. + */ + virtual QCString trSearchResultsTitle() + { + return "Arama sonuçları"; + } + /*! This string is put just before listing the search results. The + * text can be different depending on the number of documents found. + * Inside the text you can put the special marker $num to insert + * the number representing the actual number of search results. + * The @a numDocuments parameter can be either 0, 1 or 2, where the + * value 2 represents 2 or more matches. HTML markup is allowed inside + * the returned string. + */ + virtual QCString trSearchResults(int numDocuments) + { + if (numDocuments==0) + { + return "Üzgünüm, sorgunuzla eşleşen doküman bulunamadı."; + } + else if (numDocuments==1) + { + return "Sorgunuzla eşleşen <b>1</b> doküman bulundu."; + } + else + { + return "Sorgunuzla eşleşen <b>$num</b> doküman bulundu. " + "Önce en iyi eşleşmeler gösteriliyor."; + } + } + /*! This string is put before the list of matched words, for each search + * result. What follows is the list of words that matched the query. + */ + virtual QCString trSearchMatches() + { + return "Eşleşme:"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.3.8 +////////////////////////////////////////////////////////////////////////// + + /*! This is used in HTML as the title of page with source code for file filename + */ + virtual QCString trSourceFile(QCString& filename) + { + return filename + " Kaynak Dosyası"; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.3.9 +////////////////////////////////////////////////////////////////////////// + + /*! This is used as the name of the chapter containing the directory + * hierarchy. + */ + virtual QCString trDirIndex() + { return "Dizin Hiyerarşisi"; } + + /*! This is used as the name of the chapter containing the documentation + * of the directories. + */ + virtual QCString trDirDocumentation() + { return "Dizin Dokümantasyonu"; } + + /*! This is used as the title of the directory index and also in the + * Quick links of an HTML page, to link to the directory hierarchy. + */ + virtual QCString trDirectories() + { return "Dizinler"; } + + /*! This returns a sentences that introduces the directory hierarchy. + * and the fact that it is sorted alphabetically per level + */ + virtual QCString trDirDescription() + { return "Bu dizin hiyerarşisi tamamen olmasa da yaklaşık " + "olarak alfabetik sıraya konulmuştur:"; + } + + /*! This returns the title of a directory page. The name of the + * directory is passed via \a dirName. + */ + virtual QCString trDirReference(const char *dirName) + { QCString result=dirName; result+=" Dizin Referansı"; return result; } + + /*! This returns the word directory with or without starting capital + * (\a first_capital) and in sigular or plural form (\a singular). + */ + virtual QCString trDir(bool first_capital, bool singular) + { + QCString result((first_capital ? "Dizin" : "dizin")); + if (!singular) result+="ler"; + return result; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.4.1 +////////////////////////////////////////////////////////////////////////// + + /*! This text is added to the documentation when the \\overload command + * is used for a overloaded function. + */ + virtual QCString trOverloadText() + { + return "Bu çok anlamlı (overloaded) bir üye fonksiyondur, " + "tamamlık açısından burada verilmektedir. Yukarıdaki fonksiyondan " + "sadece aldığı argüman(lar) açısından farklıdır."; + } + +////////////////////////////////////////////////////////////////////////// +// new since 1.4.6 +////////////////////////////////////////////////////////////////////////// + + /*! This is used to introduce a caller (or called-by) graph */ + virtual QCString trCallerGraph() + { + return "Bu fonksiyon için çağırılma şeması:"; + } + + /*! This is used in the documentation of a file/namespace before the list + * of documentation blocks for enumeration values + */ + virtual QCString trEnumerationValueDocumentation() + { return "Enümerasyon Dokümantasyonu"; } + +////////////////////////////////////////////////////////////////////////// +// new since 1.5.4 (mainly for Fortran) +////////////////////////////////////////////////////////////////////////// + + /*! header that is put before the list of member subprograms (Fortran). */ + virtual QCString trMemberFunctionDocumentationFortran() + { return "Üye Fonksiyon/Subroutine Dokümantasyonu"; } + + /*! This is put above each page as a link to the list of annotated data types (Fortran). */ + virtual QCString trCompoundListFortran() + { return "Veri Tipleri Listesi"; } + + /*! This is put above each page as a link to all members of compounds (Fortran). */ + virtual QCString trCompoundMembersFortran() + { return "Veri Alanları"; } + + /*! This is an introduction to the annotated compound list (Fortran). */ + virtual QCString trCompoundListDescriptionFortran() + { return "Kısa tanımlarıyla veri tipleri:"; } + + /*! This is an introduction to the page with all data types (Fortran). */ + virtual QCString trCompoundMembersDescriptionFortran(bool extractAll) + { + QCString result="Bu liste tüm "; + if (!extractAll) + { + result+="dokümante edilmiş "; + } + result+="veri tiplerini içerir ve "; + if (!extractAll) + { + result+="her üyeyi veri yapısı dokümantasyonuna bağlar:"; + } + else + { + result+="ait oldukları veri tiplerine bağlar:"; + } + return result; + } + + /*! This is used in LaTeX as the title of the chapter with the + * annotated compound index (Fortran). + */ + virtual QCString trCompoundIndexFortran() + { return "Veri Tipi İndeksi"; } + + /*! This is used in LaTeX as the title of the chapter containing + * the documentation of all data types (Fortran). + */ + virtual QCString trTypeDocumentation() + { return "Veri Tipi Dokümantasyonu"; } + + /*! This is used in the documentation of a file as a header before the + * list of (global) subprograms (Fortran). + */ + virtual QCString trSubprograms() + { return "Fonksiyonlar/Subroutine\'ler"; } + + /*! This is used in the documentation of a file/namespace before the list + * of documentation blocks for subprograms (Fortran) + */ + virtual QCString trSubprogramDocumentation() + { return "Fonksiyon/Subroutine Dokümantasyonu"; } + + /*! This is used in the documentation of a file/namespace/group before + * the list of links to documented compounds (Fortran) + */ + virtual QCString trDataTypes() + { return "Veri Tipleri"; } + + /*! used as the title of page containing all the index of all modules (Fortran). */ + virtual QCString trModulesList() + { return "Modüller Listesi"; } + + /*! used as an introduction to the modules list (Fortran) */ + virtual QCString trModulesListDescription(bool extractAll) + { + QCString result="Bu liste tüm "; + if (!extractAll) result+="dokümante edilmiş "; + result+="modülleri kısa tanımlarıya içerir:"; + return result; + } + + /*! used as the title of the HTML page of a module/type (Fortran) */ + virtual QCString trCompoundReferenceFortran(const char *clName, + ClassDef::CompoundType compType, + bool isTemplate) + { + QCString result=(QCString)clName; + switch(compType) + { + case ClassDef::Class: result+=" Modül"; break; + case ClassDef::Struct: result+=" Tip"; break; + case ClassDef::Union: result+=" Birleşim(Union)"; break; + case ClassDef::Interface: result+=" Arayüz"; break; + case ClassDef::Protocol: result+=" Protokol"; break; + case ClassDef::Category: result+=" Kategori"; break; + case ClassDef::Exception: result+=" İstisna"; break; + } + if (isTemplate) result+=" Şablon"; + result+=" Referans"; + return result; + } + /*! used as the title of the HTML page of a module (Fortran) */ + virtual QCString trModuleReference(const char *namespaceName) + { + QCString result=namespaceName; + result+=" Modül Referansı"; + return result; + } + + /*! This is put above each page as a link to all members of modules. (Fortran) */ + virtual QCString trModulesMembers() + { return "Modül Üyeleri"; } + + /*! This is an introduction to the page with all modules members (Fortran) */ + virtual QCString trModulesMemberDescription(bool extractAll) + { + QCString result="Bu liste tüm "; + if (!extractAll) result+="dokümante edilmiş "; + result+="modül üyelerini içerir ve "; + if (extractAll) + { + result+="her üyeyi modül dokümantasyonuna bağlar:"; + } + else + { + result+="ait oldukları modüllere bağlar:"; + } + return result; + } + + /*! This is used in LaTeX as the title of the chapter with the + * index of all modules (Fortran). + */ + virtual QCString trModulesIndex() + { return "Modüller Indeksi"; } + + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trModule(bool first_capital, bool singular) + { + QCString result((first_capital ? "Modül" : "modül")); + if (!singular) result+="ler"; + return result; + } + /*! This is put at the bottom of a module documentation page and is + * followed by a list of files that were used to generate the page. + */ + virtual QCString trGeneratedFromFilesFortran(ClassDef::CompoundType compType, + bool single) + { // here s is one of " Module", " Struct" or " Union" + // single is true implies a single file + QCString result=(QCString)"Bu "; + switch(compType) + { + case ClassDef::Class: result+="mdoül"; break; + case ClassDef::Struct: result+="tip"; break; + case ClassDef::Union: result+="birleşim(union)"; break; + case ClassDef::Interface: result+="arayüz"; break; + case ClassDef::Protocol: result+="protokol"; break; + case ClassDef::Category: result+="kategori"; break; + case ClassDef::Exception: result+="istisna"; break; + } + result+=" için dokümantasyon aşağıdaki dosya"; + if (single) result+=":"; else result+="lar"; + result="dan üretilmiştir:"; + return result; + } + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trType(bool first_capital, bool singular) + { + QCString result((first_capital ? "Tip" : "tip")); + if (!singular) result+="ler"; + return result; + } + /*! This is used for translation of the word that will possibly + * be followed by a single name or by a list of names + * of the category. + */ + virtual QCString trSubprogram(bool first_capital, bool singular) + { + QCString result((first_capital ? "Alt program" : "alt program")); + if (!singular) result+="lar"; + return result; + } + + /*! C# Type Constraint list */ + virtual QCString trTypeConstraints() + { + return "Tip Sınırlamaları"; + } + +}; + +#endif |