| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |/ / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The backslash (\) is in Fortran not an escape character but was handled as such, this has been corrected.
Handling of the different Fortran string types ('...' and "...") made more consistent.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Bug 784322 - .tex file is wrong when generating a function whose name includes an underline
|
| | | |_|/ / / / /
| | |/| | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
includes an underline
Correctly write the text to the text file (i.e. escape some characters)
|
| |\ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Documentation correction CLANG option usage
|
| | |/ / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Corrected reference to use of CLANG option in Doxyfile.
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_tooltip_apostrophe
|
| | |/ / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
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'
|
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Cannot properly jump from brief to detailed function description in python
|
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In case a plain python function (i.e. not in a class or similar) the reference in the brief description to the detailed description points to nowhere as the anchor at the detailed description has file_ in front of it.
The file_ is required for namespaces as mentioned in the code:
// member is in a namespace, but is written as part of the file documentation
// as well, so we need to make sure its label is unique.
tests, on a python project, gave that this doesn't happen and that in case of just files a wrong member reference is given in.
Based on: Generating Python Documentation with doxygen produces broken links to functions (https://stackoverflow.com/questions/50217315/generating-python-documentation-with-doxygen-produces-broken-links-to-functions#50217315)
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Resolve inconsistency in formula repositories.
|
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | | |
HTML and RTF have their own directory with formula repository files. These can get out of sync when HTML and RTF versions are not always build together (and both are required again).
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Bug 727103 - Misparsed comments leading to missing call graph
|
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Handling comment block in scanner.l and code.l in an analogous way.
The problem is caused by a non terminated comment bock in a comment block.
It is strongly advised not to use comment blocks inside other comment blocks and otherwise fix the message.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Bug 796426 - Invalid 3-byte UTF8 found in input of graph
|
| | | |_|_|_|_|/
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
- Corrected counting of utf-8 characters
- Corrected truncation of text for e.g. tooltips
(Note dot 2.38.0 silently ignored the error, 2.40.1 shows the error.)
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Update Dutch translation in respect to new VHDL entries.
|
| | | |_|/ / / /
| | |/| | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Typos found by running "codespell"
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | |/ / / / / / |
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Problem with \cond in normal comment of test 015
|
| | | |/ / / /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In the \cond is also recognized in non-doxygen comment.
- As a work around the \ has been removed
- in case of e.g. pdf the enabled function is not shown as it does not have a doxygen comment
- test file output update due to change in input code.
- pre.l and commentcnv.l. better error message i.e. showing better the used condition
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Problem with code inside a Doxy table in LaTeX
|
| | | |/ / / /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When code is used inside a problem occurs with \discretionary
- Inside a table \discretionary is disabled when code is used.
- \newline should not be appended to a code line (is already implicitly done by the command).
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Problems and some enhancements for LaTeX tables
|
| | |/ / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- Possibility to honor also the cell alignment when using Markdown tables for other formats (markdown.cpp, latexdocvisitor.cpp, lines: 1146, 1157, 1173)
latexdocvisitor.cpp:
- Possibility to nest tables to a further level when using LaTeX. It was only possible till level 2 (i.e. a longtabu followed buy a tabularx table). By placing tabularx in an extra set of brackets this is fixed (lines 938 and 951)
- tablarx environment cannot handle the headers as used for the longtabu table. A header line is in case of tabularx implemented by mimicking the header line.
- longtabu needs multiple times the header line (first and following), tabularx we only need 1 (line 998)
- no longtabu special headers (line 1092)
- tabularx cannot handle rowcolor, coloring done only with columncolor(line 1024, 1134, 1188)
- no necessity for longtabu to define column with for spanned columns / rows(line 1048, 1134, 1171)
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Improvement LaTeX output (regression)
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Regression on pull request #698.
We shouldn't switch to pdflatex for formula generation (follow up procedure: dvips and gs / splitting into images does not work).
In the travis tests this was shown as well but not flagged as an error.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Bug 363762 - Tooltips are not shown in dot-generated graphs
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Some graphs were still missing a tooltip in the root node (most notably the caller graphs), so were still displaying something like Node0.
|
| | |/ / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The basic problem mentioned in this issue was already solved in Mai 2009 (version 1.5.8 or earlier), in case a brief description is present this is displayed otherwise the node number is specified)
A remaining thing was that the tooltip with the root nodes (gray nodes) was always something like Node0 irrespective of the brief description. This has been solved here.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Bug 792122 - XHTML pages are broken several ways (Regression #674)
|
| | | |_|_|/ / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The markdown processing of [TOC] was not performed anymore, at the moment of processing there was no g_current.
Adding @tableofcontents to the stream (like with images) solves this problem.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Bug 782082 - Czech/Slovak language documentation with tables from LaTeX to PDF is not possible
|
| | | |_|/ / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
PDF is not possible
Added commands as indicated to overrule \cline and \cmidrule due to problems with `-`
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Small problems when displaying python code
|
| | | |_|_|_|_|/
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
- with was not colored (in pyscanner the KEYWORD item was not used, so removed as dead code)
- incorrect handling of a 'triquote' at end of string
- incorrect handling of a stringprefix followed by the end of a string
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Bug 792918 - incorrect parsing of markdown table
|
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Problem due to the fact that for the display of the header line the size of the separator line was used. The headerStart and headerEnd have to be set before the next call to 'findTableColumns'
Related to:
- pull request 537 Add support for more CSS and column/row spanning in markdown tables
- pull request 542 Reverting pull request #537 until it will be fixed
- commit on 16/09/2017: New table features mentioned in the documentation were not enabled.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Wrong spelling of word doxygen
|
| | |/ / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Corrected spelling Doxgyen -> doxygen and added space for better readability
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Add formula (images) to RTF output
|
| | | |_|_|/ / /
| | |/| | | | |
| | | | | | | |
| | | | | | | | |
The RTF output was lacking the possibility to have formulas in it (were written as text). This patch generates the images analogous to the HTML, non MATHJAX, version and includes them in the output.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Syntax highlighting / code coloring in RTF
|
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | | |
Although stated in the Doxyfile that for RTF source code syntax highlighting should be present this was not the case.
|