| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Implementation of the C++2x three-way / spaceship operator.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having a text like:
```
https://storm-irit.github.io/OpenGR/, 2017.
```
the corresponding link will contain the comma as well although this is not intended.
The original problem comes from CGAL, where we have a bibliography entry:
```
@misc{ cgal:m-ogr-17,
author = {Nicolas Mellado and others},
title = {OpenGR: A C++ library for 3D Global Registration},
howpublished = {https://storm-irit.github.io/OpenGR/},
year = {2017}
}
```
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not all possibilities in respect of `\*only` and `\end*only` commands were present which could lead to messages like:
```
.../aa.h:4: warning: reached end of comment while inside a \rtfonly block; check for missing \endrtfonly tag!
../.aa.h:4: warning: rtfonly section ended without end marker
.../aa.h:4: warning: rtfonly section ended without end marker
```
in case of a problem like:
```
/** \file
* \rtfonly
* RTF /* Nested */
* \endrtfonly
*/
```
|
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_formula
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having a problem like:
```
/** \file */
/**
* The fie
*
* @form: the new format
* @content: the content of the form
*
* Sets @form content to be @content.
*
* \f$ \alpha \f$ \f[ \beta \f]
*/
void fie(char *form, char *content);
```
we get warnings like:
```
.../aa.h:5: warning: Wrong formula id -1
.../aa.h:6: warning: Found unknown command '\content'
.../aa.h:8: warning: Wrong formula id -1
.../aa.h:8: warning: Found unknown command '\content'
```
The `@form:` is in RST analogue to the doxygen `@param form` but not understood by doxygen.
The result is that it is seen as an formula as doxygen translates the formula commands to `\form`.
For `@content` is handled properly as this is not a doxygen command.
In this patch a more unique name is chosen so these type of conflicts don't appear (that easy). The resulting, better, warnings are now:
```
.../aa.h:5: warning: Found unknown command '\form'
.../aa.h:6: warning: Found unknown command '\content'
.../aa.h:8: warning: Found unknown command '\form'
.../aa.h:8: warning: Found unknown command '\content'
```
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_html_s
|
| | |
| | |
| | |
| | |
| | |
| | | |
Adding the HTML `<s>` tag (https://www.w3schools.com/tags/tag_s.asp).
Adding 's' and correcting 'inc' to 'ins' in compound.xsd
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_unsupported_html
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having a problem like:
```
/** \file
- Just name <name>
- name plus subname <name subname>
- name plus twice subname <name subname subname>
- name plus subname subname="" <name subname subname="">
*/
```
we get correctly the warnings:
```
.../aa.h:3: warning: Unsupported xml/html tag <name> found
.../aa.h:4: warning: Unsupported xml/html tag <name> found
.../aa.h:5: warning: Unsupported xml/html tag <name> found
.../aa.h:6: warning: Unsupported xml/html tag <name> found
```
but the output doesn't look good as there is `=""` added:
```
Just name <name>
name plus subname <name subname="">
name plus twice subname <name subname="" subname="">
name plus subname subname="" <name subname="" subname="">
```
This patch fixes this output.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_nospam_email
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having a simple nospam email address coded like:
```
/** \file
* Big Unknown <big at none dot com>
*/
```
this results in the warning:
```
aa.c:2: warning: Unsupported xml/html tag <big> found
```
and in the HTML output it looks like:
```
Big Unknown <big at none dot com>
```
instead of:
```
Big Unknown <big at none dot com>
```
(Found in a couple of open source projects).
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
virusxp-memory_leakage_fix
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
namespace
Fixing some memory issues caused by not correctly freed pointers
|
|/ / / |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Spelling corrections as found by codespell and in #561.
Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.):
- "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...)
- "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A HTML attribute name can have e.g. a XML namespace in it and thus containing a colon (`:`) like:
```
<span xmlns:dct="http://purl.org/dc/terms/" property="dct:title">Social Icons</span>
```
but this results in
```
warning: found </span> tag without matching <span>
```
and grabled outpuzt.
allowing a colon in the attribute name solves this problem
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_consistency_state_2
|
| | |
| | |
| | |
| | |
| | | |
Create a consistent way to display the state mnemonics of the different scanners (analogous to the fortranscanner.l)
Use an automatic procedure to generate the routine with the translation of the states to a string.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When having:
```
* IRC: irc://irc.gimp.org/#gsconnect
```
we get:
```
warning: explicit link request to 'gsconnect' could not be resolved
```
When using the 'news:" protocol we don't get this message, adding 'irc' to the list of possibilities.
(Found in https://github.com/andyholmes/gnome-shell-extension-gsconnect )
|
|/ /
| |
| |
| | |
after @ref (try 2)
|
|/
|
|
| |
null pointer fix)
|
|
|
|
|
|
| |
In the docbook ouput this was shown with the attribute `nowrap>=''`, in HTML this empty tag was skipped.
Normally a HTML attribute will have a value but in some cases it is possible without attribute and when this is the last attribute the `>` was accidently added to the attribute (in case of the value the `>` was already considered).
Furthermore `In XHTML, attribute minimization is forbidden, and the nowrap attribute must be defined as <td nowrap="nowrap">.`, this is now handled for HTML and docbook as well.
|
|\
| |
| |
| | |
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.
|
|\ \
| | |
| | | |
Conflict between RCS tag and (e.g.) php description
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In some languages the `$` is used to start a variable name (php, perl).
When having a description like:
```
<b>$RRDp::error_mode</b>, <b>$RRDp::error</b>
```
this will lead to a message like:
```
warning: found </b> at different nesting level (4) than expected (2)
```
because the part `$RRDp:` is seen as start of a RCS tag and runs till the next `$`.
Though the `::` indicates here a class / namespace separator and in case of `$...:` directly followed by a `:` this should not be seen as RCS tag.
|
|/ /
| |
| |
| | |
In case of `\includedoc` the `\n` was not handled on the first line (`@startuml`)
|
|/
|
|
| |
Also in HTML tag handling.
|
|
|
|
|
|
| |
suspicious text
To escape `\` and `@` not only `\\` and `@@` should be possible but also `\@` and `@\`
|
| |
|
|\
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Changes:
- Use of `@emoji name` instead of `:name:`
- Support only GitHub emojis (i.e. without spaces or special characters in the name)
- Provided script to download images for LaTeX support.
- XML output now has <emoji> tag with name an unicode sequence.
|
|\ \
| | |
| | | |
issue #6691 Multiple issues with emoji matching
|
| | |
| | |
| | |
| | |
| | | |
This fix is regarding the false positive emoji detection of scope rules like: `Platform::*Application::viewportEvent(const Vector2i&)`
In case the "emoji" is followed by and extra `:` it is not seen as an emoji anymore.
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
The attribute values of the `align` and `valign` attribute have to be in lowercase and the `valign` attribute value `center` does not exist but has to be `middle`.
Most browsers do accept the 'incorrect' values but it is better to have the right values present.
(Found by means of the CGAL/cgal repository)
|
| |
| |
| |
| |
| |
| | |
Analogous to the `\htmlonly` also with the `\htmlinclude` command it is possible that some parts are added that cannot be inside a `<p> ... <\/p>` and thus we have to temporary close (and later reopen) the paragraph.
The option `[block]` has been added to the `\htmlinclude` command (analogous to the `\htmlonly` command).
Problem can be seen with the default doxygen test 30 (`[030_htmlinclude.dox]: test the \htmlinclude command`).
|