Commits

shuerhaaken committed 1426a98

add documentation

Comments (0)

Files changed (8)

+commit 6413107e98df0c4e18b83095ca1e6a21de3bdb53
+Author: Jörn Magens <shuerhaaken@googlemail.com>
+Date:   Tue Jul 9 15:55:20 2013 +0200
+
+    extend C test; update bindings
+
 commit 5d2888151d7f4ed8896e384d31c1ed65b103c536
 Author: Jörn Magens <shuerhaaken@googlemail.com>
 Date:   Tue Jul 9 15:44:12 2013 +0200
     bindings \
     examples \
     packaging \
+    doc \
     tests
 
 DIST_SUBDIRS = \
     bindings \
     examples \
     packaging \
+    doc \
     tests
 
 dist_noinst_DATA = AUTHORS COPYING NEWS TODO README ChangeLog taginfo.svg
     config.sub \
     aclocal.m4
 
-
 .PHONY: ChangeLog
 
+docs:
+	-cd doc && $(MAKE) $(AM_MAKEFLAGS) $@
+
 ChangeLog: Makefile
 	(GIT_DIR=$(top_srcdir)/.git git log > .changelog.tmp \
 	&& mv -f .changelog.tmp ChangeLog; rm -f .changelog.tmp) \
 	|| (touch ChangeLog; echo 'Git directory not found: installing possibly empty changelog.' >&2)
 
-dist-hook: ChangeLog
+dist-hook: ChangeLog docs
 
     bindings/c/libtaginfo_c.pc:bindings/c/libtaginfo_c.pc.in
     bindings/vala/Makefile
     examples/Makefile
+    doc/Makefile
     packaging/Makefile
     tests/samples/Makefile
     tests/Makefile
