| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to the fact that an empty HTML tag (like `<strike/>` is seen as a start tag the rest of a documentation block is handled with the strikethrough. Same problem occurs for other tags as well, in most cases empty HTML tags should be left out of the output (and just give the warning about the empty tag).
Mentioned example:
```
/**
Before a strike:
<strike/>
after strike
*/
void fie_b_strike(void);
```
|
|
|
|
|
|
| |
- the HR tag has in xhtml the form <HR/>. Supporting empty tag
- better warning (with tag name, for empty tag.
- `</hr>` does not exist, correcting warning (analogous to `</br>`)
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we use the construct:
```
<p/>
```
we get the warning:
```
warning: HTML tags may not use the 'empty tag' XHTML syntax.
```
tough the construct is handled properly, so we can omit the warning.
|
| |
|
|
|
|
| |
null pointer fix)
|
| |
|
|\
| |
| | |
Bug 632754 - The \copydoc Command Requires The Use of C++ Syntax in C# Code
|
| |
| |
| |
| | |
Replace the scope separators to the default scope separators (::) of doxygen.
|
|\ \
| | |
| | | |
Missing warning about ambiguous files
|
| |/
| |
| |
| |
| | |
- Handling of ambiguous files (in case of an ambiguous file `fd` does return a value)
- using correct dictionary for warning
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| |/
| |
| |
| | |
Consistency
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are 2 different situations here:
- @var, here a special change is necessary to check and handle whether or not we are in PHP (declinfo.*, doxygen.cpp)
- @param
- the type recognition for the PHP type has to be extended with the `[]` possibility and subsequently the `[]` part has to be handled separately from the 'datatype' (doctokinizer.l, docparser.*).
- In the output we now can have multiple text strings resulting in a small change in handling of the separator between the data type (*docvisitor.*)
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-fetaure/bug_html_ins_del_tag
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Github does not support the `<u>` tag for underlined text, in HTML there exists the tag `<ins>`. On https://www.w3schools.com/tags/tag_ins.asp is written:
The `<ins>` tag defines a text that has been inserted into a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<ins>` element with the following default values:
```
ins {
text-decoration: underline;
}
```
analogous there exists the tag `<del>` (https://www.w3schools.com/tags/tag_del.asp):
The `<del>` tag defines text that has been deleted from a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<del>` element with the following default values:
```
del {
text-decoration: line-through;
}
```
Definitions analogue to the underline and strike through tag the implementation for the other formats has been chosen.
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_retval_mult
|
| | | | |
| | | | |
| | | | |
| | | | | |
Analogous to arguments when they have multiple `\param` commands this is also done when a return value is specified multiple times with the `\retval` command
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6925
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In general ATX headers ('#' headers and other markdown ) are converted to doxygen `\section` etc. commands
In case not all levels of doxygen commands are present so like;
```
\section sect1 Section
....
\subsubsection subsubsect1 Sub sub section
```
the information of the `\subsubsection` is not shown. Same happens in case the `\section` is not present at all.
Part of the steering of the ATX headers is done by means of the configuration setting TOC_INCLUDE_HEADINGS (default is 5) setting this setting to '0' will not convert the '#' headers to `\section` etc. (but this as side note).
Basic problem is fixing the not shown headers in case of missing levels in the `\section` commands.
- In case the `\section` command does start the page
- In case the `\section` command does not start the page.
Case the `\section` command does start the page: this is handled in the routine `int DocSection::parse()`
- see to it that not only the exact matching level is handled but also the 'jumps' in levels
- loop all 'section' of the found type and its sub sections and only jump out in case of the 'jump' level case
- give a warning in case of a 'level jump'
Case the `\section` command does not start the page: this is handled in the routine ` void DocRoot::parse()`
- as e.g. `\paragraph` could be followed by a `\subsubsection` each section type has to be handled one after another (otherwise higher types would not be handled)
- note the order is important therefore a `\subsubsection` has to be handled after a `\paragraph.
- due to the different handling the 'TK_LISTITEM' has to be handled at the end (each part can also give a 'TK_LISTITEM'
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Incorrect warning message
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In case we have e.g. the comment:
```
* @b: first
```
We get the warning message:
```
warning: expected whitespace after : command
```
instead of a better understandable:
```
warning: expected whitespace after \b command
```
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As per comment in `docvisitor.h`:
```
class DocCopy; // TODO: no longer generated => remove
```
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/svg_image_determnation
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In case a svg image url has some decoration behind it, the image is not seen as a svg image. The decoration is taken away from the determination.
Found by means of:
```
[![Build Status](https://api.travis-ci.com/ILIAS-eLearning/ILIAS.svg?branch=release_5-3)](https://travis-ci.com/ILIAS-eLearning/ILIAS)
[![Minimum PHP Version](https://img.shields.io/badge/php-%3E%3D%205.6-8892BF.svg)](https://php.net/)
```
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_init_fd_line
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In case thee `line` command is used without previous `\inclide` or `\dontinclude` command doxygen will crash due to a non initialized fd.
We get the message:
warning: No previous '\include' or \dontinclude' command for '\line' present
also a small correcting regarding the warning message is done.
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_lineno_split_examples
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the commands like `\skip`, `\skipline` it is possible to show parts of a file for further explanation / tutorials. They can be started with `\include` or `\dontinclude` but in case `\include` specifies that the line numbers have to be shown they are only shown in the full example and not in the split up example
- show line numbers in split up example in case `lineno` is required
- add `lineno` option to `\dontinclude` so here also line numbers can be shown.
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
Create a warning in case no `\include` or `\dontinclude` command has been given before using `\skip`, `\line`, `\skipline` or `\utnil`
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
<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.
|
|/
|
|
|
|
|
| |
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
|
|
|
|
| |
Don't add the argument to list of parameters in case of a non-parameter call (i.e. retval call)
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_escaped_equal_sign
|
| |
| |
| |
| | |
This command writes an equal sign (`=`) to the output. This character sequence has to be escaped in some cases, because it is used in Markdown header processing.
|