| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
- add doxygen version to rtf, comment, output
- remove duplicate code (getFullVersion)
- more clear name to get doxygen version (getVersion becomes getrDoxygenVersion). Also to overcomecofusion with the version information for files.
|
| |
|
|
|
|
| |
Although there is not a lot of doxygen internal documentation, it still should not produce warnings.
|
| |
|
|
|
|
|
| |
Avoid code duplication by adding function addHtmlExtensionIfMissing() and
avoid member shadowing by using 'm_' prefix for member variables
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_335614
|
| |
| |
| |
| |
| | |
- See to it that when an extension is already present this extension is used and not a second extension is added
- let the tag file know what the original extension was.
|
|\ \
| | |
| | | |
Create possibility to define LaTeX commands for formulas
|
| |/
| |
| |
| |
| |
| | |
To be able to have building bocks for formulas one can create a `\newcommand` (or when one wants to change a command `\renewcommand`).
Due to the different handling of LaTeX commands in pure LaTeX code (latex output and formulas converted to images) and MathJax it is necessary to transform LaTeX commands to the MathJax equivalent.
This is done in a transparent way by providing the new commands in a file and add this verbatim to the pure LaTeX code and to translate the `\newcommand` and `\renewcomamnd` to MathJax macros.
|
|\ \ |
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_terminate
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In case a `WARN_LOGFILE` is used it in this file no clear whether doxygen finished correctly or exited beforehand in case a fatal error.
Now a 'Exiting...' is also given in the warning log file in case an error is a fatal error.
|
| |/ /
| | |
| | |
| | | |
the content
|
| | | |
|
|/ / |
|
|/
|
|
|
|
|
| |
- handling of the used filename, sometimes the filename was not set resulting in case of a warning with file `<unknown>`, also improving, slightly, the line reference.
- in case of `##` comment blocks the last line was not always show
- in case of multiple comment blocks, properly separate them
- correct handling tab character in source code output (*gen)
|
|\
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having the example:
```
/*! \file
* \brief
* Prerequisite header file
*/
//! \cond
#ifdef HAVE_CONFIG_H
#include "gmxpre-config.h"
#endif
//! \endcond
```
and we run xmllint on it:
```
xmllint --path .../testing/dtd --noout --nonet --postvalid html/*.html
```
we get the messages:
```
html/aa_8h_source.html:75: parser error : Opening and ending tag mismatch: div line 67 and body
</body>
^
html/aa_8h_source.html:76: parser error : Opening and ending tag mismatch: body line 17 and html
</html>
^
html/aa_8h_source.html:77: parser error : Premature end of data in tag html line 2
^
```
It looks like the problematic part in this case is the doxygen type comment at the end of the file.
In the past similar situations were present in LaTeX (related to maximum line length correction), but it was only fixed for LaTeX.
Besides the change for HTML also small changes were necessary for RTF and docbook.
|
| | |
|
|/ |
|
|\
| |
| | |
Adjustment of xhtml1-transitional.dtd
|
| |
| |
| |
| | |
Some more ...
|
| |
| |
| |
| |
| | |
- mapping changed due to missing `doxygen=`
- externalRef part changeddue to missing`doxygen=`
|
|/ |
|
|\
| |
| | |
Double id for tooltips in XHTML possible.
|
| |
| |
| |
| | |
The tooltips (XHTML) should not be displayed per code fragment but for the entire (output) file as otherwise tooltips might be added multiple times resulting in double IDs.
|
|/
|
|
| |
In case of an empty line insert an space so the line will be shown with copy & paste (including the space!).
|
|
|
|
|
|
| |
In case a filename starts with a number the `id` also starts with a number and this is not allowed in XHTML and results in the message:
`Syntax of value for attribute id of div is not valid`
on other places it has been solved by placing an `a` as first character, this is done here as well but also needs to be don in the transformation from reference to tooltip id (htmlgen.cpp)
|
|
|
|
|
|
|
|
|
| |
Message:
`< Element map content does not follow the DTD, expecting ((p | h1 | h2 | h3 | h4 | h5 | h6 | div | ul | ol | dl | menu | dir | pre | hr | blockquote | address | center | noframes | isindex | fieldset
| table | form | noscript | ins | del | script)+ | area+), got (area area div)`
The problem first surfaced with test 11 (empty map tag), but the solution given at that moment (`<div/>)`) did work for test 11, but was not correct for test 27.
Problem can be seen with the default doxygen test 27 (`[027_extends.c]: test the \extends, \implements, \memberof, \private, and \public commands`).
|
|
|
|
|
|
|
|
| |
In case of a class diagram without mapping information the `map` tag is written without content. This is not allowed and results in xhtml (as reported by xmllint) in:
`Element map content does not follow the DTD, expecting ((p | h1 | h2 | h3 | h4 | h5 | h6 | div | ul | ol | dl | menu | dir | pre | hr | blockquote | address | center | noframes | isindex | fieldset | table | form | noscript | ins | del | script)+ | area+), got ()`
By adding a dummy 'paragraph' `<div/>` this can be overcome,
The closing tag for `map` has been placed on a bit a more logical place, showing the open and close tag together.
Problem can be seen with the default doxygen test 11 (`[011_category.m]: test the \interface and \category command`).
|
| |
|
|
|
|
| |
Added a Slice-optimized output mode.
|
|
|
|
|
| |
- corrected some initializations
- corrected some missing, new, cases (reported by travis CI)
|
|
|
|
| |
Note: especially latexdocvisitor (dead code that should not be dead code).
|
| |
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_693515
|
| |
| |
| |
| | |
Made implementation analogous to the implementation for parameters in respect to padding and the use of colon (:).
|
|\ \
| | |
| | | |
Wrong link generated for inherited members when tag files are used.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case a tag file is used and `EXT_LINKS_IN_WINDOW` is set to `YES` a link is generated of the form:
`Public Member Functions inherited from <a class="el" href="target="_blank" https://doc.qt.io/archives/qt-5.10/qobject.html">`
instead of
`Public Member Functions inherited from <a class="el" target="_blank" href="https://doc.qt.io/archives/qt-5.10/qobject.html">`
When `EXT_LINKS_IN_WINDOW` is set to `NO` a correct link is generated but the external documentation comes straight forward in the current window.
(relevant link: https://stackoverflow.com/questions/51323207/doxygen-external-link-to-qt-classes)
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For external tagfiles, there is an issue with the links being provided from the file list. Whenever there is a reference in HtmlGenerator::startIndexItem, the href had never been closed with an end quote and close bracket.
For example, this addition addresses the following issue beginning at href:
<td class="entry"><span style="width:16px;display:inline-block;"> </span><span class="icondoc"></span><a class="elRef" doxygen="/path/to/external/example.tag:../../external/html/" href="../../external/html/file.htmlfile.h</a> [external]</td><td class=" desc"=""></a></td>
Since the file path is true for ref and not f, the proposed changes will provide an external link to the tagfile beside the icon.
Running Doxygen 1.8.14 on HP-UX B.11.31.
|
| | |
|
|/
|
|
|
| |
The tooltip was already 'HTML escaped' except for some '<' and '>' characters but was again 'HTML escaped' resulting in e.g. that a single apostrophe (') was translated to ' and again to &#39; resulting in ' in the tooltip.
Only '<' and '>' are now 'HTML escaped again'
|
|\
| |
| | |
Better HTML output for VHDL Ports
|
| |
| |
| |
| | |
Small alignment improvement of HTML output for VHDL Ports so that the mode will be in a separate column
|
|\ \
| | |
| | | |
Bug 792211 - When generating xhtml, async attribute on script tags need a value
|