+# Doxyfile 1.2.2
+
+# This file describes the settings to be used by doxygen for a project
+#
+# All text after a hash (#) is considered a comment and will be ignored
+# The format is:
+#       TAG = value [value, ...]
+# For lists items can also be appended using:
+#       TAG += value [value, ...]
+# Values that contain spaces should be placed between quotes (" ")
+
+#---------------------------------------------------------------------------
+# General configuration options
+#---------------------------------------------------------------------------
+
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
+# by quotes) that should identify the project. 
+
+PROJECT_NAME           = @PACKAGE@
+
+# 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.
+
+PROJECT_NUMBER         = @VERSION@
+
+# 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.
+
+OUTPUT_DIRECTORY       = .
+
+# 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: 
+# Dutch, French, Italian, Czech, Swedish, German, Finnish, Japanese, 
+# Korean, Hungarian, Spanish, Romanian, Russian, Croatian, Polish, and 
+# Portuguese.
+
+OUTPUT_LANGUAGE        = English
+
+# 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 
+
+EXTRACT_ALL            = NO
+
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
+# will be included in the documentation. 
+
+EXTRACT_PRIVATE        = NO
+
+# If the EXTRACT_STATIC tag is set to YES all static members of a file 
+# will be included in the documentation. 
+
+EXTRACT_STATIC         = NO
+
+# 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. 
+
+HIDE_UNDOC_MEMBERS     = YES
+
+# 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 class will be included in the various 
+# overviews. This option has no effect if EXTRACT_ALL is enabled. 
+
+HIDE_UNDOC_CLASSES     = YES
+
+# 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. 
+
+BRIEF_MEMBER_DESC      = YES
+
+# 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. 
+
+REPEAT_BRIEF           = YES
+
+# 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. 
+
+ALWAYS_DETAILED_SEC    = NO
+
+# 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. 
+
+FULL_PATH_NAMES        = YES
+
+# 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. It is allowed to use relative paths in the argument list.
+
+STRIP_FROM_PATH        = ..
+
+# 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. 
+
+INTERNAL_DOCS          = NO
+
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
+# generate a class diagram (in Html and LaTeX) for classes with base or 
+# super classes. Setting the tag to NO turns the diagrams off. 
+
+CLASS_DIAGRAMS         = YES
+
+# 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. 
+
+SOURCE_BROWSER         = YES
+
+# Setting the INLINE_SOURCES tag to YES will include the body 
+# of functions and classes directly in the documentation. 
+
+INLINE_SOURCES         = NO
+
+# 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. 
+
+STRIP_CODE_COMMENTS    = YES
+
+# 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 
+# users are adviced to set this option to NO.
+
+CASE_SENSE_NAMES       = NO
+
+# 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. 
+
+HIDE_SCOPE_NAMES       = NO
+
+# 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. 
+
+VERBATIM_HEADERS       = NO
+
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
+# will put list of the files that are included by a file in the documentation 
+# of that file. 
+
+SHOW_INCLUDE_FILES     = YES
+
+# If the JAVADOC_AUTOBRIEF tag is set to YES (the default) 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-style will 
+# behave just like the Qt-style comments. 
+
+JAVADOC_AUTOBRIEF      = YES
+
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
+# member inherits the documentation from any documented member that it 
+# reimplements. 
+
+INHERIT_DOCS           = YES
+
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
+# is inserted in the documentation for inline members. 
+
+INLINE_INFO            = YES
+
+# 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. 
+
+SORT_MEMBER_DOCS       = YES
+
+# 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.
+
+DISTRIBUTE_GROUP_DOC   = YES
+
+# 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. 
+
+TAB_SIZE               = 8
+
+# The ENABLE_SECTIONS tag can be used to enable conditional 
+# documentation sections, marked by \if sectionname ... \endif. 
+
+ENABLED_SECTIONS       = 
+
+# 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.
+
+GENERATE_TODOLIST      = YES
+
+# 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.
+
+GENERATE_TESTLIST      = YES
+
+# 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. 
+
+ALIASES                = 
+
+#---------------------------------------------------------------------------
+# configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+
+# 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. 
+
+QUIET                  = NO
+
+# 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. 
+
+WARNINGS               = YES
+
+# 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. 
+
+WARN_IF_UNDOCUMENTED   = NO
+
+# 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. 
+
+WARN_FORMAT            = "$file:$line: $text"
+
+#---------------------------------------------------------------------------
+# configuration options related to the input files
+#---------------------------------------------------------------------------
+
+# 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. 
+
+INPUT                  = ../libtaginfo/taginfo.h
+
+
+# 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 all files are included. 
+
+FILE_PATTERNS          = *.cpp \
+                         *.h
+
+# 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. 
+
+RECURSIVE              = YES
+
+# 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. 
+
+EXCLUDE                = 
+
+# 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. 
+
+EXCLUDE_PATTERNS       = 
+
+# 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). 
+
+EXAMPLE_PATH           = ../examples
+
+# 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. 
+
+EXAMPLE_PATTERNS       = *.cpp \
+                         *.c \
+                         *.h
+
+# 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). 
+
+IMAGE_PATH             = .
+
+# 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. 
+
+INPUT_FILTER           = 
+
+#---------------------------------------------------------------------------
+# configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+
+# 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. 
+
+ALPHABETICAL_INDEX     = NO
+
+# 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]) 
+
+COLS_IN_ALPHA_INDEX    = 5
+
+# 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. 
+
+IGNORE_PREFIX          = 
+
+#---------------------------------------------------------------------------
+# configuration options related to the HTML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
+# generate HTML output. 
+
+GENERATE_HTML          = YES
+
+# 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. 
+
+HTML_OUTPUT            = @DOX_DIR_HTML@
+
+# 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.
+
+HTML_HEADER            = 
+
+# 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.
+
+HTML_FOOTER            = 
+
+# 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 
+
+HTML_STYLESHEET        = libtaginfo.css
+
+# 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. 
+
+HTML_ALIGN_MEMBERS     = YES
+
+# 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 compressed HTML help file (.chm) 
+# of the generated HTML documentation. 
+
+GENERATE_HTMLHELP      = NO
+
+# 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. 
+
+DISABLE_INDEX          = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the LaTeX output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
+# generate Latex output. 
+
+GENERATE_LATEX         = YES
+
+# 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. 
+
+LATEX_OUTPUT           = @DOX_DIR_LATEX@
+
+# 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. 
+
+COMPACT_LATEX          = NO
+
+# 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. 
+
+PAPER_TYPE             = letter
+
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
+# packages that should be included in the LaTeX output. 
+
+EXTRA_PACKAGES         = 
+
+# 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! 
+
+LATEX_HEADER           = 
+
+# 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. 
+
+PDF_HYPERLINKS         = NO
+
+# 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. 
+
+USE_PDFLATEX           = NO
+
+# 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. 
+
+LATEX_BATCHMODE        = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the RTF output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
+# The RTF output is optimised for Word 97 and may not look very pretty with 
+# other RTF readers or editors.
+
+GENERATE_RTF           = NO
+
+# 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. 
+
+RTF_OUTPUT             = @DOX_DIR_RTF@
+
+# 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. 
+
+COMPACT_RTF            = NO
+
+# 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 a WORD or other. 
+# programs which support those fields. 
+# Note: wordpad (write) and others do not support links. 
+
+RTF_HYPERLINKS         = NO
+
+# Load stylesheet definitions from file. Syntax is similar to doxygen's 
+# config file, i.e. a series of assigments. You only have to provide 
+# replacements, missing definitions are set to their default value. 
+
+RTF_STYLESHEET_FILE    = 
+
+#---------------------------------------------------------------------------
+# configuration options related to the man page output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
+# generate man pages 
+
+GENERATE_MAN           = NO
+
+# 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. 
+
+MAN_OUTPUT             = @DOX_DIR_MAN@
+
+# The MAN_EXTENSION tag determines the extension that is added to 
+# the generated man pages (default is the subroutine's section .3) 
+
+MAN_EXTENSION          = .3
+
+#---------------------------------------------------------------------------
+# configuration options related to the XML output
+#---------------------------------------------------------------------------
+
+# 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. Warning: This feature 
+# is still experimental and very incomplete.
+
+GENERATE_XML           = NO
+
+#---------------------------------------------------------------------------
+# Configuration options related to the preprocessor   
+#---------------------------------------------------------------------------
+
+# 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. 
+
+ENABLE_PREPROCESSING   = YES
+
+# 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. 
+
+MACRO_EXPANSION        = YES
+
+# 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_PREDEFINED tags. 
+
+EXPAND_ONLY_PREDEF     = NO
+
+# 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. 
+
+SEARCH_INCLUDES        = YES
+
+# 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. 
+
+INCLUDE_PATH           = 
+
+# 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. 
+
+INCLUDE_FILE_PATTERNS  = 
+
+# 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. 
+
+PREDEFINED             = __cplusplus
+
+# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY 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. 
+
+EXPAND_AS_DEFINED      = 
+
+#---------------------------------------------------------------------------
+# Configuration::addtions related to external references   
+#---------------------------------------------------------------------------
+
+# The TAGFILES tag can be used to specify one or more tagfiles. 
+
+TAGFILES               = 
+
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
+# a tag file that is based on the input files it reads. 
+
+GENERATE_TAGFILE       = 
+
+# 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. 
+
+ALLEXTERNALS           = NO
+
+# The PERL_PATH should be the absolute path and name of the perl script 
+# interpreter (i.e. the result of `which perl'). 
+
+PERL_PATH              = /usr/bin/perl
+
+#---------------------------------------------------------------------------
+# Configuration options related to the dot tool   
+#---------------------------------------------------------------------------
+
+# 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) 
+
+HAVE_DOT               = NO
+
+# 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.
+
+CLASS_GRAPH            = YES
+
+# 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. 
+
+COLLABORATION_GRAPH    = YES
+
+# If the ENABLE_PREPROCESSING, 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. 
+
+INCLUDE_GRAPH          = YES
+
+# If the ENABLE_PREPROCESSING, 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 
+
+INCLUDED_BY_GRAPH      = YES
+
+# 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. 
+
+GRAPHICAL_HIERARCHY    = YES
+
+# 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 on the path. 
+
+DOT_PATH               = 
+
+# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than 
+# this value, doxygen will try to truncate the graph, so that it fits within 
+# the specified constraint. Beware that most browsers cannot cope with very 
+# large images. 
+
+MAX_DOT_GRAPH_WIDTH    = 1024
+
+# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than 
+# this value, doxygen will try to truncate the graph, so that it fits within 
+# the specified constraint. Beware that most browsers cannot cope with very 
+# large images. 
+
+MAX_DOT_GRAPH_HEIGHT   = 1024
+
+#---------------------------------------------------------------------------
+# Configuration::addtions related to the search engine   
+#---------------------------------------------------------------------------
+
+# 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. 
+
+SEARCHENGINE           = NO
+
+# The CGI_NAME tag should be the name of the CGI script that 
+# starts the search engine (doxysearch) with the correct parameters. 
+# A script with this name will be generated by doxygen. 
+
+CGI_NAME               = search.cgi
+
+# The CGI_URL tag should be the absolute URL to the directory where the 
+# cgi binaries are located. See the documentation of your http daemon for 
+# details. 
+
+CGI_URL                = 
+
+# The DOC_URL tag should be the absolute URL to the directory where the 
+# documentation is located. If left blank the absolute path to the 
+# documentation, with file:// prepended to it, will be used. 
+
+DOC_URL                = 
+
+# The DOC_ABSPATH tag should be the absolute path to the directory where the 
+# documentation is located. If left blank the directory on the local machine 
+# will be used. 
+
+DOC_ABSPATH            = 
+
+# The BIN_ABSPATH tag must point to the directory where the doxysearch binary 
+# is installed. 
+
+BIN_ABSPATH            = /usr/local/bin/
+
+# The EXT_DOC_PATHS tag can be used to specify one or more paths to 
+# documentation generated for other projects. This allows doxysearch to search 
+# the documentation for these projects as well. 
+
+EXT_DOC_PATHS          = 
+# This file is part of libtaginfo.
+# Copyright (C) 2012-2013  Jörn Magens <shuerhaaken@googlemail.com>
+
+Doxyfile: $(srcdir)/Doxyfile.in  $(top_builddir)/config.status
+	cd $(top_builddir) \
+	  && CONFIG_FILES=$(subdir)/$@ CONFIG_HEADERS= $(SHELL) ./config.status
+
+index.html: $(srcdir)/index.html.in  $(top_builddir)/config.status
+	cd $(top_builddir) \
+	  && CONFIG_FILES=$(subdir)/$@ CONFIG_HEADERS= $(SHELL) ./config.status
+
+docsdistdir = $(PACKAGE)-doc-$(VERSION)
+
+dox: Doxyfile
+	-rm -rf @DOX_DIR_HTML@ @DOX_DIR_LATEX@
+	cd $(srcdir) && doxygen Doxyfile
+
+docs: dox index.html libtaginfo.css
+	-rm -rf $(docsdistdir).*
+	cd $(srcdir)/@DOX_DIR_LATEX@ && \
+	make pdf && \
+	(cp *.pdf ../$(docsdistdir).pdf || true) && \
+	cp *.ps ../$(docsdistdir).ps && \
+	gzip -9 ../$(docsdistdir).ps
+	-rm -rf $(srcdir)/@DOX_DIR_LATEX@
+
+EXTRA_DIST = \
+	Doxyfile.in \
+	libtaginfo.css \
+	index.html.in
+
+DISTCLEANFILES = \
+	Doxyfile \
+	index.html

