| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
In pre part always use `\string~` for `~` otherwise it will be translated to a space.
|
|\
| |
| | |
Warning with xrefitem from documentation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The example code with the `xrefitem` in the documentation gives a warning:
```
my_errors:1: warning: multiple use of page label 'my_errors', (other occurrence: .../aa.h, line: 4)
```
it is possible (and explicitly stated) to have an `\page` with the same name giving some extra information.
The warning regarding the multiple page is removed in case of a xrefitem page.
|
|/
|
|
|
|
| |
Take the part after the last '.', method 'extension` gives the extension after the first '.' of a filename.
This is a regression on pull request #7121 (issue #7120)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having a backslash in a href like:
```
<a href="C:\boost">`C:\boost`</a>
```
we get in LaTeX the error:
```
(aa_8h.tex
! Undefined control sequence.
<argument> C:\boost
l.6 \href{C:\boost}
{\texttt{ {\ttfamily C\+:\textbackslash{}boost}}}
```
this can be overcome by escaping the backslash.
Note this is just an example, for an URI actually forward slashes should be used. It is just about the backslash not generating an error.
|
| |
|
|
|
|
| |
Creating warning when adding documentation to an already existing page.
|
|\
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
- moved unescapeCharsInString to util.cpp
- restructured flow keyword counting
- make flow keyword counting work for python and fortran code 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/bug_gitversion
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The original version has as features:
- getting the git version number for usage in doxygen
- making the doxygen version number inclusion dependent on the VERSION file
The disadvantage of the chosen methodology was that an extra correction step was necessary, by defining getter methods to retrieve the values this correction can be hidden.
The information is coming from different sources:
- the VERSION file
- the git "repository and build system (when present)
Furthermore there are a couple of places where the version information is used (a.o. doxygen and doxywizard executable, though the doxygenwizard was only done "half hearted")
The handling of the VERSION file has been made in such a way that it is comparable with the generation of the git version changes.
For a better abstraction the version handling is all done in a separate directory.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6950
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
references in first array element
Don't stop at a hexadecimal number, but output the hexadecimal number (plus the part that has not been printed yet) and continue with the next input part.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
with no extension
Better handling of the determination of what is an extension.
- don't see a file references like: `./LICENSE` as extension
- use the qt way of extension determination and in case of no extension use the no extension placeholder for it.
|
| | | |
| | | |
| | | |
| | | | |
For an URL also the percentage (`%`)sign has to be escaped
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
issue #7033 Syntax highlighting doesn't work when calling \dontinclude from Markdown files
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
Markdown files
Don't use the file name extension of the including file but of the included file. In case of no included filename or no extension, fall back of the file extension of the including file.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_case_sense
|
| | | | |
| | | | |
| | | | |
| | | | | |
In case special characters in a filename need escaping into something like: `_0` the `0` should not be followed by an uppercase character as this would be in contradiction wit the setting `CASE_SENSE_NAMES=NO`.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When we have a construct like:
```
template <typename Element, size_t N>
class StlContainerView<Element[N]> {
public:
typedef internal::NativeArray<RawElement> type;
};
```
this will lead to files with `[` and `]` in it, as such not nice, but it is used in ids inside the code as well like:
```
id="aclass_stl_container_view_3_01_element[_n]_4_html_a1bf60158ff15896f2b53af11c09524fb"
```
running
```
xmllint --path ..../testing/dtd --noout --nonet --postvalid html_org/*html
```
this leads to the message:
```
Syntax of value for attribute id of div is not valid
Document html_org/test_8h_source.html does not validate
```
escaping the `[` and `]` as done with other special characters solves this problem
|
|/ / /
| | |
| | |
| | |
| | | |
Cygwin should by default also have `CASE_SENS_NAMES=NO` like is the case for the underlying Windows.
In case of Cygwin the define `_WIN32` is not set so we also have to test for `__CYGWIN__`
|
|\ \ \
| | | |
| | | | |
Markdown file as internet link
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
See a link in case of a md file only as local link if it doesn't start with a supported protocol.
Example found was:
```
[Ansibullbot](https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md)
```
|
| | | |
|
| |/
|/| |
|
| | |
|
|\ \
| | |
| | | |
issue #6917 Crash in php with UTF-8 character
|
| |/
| |
| |
| |
| |
| | |
Problem is that a value is fed to isspace that is not in the correct range and has to be converted to this range.
compare also Assertion failure generation documentation (fdefe70a955c8140f080974319bbf97364d3e610 of March 30 2016).
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
In case in code 2 consecutive minus signs are present they are shown as endash.
using the same code as in the non code part solves the issue.
Issue can e.g. be seen in cpp source code (with e.g. i--) and in the doxygen documentation in the paragraph "Comment blocks in VHDL"
This is a regression in 1.8.15
|
|/ |
|
|
|
|
| |
After small discussion conclusion was better to remove the obsolete `doxygen=`
|
|
|
|
| |
operators in 1.8.15
|
| |
|
|
|
|
| |
An empty string was defined in a `<a href="">` resulting in a null pointer access.
|
|
|
|
| |
Convert name / url based on HTML / XML conventions and don't do double conversions (XML).
|
| |
|
| |
|