| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
issue #7762 C# mode completely broken
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
In case a `#` is used in the path this is not escaped and this gives a problem in label names for LaTeX and in file references for HTML>
|
|\ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / /
|/| | | | | | | | | |
|
| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
|/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7747
|
| |/ / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Implementation of the C++2x three-way / spaceship operator.
|
|\ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
On subsequent calls we should know which inkscape version we have when this is not the case we already tried to determine it, but it failed so we should bail out here without error as an error has already been given.
|
| |/ / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The command line interface (CLI) of Inkscape 1.0 has changed in comparison to previous versions. In order to invoke Inkscape, the used version is detected and based on the version the right syntax of the CLI is chosen.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Normal users of github cannot set labels to issues.
|
|/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When having a very long initialization line in php code we get the message:
```
input buffer overflow, can't enlarge buffer because scanner uses REJECT
```
In this case the, easy, solution is to split, in the lexer, the input based on the commas.
|
| | | | | | | | |
|
|/ / / / / / / |
|
| | | | | | | |
|
| |/ / / / /
|/| | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|/ / / / / |
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When we have code like:
```
//!
//! \f$a \times
//! c \f$
//!
```
this will throw a warning like:
```
warning: End of comment block while inside formula.
```
due to the fact that after the comment conversion the code is like:
```
/**
* \f$a \times
//! c \f$
* */
```
Comparing to the `///` comments:
```
///
/// \f$a \times
/// c \f$
///
```
we get
```
/**
* \f$a \times
c \f$
* */
```
This discrepancy has been removed.
|
| | | | | | |
|
| | | | | | |
|
|/ / / / / |
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When having a code comment like:
```
@code
sub postprocess
{
s/\(?\@xref\{(?:[^\}]*)\}(?:[^.<]|(?:<[^<>]*>))*\.\)?//g;
s/\s+\(\@pxref\{(?:[^\}]*)\}\)//g;
}
@endcode
```
and using MathJax the `/(` is seen as a the beginning of a formula, but should be seen as text and can now lead to "Undefined control sequence".
(The problem comes originally from code as generated by the doxygen-perl-filter for converting perl code in something doxygen does understand).
This problem is similar to the problems solved in pull request #7697, but not handled here.
This pull request will see `\(` (and its counter part `\)` as complete entities and replace them in a similar way as done in #7697 (but now in an earlier stage but the `‍` will be properly filtered in the different output formats.
|
|/ / / / / |
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
For the configuration setting `HTML_FORMULA_FORMAT` the text reads:
> Possible values are: png The default and svg Looks nicer but requires the pdf2svg tool.
this is not quite understandable and has been reformulated to:
> Possible values are: png (the default) and svg (looks nicer but requires the pdf2svg or inkscape tool).
this concerns automatically generated texts from config.xml to the different formats.
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
|/ / / / / /
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_tag_doxygen
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add doxygen version information to doxygen tag file.
currently this information is not used inside doxygen , but is useful for checking with which version of doxygen is used when debugging problems.
|
|\ \ \ \ \ \ |
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When we have set `HTML_FORMULA_FORMAT = svg` we still get the message:
```
Generating image form_0.png for formula
```
instead of
```
Generating image form_0.svg for formula
```
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
In some cases performance dropped when upgrading from version 1.8.16 to 1.8.17 or 1.8.18.
With these changes the performance should be back to normal again.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |_|/ /
|/| | | |
|
| | | | |
|
| | | | |
|