doc/index.html.in

+<!-- $Id: index.html.in,v 1.10 2000/10/15 16:37:54 eldamitri Exp $ -->
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+  <head>
+    <title>libtaginfo - Media Metatag Library</title>
+
+    <style type="text/css">
+      <!--
+      body {text-align: center}
+      td.h1 {font: 43px Arial, Helvetica} 
+      td.h2 {font: 27px Arial, Helvetica}
+      td.h3 {font: 17px Arial, Helvetica}
+      div.h5 {font: 14px Arial, Helvetica} 
+      td {font: 14px Arial, Helvetica} 
+      a {color: #DD6600; text-decoration: none} 
+      b {font-weight: bold}
+      -->
+   </style>
+    
+    <meta name="description" content="libtaginfo - Media Metatag Library">
+    
+  </head>
+  
+  <body vlink="#551a8b" alink="#ff0000" link="#0000ee" text="#000000" bgcolor="#ffffff">
+    <br>
+
+    <table border=0 width="90%">
+      <tr align="center">
+        <td class=h5 align="center" width="16%">
+          <a href="http://sourceforge.net/news/?group_id=979">News</a>
+        </td>
+        <td class=h5 align="center" width="17%">
+          <a href="http://sourceforge.net/project/filelist.php?group_id=979">Download</a>
+        </td>
+        <td class=h5 align="center" width="16%">
+          <a
+            href="https://groups.google.com/forum/#!forum/xnoise">Mailing list</a>
+        </td>
+        <td class=h5 align="center" width="16%">
+          <a href="http://sourceforge.net/bugs/?group_id=979">Bugs</a>
+        </td>
+        <td class=h5 align="center" width="17%">
+          <a href="http://sourceforge.net/patch/?group_id=979">Patches</a>
+        </td>
+        <td class=h5 align="center" width="16%">
+          <a href="http://sourceforge.net/cvs/?group_id=979">CVS</a>
+        </td>
+      </tr>
+      <tr>
+        <td bgcolor="#FF7700" colspan=6><img src="fillpx.gif" width=1 height=1 alt="----------------------------------------------------------------------"></td>
+      </tr>
+    </table>
+    
+    <br>
+    
+    <img src="id3v2.gif" alt="[ID3v2 logo]">
+    <table border=0>
+      <tr align="center"><td class=h1>&nbsp;<a href="http://sourceforge.net/project/?group_id=979">@PACKAGE@</a>&nbsp;</td></tr>
+      <tr align="center">
+        <td bgcolor="#FF7700"><img src="fillpx.gif" width=1 height=1 alt="------"></td>
+      </tr>
+      
+    </table>
+    <table border=0>
+      <tr align="center">
+        <td class=h3>Latest Release:
+          <a href="http://sourceforge.net/project/filelist.php?group_id=979">@VERSION@</a>
+        </td>
+      </tr>
+    </table>
+    
+    <br>
+    
+    <table border=0 width="90%">
+      <tr align="left"><td class=h2>Overview</td></tr>
+    </table>
+    <table border=0 width="80%">
+      <tr>
+        <td>
+          
+            TagInfo is a library for reading media metadata (tags).
+            TagInfo is a convenience wrapper for taglib with C and vala bindings.
+            Features are reading/writing fields like: Artist, Album, Title, Genre, AlbumArtist, Comments, Disk number, Compilation flag, User labels, Embedded Images, Lyrics, Audio properties (length, bitrate, samplerate, channels ...), ...
+            TagInfo is fast. Very rough tests have shown that it is about 40 - 60 times faster in file reading than with GStreamer's GstDiscoverer (codec based). There is not much overhead coming with this library, so it reads at almost the same speed as taglib itself, which is the fastest way around to read tag information.
+            
+            Additionally, this library offers C and vala bindings that provide a lot of features that are not available via TagLib's own C bindings (and the according vala bindings).
+            
+            The lacking possibility of accessing certain data fields via taglibs own C bindings was the original motivation for the creation of this library.
+            
+            TagInfo can be used from C++, C and vala.
+        </td>
+      </tr>
+    </table>
+    
+    <br>
+    
+    <table border=0 width="90%">
+      <tr><td class=h2>Licensing</td></tr>
+    </table>
+    <table border=0 width="80%">
+      <tr><td>
+          
+          The libtaginfo library is <a
+            href="http://www.opensource.org">open-source</a> software, licensed
+          under the <a href="http://www.gnu.org/copyleft/lesser.html">GNU
+            Library General Public License (LGPL)</a>.  In short, this allows
+          any application to link to and use the library without affecting
+          their license, while guaranteeing that the libtaginfo library itself
+          (and any modifications to it) will remain freely available in
+          source code form.  The project developers therefore greatly
+          encourage input from everyone, be it with feature suggestions, code
+          patches, bug reports, or anything.  The best way to contribute to
+          this effort is to <a
+            href="https://groups.google.com/forum/#!forum/xnoise">subscribe
+            to the mailing list</a> and join in on the discussions!
+          
+          <br>
+        </td>
+      </tr>
+    </table>
+    
+    <br>
+    
+    <a name="contact"></a>
+    <table border=0 width="90%">
+      <tr><td class=h2>Contacting the Author</td></tr>
+    </table>
+    <table border=0 width="80%">
+      <tr>
+        <td> 
+          
+          The libtaginfo project is coordinated by <a
+            href="mailto:shuerhaaken@googlemail.com">Shuerhaaken</a>.
+          
+        </td>
+      </tr>
+    </table>
+    
+    <br>
+    
+  </body>
+</html>

doc/libtaginfo.css

+/** $Id: libtaginfo.css**/
+
+body, p, h2, b, a, ol, ul {font-family: Arial, Helvetica, sans-serif;}
+body { background-color: white; }
+pre {font-family: monospace; font-size: small;}
+h1 { text-align: center; font-size: x-large; }
+h2 { font-size: large; font-weight: bold; }
+h3 { font-size: large; }
+a {color: #DD6600; text-decoration: none;} 
+A.qindex {}
+A.qindexRef {}
+A.el { text-decoration: none; font-weight: bold; }
+A.elRef { font-weight: bold; }
+A.code { text-decoration: none; font-weight: normal; /*color: #4444ee;*/ }
+A.codeRef { font-weight: normal; color: #4444ee; }
+DL.el { margin-left: -1cm; }
+DIV.fragment { width: 100%; border: none; background-color: #eeeeee; }
+DIV.in { margin-left: 16; }
+DIV.ah { background-color: black; margin-bottom: 3; margin-top: 3; }
+TD.md { background-color: #f2f2ff; }
+DIV.groupHeader { margin-left: 16; margin-top: 12; margin-bottom: 6; font-weight: bold; }
+DIV.groupText { margin-left: 16; font-style: italic; font-size: smaller; }
+td.h1 {font: 43px Arial, Helvetica;} 
+td.h2 {font: 27px Arial, Helvetica;}
+div.h5 {font: 14px Arial, Helvetica;} 
+td {font: 14px Arial, Helvetica;} 
+b {font-weight: bold;}

libtaginfo/taginfo.h

         MEDIA_FILE_TYPE_WMV
     };
     
+    
+    //! The enumeration type for the image encoding
+    
+    /*!
+    * Images can be in jpeg, png, bmp, ... format
+    */
     enum ImageFileType {
         IMAGE_FILE_TYPE_UNKNOWN,
         IMAGE_FILE_TYPE_JPEG,
         IMAGE_FILE_TYPE_BMP
     };
     
+    //! The enumeration type for the image type
+    
+    /*!
+    * Content of images can show different things
+    */
     enum ImageType {
         IMAGE_TYPE_OTHER,
         //! 32x32 PNG image that should be used as the file icon
     };
     
     
+    //! A wrapper for image data
+
+    /*!
+    * This class holds image data and information on reads and writes
+    * Internal memory is freed automatically.
+    */
     class Image {
         public:
             
     };
     
     
+    //! A simple, generic interface to common audio meta data fields
+    
+    /*!
+    * This is an attempt to abstract away the difference in the meta data formats
+    * of various audio codecs and tagging schemes.  As such it is generally a
+    * subset of what is available in the specific formats but should be suitable
+    * for most applications.
+    */
     class Info {
         protected :
             TagLib::FileRef * taglib_fileref;
             bool is_valid();
             
             //Tag access functions
+            
+            /*!
+             * Get the title of a music track
+             */
             String get_title(void) const;
+            /*!
+             * Set the title of a music track.
+             * This will not be saved to file before write() is called on the Info object.
+             */
             void   set_title(const String new_title);
             
             String get_genre(void) const;
             Info(const String &filename = "", bool create_own_fileref = false);
             ~Info();
             
-            
+            /*!
+             * Reads tags and properties from the Info of a file.
+             * String returns are coming as TagLib::String.
+             */
             virtual bool read(void);
+            
+            /*!
+             * Writes the tags of the Info object to the file.
+             */
             virtual bool write(void);
             
             
             virtual Image ** get_images(int &image_count) const;
             virtual void     set_images(const Image ** images, const int image_count);
 
-//            virtual bool can_handle_images(void) const;
-//            virtual bool get_image(char*& data, int &data_length, ImageFileType &image_file_type) const;
-//            virtual bool set_image(const char* data, int data_length, ImageFileType image_file_type);
-            
             virtual bool can_handle_lyrics(void) const;
             virtual String get_lyrics(void) const;
             virtual bool set_lyrics(const String &lyrics);
             
+            /*!
+             * Create a Info from \a file.
+             *
+             * This is a recommended way for accessing media tags through libtaginfo.
+             */
             static Info * create_tag_info(const String &file);
+            
+            /*!
+             * Create a Info from \a file. If \a format is given, libtaginfo will try to create 
+             * an Info object for the desired \a format.
+             * This is a recommended way for accessing media tags through libtaginfo.
+             */
             static Info * create_tag_info_with_format(const String &file, MediaFileType format);
+            
+            /*!
+             * Create a Info from \a file. If \a mime is given, libtaginfo will try to create 
+             * an Info object for the desired \a mime.
+             * This is a recommended way for accessing media tags through libtaginfo.
+             */
             static Info * create_tag_info_from_mime(const String &filename, const String &mime_type);
     };