| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having a line of code like:
```
callback_check = re.compile(r'([^\(]*\(.*)(\* *)(\).*\(.*\))')
```
this is seen as an incomplete formula when using MathJax, the `\(` is seen as start of a MathJax formula.
Replacing the backslash by the corresponding code `\` didn't work as this is already translated by the bowser and still picked up by MathJax, so we need `‍` to separate the backslash and the bracket without any spacing.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | | |
The break statement was unintentional left out (found by coverity).
|
|/ / / / |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_cite_comma
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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}
}
```
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7692
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Besides links to functions / classes etc. it is also possible to have a link to a file and a file can contain a dot, so we first have to check the "original" name and when not OK we should also check the replacements.
Regression on #7042
|
| | | | | |
|
| | | | | |
|
|/ / / / |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In case we have a relative reference to a local markdown file this file is not found when the relative path starts e.g. with `..`
So when we have a file:
```
docs\tutorial\security.md
```
and this references the file:
```
../api/browser-window.md
```
through the markdown syntax:
```
[`BrowserWindow`](../api/browser-window.md)
```
then the link was not found and a warning was given.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Resolves warning introduced by https://github.com/doxygen/doxygen/pull/7679
Signed-off-by: Andrey Vostrikov <andrey.vostrikov@cogentembedded.com>
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Add HTML extension to url conditionally in tree view item.
This change fixes issue with double extension in treeview file list items generated from external tag file.
Items that were read from tag file already have extension.
* Add missing HTML file extension in writeTagFile() calls
* Unify addition of HTML file extension in writeTagFile calls.
Signed-off-by: Andrey Vostrikov <andrey.vostrikov@cogentembedded.com>
|
| | | |
| | | |
| | | |
| | | | |
on aliased member.
|
| | | | |
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In case of svg and inline images we have to follow a little bit another strategy.
In markdown we also have to declare all markdown images to inline images (which is also consistent with the handling on github)
|
|/ / / / |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
Fortran function definitions at begin of a line
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When we have an Fortran source that needs preprocessing like:
```
INTEGER FUNCTION &
BI()
END FUNCTION BI
```
the preprocessor will output:
```
00001 INTEGER FUNCTION &
00002
00003 END FUNCTION BI
```
we see that the function name (and argumentlist (`BI()`) are gone, resulting in the error:
```
Error in file .../test.F90 line: 4, state: 4(SubprogBody)
```
The original problem came from the `BIND` attribute (as found by Fossies in the HDF5 package), but the example has been reduced to the above example.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Incorrect determination of fixed form Fortran
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When we have the following small example, we see that the word `subroutine` doesn't start in column 7 but in column 8.
```
subroutine expan()
c2345678 " " lb " " "
end
```
so the code is not converted from fixed form to free form Fortran and in the example (due to the odd number of double quoutes) result in:
```
********************************************************************
Error in file D:/speeltuin/bug_ftn_quote/small.f line: 5, state: 22(String)
********************************************************************
```
The condition regarding the column number was to restrictive.
|
|/ / / / / / |
|
|/ / / / / |
|
| | | | |
| | | | |
| | | | |
| | | | | |
as a bug.
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
very popular)
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add message format-checking
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When having the RTF_SOURCE_CODE and RTF_HYPERLINKS set the links to the code are generated (e.g. in "Definition at line") but the corresponding anchor is missing.
The corresponding anchors are created (in a similar way as it is done for LaTeX).
|