# This could be handy for archiving the generated documentation or
# if some version control system is used.
-PROJECT_NUMBER = %PROJECT_NUMBER%
+PROJECT_NUMBER = @PACKAGE_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 = %DEV_OR_USR_OR_JA%
+OUTPUT_DIRECTORY = %USR_JA_DEV%
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
# documentation generated by doxygen is written. Doxygen will use this
# directories like "/usr/src/myproject". Separate the files or directories
# with spaces.
-INPUT = @M17NLIB@/src/
+INPUT = "@M17NLIB@/src/m17n-core.h" "@M17NLIB@/src/m17n.h" "@M17NLIB@/src/m17n-win.h" "@M17NLIB@/src/m17n-X.h" "@M17NLIB@/src/m17n-err.h" "@M17NLIB@/src/"
# 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 = *.h *.c
+FILE_PATTERNS = *.c
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
# certain files from those directories.
-EXCLUDE_PATTERNS =
+EXCLUDE_PATTERNS = font-flt.c font-ft.c link*.c
# The EXAMPLE_PATH tag can be used to specify one or more files or
# directories that contain example code fragments that are included (see
# input file. Doxygen will then use the output that the filter program writes
# to standard output.
-INPUT_FILTER = @srcdir@/utils/%DEV_OR_USR_OR_JA%_filter.rb
+INPUT_FILTER = @abs_srcdir@/utils/%INPUT_FILTER%_filter.rb
# 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
# each generated HTML page. If it is left blank doxygen will generate a
# standard header.
-HTML_HEADER = @srcdir@/header.html
+HTML_HEADER = @abs_srcdir@/header.html
# 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 = @srcdir@/footer.html
+HTML_FOOTER = @abs_srcdir@/footer.html
# 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 = @srcdir@/m17nlib.css
+HTML_STYLESHEET = @abs_srcdir@/m17nlib.css
# HTML_STYLESHEET =
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
# 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 = @srcdir@/header.tex
+LATEX_HEADER = header.tex
# 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
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
# generate man pages
-GENERATE_MAN = no
+GENERATE_MAN = %GENERATE_MAN%
# 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
# only source the real man page, but without them the man command
# would be unable to find the correct page. The default is NO.
-MAN_LINKS = yes
+MAN_LINKS = NO
#---------------------------------------------------------------------------
# configuration options related to the XML output
# or name=definition (no spaces). If the definition and the = are
# omitted =1 is assumed.
-PREDEFINED =
+PREDEFINED = FOR_DOXYGEN
# 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.
# documentation is located. If left blank the absolute path to the
# documentation, with file:// prepended to it, will be used.
-DOC_URL = http://mule.m17n.org/m17n-lib/%DEV_OR_USR_OR_JA%/html/
+DOC_URL = http://mule.m17n.org/m17n-lib/%USR_JA_DEV%/html/
# 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 = @srcdir@/%DEV_OR_USR_OR_JA%/html
+DOC_ABSPATH = @abs_srcdir@/%USR_JA_DEV%/html
# The BIN_ABSPATH tag must point to the directory where the doxysearch binary
# is installed.