| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
|
|
| |
- Removing the `txt` and `doc` extension from the default list of `FILE_PATTERNS
- Updating documentation
- Incorrect parsing for the doxywizard of some \ref items (i.e. when the description contains a space, made compatible again with that happens in configgen.py).
|
|
|
|
|
|
|
|
|
| |
At the top of the chapter describing the commands there is a list with described commands, here the commands:
```
\noop
\static
```
were missing.
|
| |
|
| |
|
|
|
|
| |
Bringing the doxywizard documentation up to date with the current version.
|
|
|
|
| |
The syntax of the Windows Powershell differs from other shells, so an example is added to the faq section
|
|
|
|
| |
Small correction in documentation.
|
|
|
|
|
| |
In case of a sequence of hyphens the documentation was incomplete.
(found during implementation of "Miscounting in markdown in case of a horizontal ruler", #8115)
|
|\
| |
| | |
Warning about duplicate figure numbers in LaTeX
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the log file of the generated doxygen manual we see warnings like:
```
pdfTeX warning (ext4): destination with the same identifier (name{figure.22.1})
has been already used, duplicate ignored
\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
```
(this pull request was also triggered by: https://stackoverflow.com/questions/64328597/pdftex-warning-saying-about-duplicate-figures)
The solution is found by means of: https://tex.stackexchange.com/questions/566677/multiple-use-of-figure-number-ext4-warning/ in short:
> The hyperref package patches \caption so \H@refstepcounter is used instead of \refstepcounter.
The definition isn't necessary in `manual.sty` as the `doxygen_manual.tex` includes `doxygen.sty`
|
|/
|
|
|
|
|
|
| |
When we look at images in documents we see for a number of images a big amount of white space around the image.
This is e.g. the case in the doxygen manual at page 99 of the 1.8.20 version.
- using `\raggedbottom` sees to it that the space inside the page is removed (there might be some white space when the next image doesn't fit anymore. (See https://tex.stackexchange.com/questions/566779/placing-figures-on-a-fixed-place-without-lot-of-space-around-it)
- use `\centering` instead of `\begin{center}` as the center environment adds some extra white space (see a comment with the question, on a different subject though: https://stackoverflow.com/questions/64328597/pdftex-warning-saying-about-duplicate-figures#comment113772445_64328597)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the doxygen pdf manual we see that on the first page of each chapter the footer is missing, the same occurs in the "normal" documentation generated by doxygen.
References:
- https://tex.stackexchange.com/questions/566034/footer-ruler-on-first-page-in-fancyhdr-with-book
- https://tex.stackexchange.com/questions/566056/footer-ruler-on-first-page-in-fancyhdr-with-book-but-not-in-part-part/
Code changes ("normal" documentation):
- latexgen.cpp changes required for the "normal" documentation
Code changes (doxygen manual)
- doxygen_manual.sty, remove word "Part" for the Appendices.
- manual.sty changes like for "normal" documentation plus patching part in case of the `\part` (here we don't want the footer or header)
|
|
|
|
|
|
|
|
|
| |
Looks like the documentation update after
> Commit: 10787eed95266bb1a13c892fe4cf5a695dac1559 [10787ee]
> Date: Friday, May 15, 2020 11:28:16 AM
> Refactoring
has not been done.
|
| |
|
|
|
|
|
|
| |
At some places Python version 2.6 was still mentioned, made uniform to 2.7 everywhere.
(Is already a bit dubious as of January 1st, 2020 Python 2.7 will reached the end of its life., but still a lot will have Python 2.7 by default).
|
| |
|
|
|
|
| |
Small spelling correction as found by spellcheck through Fossies
|
|
|
|
|
|
|
|
|
| |
- make `GLOB` for language files consistent with `GLOB` usage in e.g. `src`
- make building of `language.doc ` depending on the language files as well
- don't copy translator and other input files and handle this also in translator.py
- update documentation
(Found after Swedish language was updated and tried to build documentation on a non new directory)
|
|\
| |
| | |
Using Python docstrings
|
| |
| |
| |
| |
| | |
- making documentation a bit clearer
- add configuration setting to have docstrings not as preformatted text but as normal documentation (default remains preformatted).
|
| |
| |
| |
| | |
There were a few logical errors in the changelog , corrected.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Changed \_linebr to \ilinebr
- \ilinebr is now also passed to doctokenizer
- Also fixes issue #7493 regarding \snippet inside markdown tables and
dealing with wrong line on issues detected by docparser after a
markdown table.
- Added function tracing to markdown (enabled with -d markdown in a
debug build)
|
| |
| |
| |
| |
| |
| |
| | |
The 5th Edition / December 2017 of https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-334.pdf
has the XML commands in Appendix D
Fix issue Typo in xmlcmds.doc XML tags moved to Appendix D of Ecma-334 #7855
https://github.com/doxygen/doxygen/issues/7855
|
| |
| |
| |
| | |
Give a meaningful fatal error when the pdf does not exists (when it exists automatically also the html directory with content exists).
Give a meaningful fatal error when the chm does not exists.
|
| |
| |
| | |
Small documentation consistency.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Link fixed in documentation
|
| | | |
|
| | |
| | |
| | | |
Normal users of github cannot set labels to issues.
|
|/ / |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
- there were still references to Tcl
- 2 entries were accidentally removed from the table with fiel extensions.
|
| |
| |
| |
| | |
very popular)
|
| | |
|
|/
|
|
| |
Documentation has to be updated as well
|
|
|
|
| |
Corrected spelling
|
|\
| |
| | |
CMake and examples
|
| |
| |
| |
| |
| | |
Making more use of arrays in CMake to create the documentation of examples.
Renaming the template/templ example to have a more consistent naming with the other examples.
|
|\ \
| |/
|/| |
Possibility to use gswin64c on Windows
|
| |
| |
| |
| |
| | |
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).
|
|/
|
|
|
|
| |
`\xmlinclude`
Adding for consistency with `\*only`, `\htmlincclude` and `\latexinclude` the commands: `\rtfinclude`, `\docbookinclude`, `\maninclude` and `\xmlinclude`
|
|
|
|
| |
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.
|
|
|
|
| |
Small spelling correction in change log
|
| |
|
| |
|