| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
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.
|
|\ \ |
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | | |
issue #7210: 1.8.16: Image inclusion is inconsistent
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The consequence of #7084 (Missing warning about ambiguous files) was that in case a file was ambiguous only a message was given.
Now a warning is given plus one of the ambiguous files is used (might be the wrong one).
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_nbsp_code
|
| | |/ /
| | | |
| | | |
| | | |
| | | | |
In case we have the UTF-8 code for nbsp in our source this is (see #6983) replaced with ` `, though in code fragments this is unwanted as here the text appears literally.
the UTF-8 nbsp is temporary replaced by a "doxygen" tag and for fenced code blocks, backtick blocks and special bloc commands (code, verbatim, htmlonly, formulas,...) replaced back with the UTF-8 version, the remaining "doxygen" tags are at the end replaced with ` `
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | | |
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.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
HIDE_FRIEND_COMPOUNDS=yes
|
| | |\ \ \ \
| | | | | | |
| | | | | | | |
issue #7228 Using markdown causes wrong error and warning line numbers - v. 1.8.16
|
| | | | |_|/
| | | |/| |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
1.8.16
Sacrificing some readability of the debug `-d markdown` output for a better approximation of the line numbers by keeping the rows of a markdown table on one line when translating to a HTML table.
|
| | |\ \ \ \ |
|
| | | |\ \ \ \
| | | | | | | |
| | | | | | | | |
Tests 31 for XHTML output
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When running test 31 for XHTML output, we get the error:
```
not ok 1 - [031_image.dox]: test the \image command
-------------------------------------
.../testing/test_output_031/html/index.xhtml:107: parser error : EntityRef: expecting ';'
"image/svg+xml" data="https://img.shields.io/badge/docs-Doxygen-blue.svg?foo&bar
```
For the SVG output the `src` was not properly converted (see also the other formats a few lines lower).
|
| | | | | | | | |
|
| | |\ \ \ \ \ \
| | | |/ / / / /
| | |/| | | | |
| | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_config
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In case of a configuration list item has an equal sign in it ('=') some extra restriction are imposed / made more understandable.
|
| | | | | | | | |
|
| | | |/ / / /
| | |/| | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We get warnings like:
```
warning: reached end of file while yyextra->inside a 'code' block!
warning: Ignoring \brief command yyextra->inside argument documentation
```
this is due to the fact that the scanner has been made reentrant (inside becomes yyextra->inside and this slipped into the warning strings as well)
|
| | |\ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_unsupported_html
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When having a problem like:
```
/** \file
- Just name <name>
- name plus subname <name subname>
- name plus twice subname <name subname subname>
- name plus subname subname="" <name subname subname="">
*/
```
we get correctly the warnings:
```
.../aa.h:3: warning: Unsupported xml/html tag <name> found
.../aa.h:4: warning: Unsupported xml/html tag <name> found
.../aa.h:5: warning: Unsupported xml/html tag <name> found
.../aa.h:6: warning: Unsupported xml/html tag <name> found
```
but the output doesn't look good as there is `=""` added:
```
Just name <name>
name plus subname <name subname="">
name plus twice subname <name subname="" subname="">
name plus subname subname="" <name subname="" subname="">
```
This patch fixes this output.
|
| | | | | | | | |
|
| | |\ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_nospam_email
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
When having a simple nospam email address coded like:
```
/** \file
* Big Unknown <big at none dot com>
*/
```
this results in the warning:
```
aa.c:2: warning: Unsupported xml/html tag <big> found
```
and in the HTML output it looks like:
```
Big Unknown <big at none dot com>
```
instead of:
```
Big Unknown <big at none dot com>
```
(Found in a couple of open source projects).
|
| | |\ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Problem with `<hr>` in LaTeX multicolumn cell
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Small problem with defining `\hrulefilll`, moved code.
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
In case we have a `<hr>` in a table cell then it is displayed as a horizontal line (in LaTeX) unless it is in a multicolumn cell. In the later case it throws an error:
```
! You can't use `\hrule' here except with leaders.
\DoxyHorRuler ... }{0ex plus 0ex minus 0ex}\hrule
```
We have to use use `\hrulefill` in a table but in combination with the table option of xcolor this gives some problems so a new command has to be defined for this.
See also:
- horizontal rule / line inside a multicolumn field (https://tex.stackexchange.com/questions/506211/horizontal-rule-line-inside-a-multicolumn-field)
- interaction between \usepackage[table]{xcolor} and \hrulefill (https://tex.stackexchange.com/questions/506221/interaction-between-usepackagetablexcolor-and-hrulefill)
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
preceding '|' action
|
| | | | | | | | | | |
|
| | |\ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7248
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Ignore automatically generated anchor names when importing a tag file.
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
The search for `/*` or /*!` ended at the last `*/` in a file and thus skipping other intermediate block end and new starts. Also the intermediate code was lost see as comment.
The filter pattern used was incorrect and should have been `<"/*" (~["*"])* "*" ("*" | ~["*","/"] (~["*"])* "*")* "/">` (thanks to https://javacc.org/contrib/C.jj).
Here also the space plus one or more `*` at the end beginning of the line are still incorporated as well as multiple `*` before the colosing `*/` this is also filtered.
|
| | |\ \ \ \ \ \ \ \ \ |
|
| | | |\ \ \ \ \ \ \ \ \
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
Email address seen as code starter
|
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
Some email addresses give problems in the comment converter as they contain e.g. `@code`, so we try to detect Email addresses (analogous to doctokenizer.l) to prevent these false positives.
The given warning would ne like:
```
aa.h:13: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 1)
```
|
| | | |\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
Incorrect NCName in docbook citations
|
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
In a bibtex reference it is possible to have a colon as the id, but in docbook this will result in:
```
docbook/citelist.xml:5: validity error : xml:id : attribute value _citelist_1CITEREF_pre:post is not an NCName
<varlistentry><term><anchor xml:id="_citelist_1CITEREF_pre:post"/>[1]</term>
```
So the id has to be translated. A colon in an id can only happen in case the names is provided from the outside.
|