| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| |
| |
| |
| | |
Consistency
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_gitversion
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The original version has as features:
- getting the git version number for usage in doxygen
- making the doxygen version number inclusion dependent on the VERSION file
The disadvantage of the chosen methodology was that an extra correction step was necessary, by defining getter methods to retrieve the values this correction can be hidden.
The information is coming from different sources:
- the VERSION file
- the git "repository and build system (when present)
Furthermore there are a couple of places where the version information is used (a.o. doxygen and doxywizard executable, though the doxygenwizard was only done "half hearted")
The handling of the VERSION file has been made in such a way that it is comparable with the generation of the git version changes.
For a better abstraction the version handling is all done in a separate directory.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having the example:
```
/*! \file
* \brief
* Prerequisite header file
*/
//! \cond
#ifdef HAVE_CONFIG_H
#include "gmxpre-config.h"
#endif
//! \endcond
```
and we run xmllint on it:
```
xmllint --path .../testing/dtd --noout --nonet --postvalid html/*.html
```
we get the messages:
```
html/aa_8h_source.html:75: parser error : Opening and ending tag mismatch: div line 67 and body
</body>
^
html/aa_8h_source.html:76: parser error : Opening and ending tag mismatch: body line 17 and html
</html>
^
html/aa_8h_source.html:77: parser error : Premature end of data in tag html line 2
^
```
It looks like the problematic part in this case is the doxygen type comment at the end of the file.
In the past similar situations were present in LaTeX (related to maximum line length correction), but it was only fixed for LaTeX.
Besides the change for HTML also small changes were necessary for RTF and docbook.
|
| |/
|/| |
|
|/ |
|
| |
|
|
|
|
|
| |
- In a RTF list after the last indent a number of extra paragraphs were displayed (with e.g. bullets), these extra paragraphs are removed
- Increased the number of levels conform the changes for latex (#6622)
|
|
|
|
| |
The layout was so that lines were stretched to to complete lines from left to right (Justifid). For "normal" text this is fine, but not for lists like this, so set alignment here to: Left aligned
|
|\
| |
| | |
Missing opening round bracket in case of an exception
|
| |
| |
| |
| |
| | |
In case of RTF / LaTeX the opening round bracket was missing after the word "throw"
(see e.g. in the manual the `\fn` example the detailed function description)
|
|/ |
|
| |
|
|
|
|
| |
Made implementation analogous to the implementation for parameters in respect to padding and the use of colon (:).
|
|\
| |
| | |
Wrong spelling of word doxygen
|
| |
| |
| |
| | |
Corrected spelling Doxgyen -> doxygen and added space for better readability
|
|\ \
| | |
| | | |
Syntax highlighting / code coloring in RTF
|
| |/
| |
| |
| | |
Although stated in the Doxyfile that for RTF source code syntax highlighting should be present this was not the case.
|
|\ \
| | |
| | | |
Bug 782754 - rtf generation
|
| |/
| |
| |
| |
| |
| | |
Looks like problem has been introduced with the fix for bug 445105 (release 1.5.3), in this case the \par is necessary.
The fix for bug 741547 (pull request #596) is related to this problem and the fix here is not necessary with this fix.
Related to bug 778525, here 2 problems occur and the mangling is solved with this patch.
|
|\ \
| | |
| | | |
Bug 774597 - Title in rtf file is incorrect when overridden by user in extension file
|
| |/
| |
| |
| |
| |
| | |
extension file
Corrected title in case of extension file used.
|
|\ \
| |/
| |
| |
| | |
# Conflicts:
# src/translator.h
|
| |
| |
| |
| | |
Small alignment improvement of HTML output for VHDL Ports so that the mode will be in a separate column
|
|/ |
|
|
|
|
|
| |
Super trivial typos
Some are in qtools/ which I know is a 3rd party dependency but as we know is now obsolete upstream. I reckon it wouldn't be much of an issue to merge neverthless
Tacked on several more commits
|
| |
|
|
|
|
|
|
|
| |
by..." for CSS
Added class= to html output for "Definition at..." resulting in p.definition in the css file and for "Referenced by .. " and "References ..." resulting in p.definition in css file.
(also corrected some error messages).
|
| |
|
| |
|
|
|
|
| |
improve performance
|
|
|
|
|
|
|
| |
Example section lacked of new paragraph(\par) because
writeExample set m_omitParagraph = TRUE
When the output file was open in MS word, example file name was
followed by function title in the same line.
|
|\
| |
| | |
Bug 682373 - Math does not work in LaTeX with custom header and footer.
|
| |
| |
| |
| | |
Reset current directory in case of return.
|
| |
| |
| |
| |
| | |
Removal of "begin body" from text (only visible in Open and Libre Office, not in Word).
Replace AUTHOR by the author specified in rtf configuration file.
|
| |
| |
| |
| | |
Translate the word Version as well.
|
|/
|
|
| |
Set the TITLE as the PROJECT_NAME and the CREATEDATE as the date of creation.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Based on the request http://stackoverflow.com/questions/27036474/how-do-make-doxygen-generate-index-color-png-files for index colored png files, this functionality will be included in the newer versions (2.39) of dot.
The functionality -Tpng:cairo:gd will automatically be used by doxygen, though the file extension would be wrong (.png:cairo:gd).
With this patch the :cairo:gd is stripped from the image extension, but not from the -T of the dot command.
In the doxywizard the different possibilities are supplied as well. Note however that the DOT_IMAGE_FORMAT name is not checked when read from the Doxyfile so it is possible to use other renderer / formats as well due to the generic solution with getDot ImageExtension.
|
|
|
|
| |
correctly sized.
|
| |
|
|
|
|
|
| |
Also made dangerous string access more visible by introducing rawData().
This replaces data() which will now return a constant string.
|
|
|
|
|
| |
Analogous to Latex and HTML output the possibility to have source code shown in RTF output is created.
Based on question: http://doxygen.10944.n7.nabble.com/RTF-lack-of-source-code-tc6936.html
|
| |
|
|
|
|
|
|
| |
1. New Feature: Adapted Class Graph generation for DOCBOOK
2. Fixed DOCBOOK Code documentation formatting
3. Fixed Doxygen to handle FULL_PATH_NAMES for DOCBOOK generation
|
| |
|
|
|
|
|
|
|
|
|
| |
- operations on current index and node (next(), prev(), last(), first()) have been removed.
- access to internal nodes has been removed.
- old QList has been renamed to QInternalList for use inside qtools only.
- added type safe compare, new, and delete operations (compareValues(), newValue(), deleteValue()).
- add compareValues also to QDict for consistency.
- changed doxygen's implementation to comply with the new QList and QDict interface.
|