| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Misleading warning about missing argument
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having a `@struct` command without argument one gets the misleading warning:
```
warning: missing argument after \class.
```
instead of:
```
warning: missing argument after '\struct'.
```
This happens with a number of commands, for these commands the `currentCmd` has been introduced.
(Found in cmake through Fossies).
|
|\ \ |
|
| |\ \
| | | |
| | | | |
Debug facility for the \cite command
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When issuing doxygen with `-d cite` the temporary (copied) files / directory are not removed, i.e.:
- bib*.aux
- bib*.bbl
- bib*.blg
- bib2xhtml.pl
- citelist.doc
- doxygen.bst
- bibTmpDir (directory)
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | | |
|
| |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_cite_crossref
|
| | | |
| | | |
| | | |
| | | | |
unfortunately some more regressions...
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Based on the review
- implemented tip `find("{");` instead of `find("{",0);`
- made `label..` names more expressing their content
- got a few regressions regarding endless loops (it is incorrect bib file syntax), the constructs have to be at the end of the bib file, like (also with extra newlines)
- `@book ,`
- `@book { ,`
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The crossref items in a bib file are unconditionally added to the list of used citations although the the citation to which the crossref belongs to is not used.
This has been fixed. The problem was seen in the CGAL output.
Note: a crossref in LaTeX is a bit different from the normal understanding of cross-reference, from https://tex.stackexchange.com/questions/401138/what-is-the-bibtex-crossref-field-used-for: "crossref can be used if you have multiple entries referring to the same proceeding, book or similar."
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| | | | |
|
| |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_cite_number
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we have a bibtex entry like:
```
@manual{ cgal:as-lum
,author = {Algorithmic Solutions}
,title = {The {LEDA} {U}ser {M}anual}
,organization = {Algorithmic Solutions}
,address = {66123 Saarbr\"ucken, Germany}
,url = {http://www.algorithmic-solutions.info/leda_manual/MANUAL.html}
}
```
this is rendered / referenced like:
```
[Solutions] Algorithmic Solutions. The LEDA User Manual. Algorithmic Solutions, 66123 Saarbrücken, Germany.
```
instead of
```
[2] Algorithmic Solutions. The LEDA User Manual. Algorithmic Solutions, 66123 Saarbrücken, Germany.
```
The problem is that in the resulting "bbl" file from the bibtex command we have the line:
```
<dt><a
name="CITEREF_cgal:as-lum">[Solutions]</a></dt><dd>\bibxhtmlname{Algorithmic
Solutions}.
```
instead of (from another entry):
```
<dt><a name="CITEREF_cgal:mog-vbcfe-11">[Merigot et~al.,
2011]</a></dt><dd>\bibxhtmlname{Quentin Merigot}, \bibxhtmlname{Maks
```
Note the `\n` after the `<a` instead of the (expected) space.
This has been corrected in the regular expression (Note: we need to use `[ \n][ \n]*` as we cannot use the equivalent `[ \n]+` as the `+`- sign has here a different meaning).
|
|/ /
| |
| |
| | |
(another fix)
|
| |
| |
| |
| | |
the included file not its own filename
|
| |
| |
| |
| | |
(fix)
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Also fixed bug preventing direction to be stripped from the parameter documentation.
|
| |\ \
|/ / /
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_direction
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the current version a line like:
```
uint8_t innInstances, ///< [inn]Number of CIP node instances.
```
was seen as an input parameter.
Also not all combinations were checked (`[inout]` was OK but `[outin]` wasn't although `[in,out]` and `[out,in]` were working in the tokenizer.
Line up the detection of the direction between the tokenizer and the method `extractDirection`
Note: this problem was found when working on #7879.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Still requires cmake -Duse_sqlite=YES to compile in support (and
libsqlite3)
New configuration options available:
- GENERATE_SQLITE3 enable/disable SQLITE3 output
- SQLITE3_OUTPUT configure directory where output is written to
(default: sqlite3)
- SQLITE3_RECREATE_DB controls if existing database file is overwritten
(default: YES)
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
string passed.
|
| |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7884
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
(MARKDOWN_SUPPORT=NO)
Corrected handling of the comment blocks. Due to the possible nesting of classes and the handling of the first line special handling is required by means of the stripping of spaces after a return in a doc block (otherwise it might be stripped away multiple times / left multiple times).
|
|\ \ \ \
| |_|_|/
|/| | | |
Prefer more inclusive language
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Doxygen is used for some Android API documentation, hence:
Update language to comply with Android’s inclusive language guidance.
See https://source.android.com/setup/contribute/respectful-code for reference
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Fix compiling with clang parser support and with Clang compiler, too
When compiling the code with the Clang compiler a new CMake option
`use_libc++` is available which is enabled by default. It determines if
the Clang compiler should use libc++ as its C++ standard library or uses
the systems default (e.g. libstdc++ on Linux).
Disabling that option might help when compiling with Clang and the
option `use_libclang` is enabled but the associated library was not
built with libc++ as its C++ standard library.
Additionally, the doxygen executable that is created when CMake option
`static_libclang` is enabled, no longer crashes.
* Removing obsolete (and wrong) forcing of -std=c++11 for GCC
The entire Doxygen project already requires the compiler to run in C++14
mode. That setting is applied globally in the top-most `CMakeLists.txt`
file.
Therefore, forcing GCC to run in C++11 mode in `src/CMakeLists.txt` is
wrong and obsolete.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
issue #7865 Update documentation of USE_PDFLATEX option
|
| | |/
| |/|
| | |
| | | |
Updated texts to better reflect current situation
|
|\ \ \ |
|
| | | | |
|
| |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7923
|
| | | |
| | | |
| | | |
| | | | |
Explicit counting of the removed newlines at the beginning of a documenation block (markdown.cpp) so this number can be added to get a better line number in case of warnings.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- White space around \\ilinebr is not preserved in commentscan
- Cases where \n was unput in doctokenizer are now handled in the same
way for \\ilinebr
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Routines to strip leading and trailing whitespace now also take
\\ilinebr into account
- Added a number of cases in doctokenizer.l where \\ilinebr wasn't
handled yet.
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Changed \_linebr to \ilinebr
- \ilinebr is now also passed to doctokenizer
- Also fixes issue #7493 regarding \snippet inside markdown tables and
dealing with wrong line on issues detected by docparser after a
markdown table.
- Added function tracing to markdown (enabled with -d markdown in a
debug build)
|
| |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7787
|
| | | |
| | | |
| | | |
| | | | |
The artificial newline characters in ALIASES (`^^`) or better said its doxygen replacements (`\\_linebr`) were not seen by the markdown parser as line terminator and as a consequence there was no table seen (it was just 1 long line, without header / data lines)..
|
| | | | |
|
| | | | |
|
|\ \ \ \ |
|