| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In the PDF version of the doxygen manual we see that for the `\image` command the chapter title the text runs into the margin (due to an unbreakable part).
With this fix the problem is solved.
(see also: https://tex.stackexchange.com/questions/474055/section-title-running-into-margin and , for the ifstar part, https://tex.stackexchange.com/questions/376375/using-ifstar-to-define-a-star-variant)
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Remove some doxygen warnings in internal documentation
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Generating the doxygen internal documentation gave some warning messages, these have been corrected.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Latex code double minus goes to endash
|
| | |/ / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In case in code 2 consecutive minus signs are present they are shown as endash.
using the same code as in the non code part solves the issue.
Issue can e.g. be seen in cpp source code (with e.g. i--) and in the doxygen documentation in the paragraph "Comment blocks in VHDL"
This is a regression in 1.8.15
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
The `...` argument was not documented in case of inline parameter documentation, with `\param` it was possible to document the `...` argument.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
issue #6840 Hash character in Markdown code span not rendered correctly
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
A hash sign has a special meaning, so it should be escaped in a code span.
|
| | | | | | | |
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
A hash sign has a special meaning, so it should be escaped in a code span.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Bug 399222 - SORT_BRIEF_DOCS produces wrong results
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
Grouped brief (with `\{ ..\}` descriptions were not sorted when `SORT_BRIEF_DOCS` was set, the detailed documentation was sorted already.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Incorrect layout of class index (HTML)
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Regression of #6663
When looking at the example of #4935 the sorting and layout is correct in 1.8.14 but the layout is incorrect in 1.8.15.
The incorrect layout is due to #6663 where a special case was solved for XHTML, the correct procedure should have been that in case of a table row without cells a dummy cell is added.
The changes from #6663 have been reverted and the fix has been corrected (the special case occurred in the doxygen diagrams example).
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Adjustment of xhtml1-transitional.dtd
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Some more ...
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
- mapping changed due to missing `doxygen=`
- externalRef part changeddue to missing`doxygen=`
|
| | |/ / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
After small discussion conclusion was better to remove the obsolete `doxygen=`
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | |
| | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_136299
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Besides the `p` tag there were a number of other tags were also the attributes were lost:
- `br`
- `hr`
- `a` in case of used as an anchor i.e. with the `name=` attribute
In case of a `caption` with a `table` and no `id=` attribute with the `caption` there was still an anchor generated
In scanner.l the warnings message was a bit unclear.
|
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
issue #6830 Message: graph_legend:39: error: Prevented to copy file <path_to_html_output>/graph_legend.png onto itself!
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
<path_to_html_output>/graph_legend.png onto itself!
In version 1.8.14 the message "Source and Destination are the same!" was given, this message could not be suppressed as can be done with normal warnings, this was corrected in 1.8.15 but backfires in case `WARN_AS_ERROR` is set. The problem only occurs when the output directory is searched for images.
Removed the message as it does not contain real information.
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | |/ / / /
| |/| | | | |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Bug 766508 - missing comments of overridden methods
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Analogous to python also for PHP and Java all functions are by default virtual (for python fix see problem #6566 and fix #6570)
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Double id for tooltips in XHTML possible.
|
| | | |_|_|/ /
| | |/| | | |
| | | | | | |
| | | | | | | |
The tooltips (XHTML) should not be displayed per code fragment but for the entire (output) file as otherwise tooltips might be added multiple times resulting in double IDs.
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Bug 626582 - Function overloads are not actually sorted in member function list
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | | |
List was only sorted on member names, now also subsequently sorted on arguments.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Bug 141919 - Wrong param and exception style in RTF output
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Some small improvements in the different formats based on the problems signaled with the issue
- doxygen.css make exceptions in line with other tables (i.e. the appearance of the name of the exception)
- doxygen.sty, rtfdocvisitor.cpp between items in e.g. Precondition, Postcondition, Note place a paragraph distance (like in main text)
- docbookvisitor.cpp handle title of Rcs and User sections correctly
.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
issue #6828 Physical newlines (^^) in ALIASES configuration tags not working with sections, subsections, subsubsections and paragraphs
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
with sections, subsections, subsubsections and paragraphs
Previous changes corrected use of _linebr, missed one so this was not handled properly.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
ignored
In case of Cpp we also have to consider the case of strings that can contain the `[[...]]` part.
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ignored
Only ally the rule `<*>"[["` for Cpp
See also fix d8001efd89146e04d92f5ea41ab27a7de09b6c53 i.e. Problem parsing c++ gnu::visibility (Origin: bugzilla #787952) #6259
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
operators in 1.8.15
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Portuguse translators updated to Doxygen 1.8.16.
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Warning for documented return of void type function
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In case a void type function is documented it is not allowed to used a `\return` or `\retval` command. The test was present but not correct
- test on `g_hasReturnCommand ` which signals whether of not `\ret...` is used instead of `g_memberDef->hasDocumentedReturnType()`
- removed test on emty return type (empty return type is assumed to be non void, see e.g. C, Fortran).
- order of the tests is important
|
|\ \ \ \ \
| | | | | |
| | | | | | |
issue #6812 Empty lines are lost when copy-pasting from code section.
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
In case of an empty line insert an space so the line will be shown with copy & paste (including the space!).
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Problem occurs when a line with just a `*` is followed by another line with an `# and some comment. The test on newline has been removed.
Problem is most likely a consequence of Bug #5288 - Asterisks in comment wrongly displayed for @code, i.e. 23f337e64b95d3fa08f32980c866669b190c872f
|
| | | | |
|