| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
- setting RECURSIVE (required for directories)
- making check / adjust consistent with doxyparse
|
|
|
|
|
| |
- initialization has to be done in an earlier stage (and only once)
- not only the INPUT tag was involved, none of the tags were set.
|
|\
| |
| | |
issue #7110 URL Encoding for Hyperlinks in PDF
|
|/
|
|
| |
For an URL also the percentage (`%`)sign has to be escaped
|
|\
| |
| | |
issue #7102 Doxygen does not generate error/warning message for unbalanced group markers "@{"..."@}"
|
| |
| |
| |
| |
| |
| |
| |
| | |
group markers "@{"..."@}"
There are 2 sorts of grouping, with and without preceding group command.
In case og a preceding group command a warning was already issued, but without preceding group this was not done
Also corrected wrong order of `\{` `\}` commands, i.e, when we see more closing before opening commands.
|
|\ \
| | |
| | | |
Remove not used class
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As per comment in `docvisitor.h`:
```
class DocCopy; // TODO: no longer generated => remove
```
|
|\ \ \
| |/ /
|/| | |
Bug 642126 - @mscfile <filename> does not process mscgen code
|
| | |
| | |
| | |
| | | |
Small explanation about required syntax.
|
|\ \ \
| | | |
| | | | |
High consequence coverity mesages
|
| | |/
| |/|
| | |
| | |
| | | |
- initializing fd (analogous to htmldocvisitor)
- always good to close file pointers
|
|\ \ \
| |/ /
|/| | |
issue #7104 Warning with preprocessor
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The test on 'defined' has to be done earlier as otherwise the replacement (limited to 2 defined is enough for the test) of
```
(defined(__AVR_ATmega644RFR2__)||defined(__AVR_ATmega256RFR2__))
```
will be
```
` ! (defined( 0 )||0( 0 )) '
```
instead of
```
` ! (defined( 0 )||defined( 0 )) '
```
|
|\ \
| |/
|/| |
Correction obvious documentation errors in mscgen
|
|/ |
|
|\
| |
| | |
doxysearch: added wildcard, partial and phrase sesarch
|
| | |
|
|\ \
| | |
| | | |
regression #6885 mscgen links placed in the wrong place when using SVG output
|
| |/
| |
| |
| | |
The output files were not placed in the output directories but in the "root" directory (the `.msc` files were correctly placed in the output directories).
|
|\ \
| | |
| | | |
Update documentation for msc
|
| |/
| |
| |
| | |
Due to the built in mscgen code the documentation needed some updates.
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Added bison 3 requirement for OSX build on Travis CI
|
|\ |
|
| |\
| | |
| | | |
issue #7033 Syntax highlighting doesn't work when calling \dontinclude from Markdown files
|
| | |
| | |
| | |
| | |
| | |
| | | |
Markdown files
Don't use the file name extension of the including file but of the included file. In case of no included filename or no extension, fall back of the file extension of the including file.
|
|/ / |
|
|\ \ |
|
| |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_case_sense
|
| | |
| | |
| | |
| | | |
In case special characters in a filename need escaping into something like: `_0` the `0` should not be followed by an uppercase character as this would be in contradiction wit the setting `CASE_SENSE_NAMES=NO`.
|
|\ \ \
| | | |
| | | | |
Incorrect (X)HTML code when generating source code.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \
| | | |
| | | | |
(X)HTML warning when `[` or `]` in constructed ids
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we have a construct like:
```
template <typename Element, size_t N>
class StlContainerView<Element[N]> {
public:
typedef internal::NativeArray<RawElement> type;
};
```
this will lead to files with `[` and `]` in it, as such not nice, but it is used in ids inside the code as well like:
```
id="aclass_stl_container_view_3_01_element[_n]_4_html_a1bf60158ff15896f2b53af11c09524fb"
```
running
```
xmllint --path ..../testing/dtd --noout --nonet --postvalid html_org/*html
```
this leads to the message:
```
Syntax of value for attribute id of div is not valid
Document html_org/test_8h_source.html does not validate
```
escaping the `[` and `]` as done with other special characters solves this problem
|
|\ \ \
| | | |
| | | | |
update jQuery version mentioned in README to 3.4.1
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Bug 796582 - Doxygen has stopped working
|
| |/ /
| | |
| | |
| | |
| | | |
In (the rare) case the path is not set don't try to use the pointer.
regression on pull request #513
|
|/ / |
|
|\ \
| | |
| | | |
Missing brief descriptions with `\defgroup`
|
| | |
| | |
| | |
| | | |
Test 19 was incorrect, didn't show group description either (see make tests TEST_FLAGS="--keep --xhtml --id=19"
|
| | |
| | |
| | |
| | |
| | | |
Due to the fact that issue #6945 ended a brief description, all following was put into the detailed description (unless explicit \brief was used). The `\defgroup` should end the current brief description, but first line of the `\defgroup` should be seen as a new brief description.
Problem can be seen with in the doxygen documentation in the example in the Grouping part and also with #7053 a small example is given in the comment.
|