| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Possibility to use gswin64c on Windows
|
| |
| |
| |
| | |
include file was missing
|
| |
| |
| |
| |
| | |
On windows the 32 bit executable is called gswin32c, but for the 64-bit systems also a gswin64c exists.
The path is checked for the existing of these executables (with a preference for the 32 bit version).
|
|\ \
| | |
| | | |
issue #7484 Error: /undefined in getenv
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The command `ps2epsi` also uses the `gs` command and this gives some problems with the gs9.50 version.
An alternative is the `eps2eps` command that doesn't have these problems with the gs9.50 version.
See also:
- #7290
- https://bugs.ghostscript.com/show_bug.cgi?id=702024
|
|\ \ \
| | | |
| | | | |
Updated Swedish translation to match the latest version
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Consistency `\*only` and `\end*only` commands
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Not all possibilities in respect of `\*only` and `\end*only` commands were present which could lead to messages like:
```
.../aa.h:4: warning: reached end of comment while inside a \rtfonly block; check for missing \endrtfonly tag!
../.aa.h:4: warning: rtfonly section ended without end marker
.../aa.h:4: warning: rtfonly section ended without end marker
```
in case of a problem like:
```
/** \file
* \rtfonly
* RTF /* Nested */
* \endrtfonly
*/
```
|
|\ \ \
| | | |
| | | | |
Remove unused rules
|
| |/ /
| | |
| | |
| | | |
Remove some unused rules.
|
|\ \ \
| | | |
| | | | |
Adding commands `\rtfinclude`, `\docbookinclude`, `\maninclude` and `\xmlinclude`
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
`\xmlinclude`
Adding for consistency with `\*only`, `\htmlincclude` and `\latexinclude` the commands: `\rtfinclude`, `\docbookinclude`, `\maninclude` and `\xmlinclude`
|
|\ \ \
| | | |
| | | | |
Bug 769411 - Confuses functions with the same name, but different namespace
|
|/ / /
| | |
| | |
| | | |
Check that the members are in the same namespace before combining documentation
|
|/ /
| |
| |
| | |
silently ignored
|
| | |
|
|\ \
| |/
|/| |
Correction behavior of make clean in respect to version files
|
| |
| |
| |
| |
| | |
I case we ran `make clean` it was not possible anymore to generate doxygen as the generated file `generated_src/gitversion.cpp` was not present any more and it was not re-generated.
The generation of the `generated_src/gitversion.cpp` depends on teh `generated_src/git_state` file and this file was still present. This has been corrected.
|
|\ \
| |/
|/| |
Showing information from all \*only commands in XML output
|
|/
|
|
| |
This fix reverts the changes from #381 (i.e issue #4214 "htmlonly content appears in generated XML output (Origin: bugzilla 646002)", as XML is seen as an output format that can be further processed and therefore should contain all possible information.
|
|\
| |
| | |
issue #7477 Broken urls in the xml output
|
|/
|
|
|
| |
Made code analogous to HTML code.
Also the doxygen internal tests suffered from this problem.
|
|\
| |
| | |
Small spelling correction in portable.cpp
|
| |
| |
| |
| | |
Small spelling correction in portable.cpp
|
|\ \
| |/
|/| |
Small spelling correction in change log
|
|/
|
|
| |
Small spelling correction in change log
|
| |
|
|\ |
|
| |\
| | |
| | | |
issue #7464 1.8.17: test suite is failing
|
| |/
| |
| |
| |
| |
| |
| |
| | |
On Windows the syntax with the command and arguments in one string worked but on *nix (and Cygwin) it didn't.
- changed calls to Popen to split command (see also: https://docs.python.org/3/library/subprocess.html).
- explicitly specify files to check for xhtml
- changed call to xmllint for xhtml and docbook (due to stdout overflow in some cases, we are not really interested in the, formatted, output of xmllint).
- in the update part a `read` was left, should have been removed.
|
|/ |
|
| |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Adding check on configuration setting EXTENSION_MAPPING
|
| |/
| |
| |
| | |
In #7419 the EXTENSION_MAPPING test was omitted
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |\
|/ /
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_formula
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When having a problem like:
```
/** \file */
/**
* The fie
*
* @form: the new format
* @content: the content of the form
*
* Sets @form content to be @content.
*
* \f$ \alpha \f$ \f[ \beta \f]
*/
void fie(char *form, char *content);
```
we get warnings like:
```
.../aa.h:5: warning: Wrong formula id -1
.../aa.h:6: warning: Found unknown command '\content'
.../aa.h:8: warning: Wrong formula id -1
.../aa.h:8: warning: Found unknown command '\content'
```
The `@form:` is in RST analogue to the doxygen `@param form` but not understood by doxygen.
The result is that it is seen as an formula as doxygen translates the formula commands to `\form`.
For `@content` is handled properly as this is not a doxygen command.
In this patch a more unique name is chosen so these type of conflicts don't appear (that easy). The resulting, better, warnings are now:
```
.../aa.h:5: warning: Found unknown command '\form'
.../aa.h:6: warning: Found unknown command '\content'
.../aa.h:8: warning: Found unknown command '\form'
.../aa.h:8: warning: Found unknown command '\content'
```
|
|\ \ |
|