| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Let $year support SOURCE_DATE_EPOCH
|
| | |
|
|\ \
| | |
| | | |
issue #7119 Doxygen does not link to C# snippets - regression
|
| |/
| |
| |
| | |
Looks like the `isLinkableIeInProject` is a bit to strict and `isLinkable` has to be used (also the original pull request #6489 still works OK).
|
|\ \
| | |
| | | |
Properly open quotes in warning
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit 78b5c44 'Properly close quotes in warning' https://github.com/doxygen/doxygen/pull/7312 handled the case that a closing quote was missing in case of a missing closing quote.
I case the word template is missing it is possible to miss the opening quote, resulting in:
```
wxWidgets-3.1.3/src/x11/brush.cpp:66: warning: no matching class member found for
wxBrush::wxBrush(const wxColour &col, int style)
Possible candidates:
wxBrush::wxBrush()'
wxBrush::wxBrush(const wxColour &colour, wxBrushStyle style=wxBRUSHSTYLE_SOLID)'
```
this is fixed here.
|
|\ \ \
| | | |
| | | | |
RTF extension file to standard output, make according documentation consistent.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Create possibility to write rtf extension file to standard output as well, see to it that same technique is used on different places
Update documentation and make it consistent
|
|\ \ \ \
| |_|/ /
|/| | | |
issue #7328 Cannot generate DoxygenLayout.xml
|
| |/ /
| | |
| | |
| | | |
Problems with generating the DoxygenLayout.xml on a system the language set to Russian, set encoding for file.
|
|\ \ \
| |_|/
|/| | |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Support for <a id="label">
|
| |/
| |
| |
| | |
Support besides `<a name="label">` also `<a id="label">` as `id=` is the HTML attribute to define an ad for an HTML element.
|
|/
|
|
| |
This reverts commit ed4515149fd0839dba1f59858aec37b73c0ac805.
|
|\
| |
| | |
Incorrect warning for ALIASES
|
| |
| |
| |
| |
| |
| |
| |
| | |
In case we have an alias in the form: `mine_err(1)=\1` we get the warning:
```
error: Illegal alias format 'mine_err(1)=\1'. Use "name=value" or "name(n)=value", where n is the number of arguments
```
Note the round brackets in the explanation., these have to be curly brackets.
|
|\ \
| | |
| | | |
Properly close quotes in warning
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Found warning like:
```
Possible candidates:
'template < T >
gmic::gmic(const T &pixel_type=(T) 0)
'template < T >
gmic::gmic(const char *const commands_line, const char *const custom_commands=0, const bool include_stdlib=true, float *const p_progress=0, bool *const p_is_abort=0, const T &pixel_type=(T) 0)
'template < T >
gmic::gmic(const char *const commands_line, cimg_library::CImgList< T > &images, cimg_library::CImgList< char > &images_names, const char *const custom_commands=0, const bool include_stdlib=true, float *const p_progress=0, bool *const p_is_abort=0)
```
Note the starting quote `'` but there is no closing quote (in case of a file and line the closing quote is present.
|
|\ \ \
| | | |
| | | | |
Warning when using empty HTML tag
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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.
|
|\ \ \
| |/ / |
|
| |\ \
| | | |
| | | | |
Bug 570798 - \\\< does not work for php constants
|
| | |/
| | |
| | |
| | | |
Handle comment for define analogous to a normal php variable, the closing part is automatically done when the comment is finished (rule: `<DefinePHPEnd>";"`).
|
| |\ \
| | | |
| | | | |
issue 7302: Parsing of template args in single-quotes is incorrect.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In case we encounter an unescaped single or double quote during specialization we search for the closing quote.
We are cionnsidering potential escape sequences in the strings as well.
|
| |\ \ \
| | | | |
| | | | | |
Fix typos
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | | |
Found via
```
codespell -q 3 -S *.js,*.po,./src/translator*,*.eps,./doc/changelog.doc -L ang,ans,attribs,ba,behaviour,classe,colour,german,iff,initialise,nam,nd,que,russian,statics,te,tim,uint
```
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we use the doxygen inheritance diagrams in doxygen (i.e. `HAVE_DOT=NO`) for a construct like (based on #7302):
```
template <char C>
struct one { };
/// The struct str_040
struct str_040 : one<'('> { };
```
this will lead to a postscript error (epstopdf) as the `(` (and analogous the `)`) have to be escaped.
|
|/ / |
|
|\ \
| |/
|/| |
|
| | |
|
|/
|
|
| |
Regression on #7050 / #7053 (Physical newlines (^^) not working in group names and without spaces in 1.8.15), in case the current name was explicitly set to mainpage it was still overwritten.
|
|
|
|
| |
with same name
|
|
|
|
| |
to process the string contents
|
|\ |
|
| |\
| | |
| | | |
HTML attribute name
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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-fetaure/bug_340202
|
| |/
| |
| |
| |
| |
| |
| | |
The `*_cast` had already been introduced, but there were some other places that needed the "REJECT" as well.
Also the cast was missing a whitesace between the cast name and the `<`.
Tested also against he doxygen internal documentation.
|
|/ |
|
| |
|
|
|
|
| |
In pre part always use `\string~` for `~` otherwise it will be translated to a space.
|