| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
specified
|
|
|
|
| |
tagfile
|
|
|
|
| |
extracted from tag files.
|
|
|
|
| |
merged if using tagfile
|
| |
|
| |
|
| |
|
|
|
|
| |
message)
|
|\ |
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_size_latex
Conflicts:
src/doctokenizer.h
src/latexgen.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adjusts some problems regarding image sizes in LaTeX output of doxygen (a.o. Bug 738299 - When using msc or PlantUML, the default latex for the created image should include [width=\linewidth]) this has been done is such a way that all the "image" commands (i.e. image, dot, dotfile, msc, mscfile, diafile, startuml) operate in a similar way / have the same possibilities.
- commands.doc
Adjusted documentation to reflect changes.
- cmdmapper.cpp
- cmdmapper.h
Added utility function to map command id back to command name
- doctokenizer.h
- doctokenizer.l
Handle Caption and Size indication. Required also that some other rules had to be tightened a bit (like usage of {} in startuml and usage of "" for captions. This was already described in the documentation in this way).
- docparser.cpp
- docparser.h
Created routine to uniformly handle the Caption and size indications and store them in a general way.
- latexgen.cpp
Replaced graphicx package by adjustbox package (includes graphicx) to support "min width" etc.
- doxygen.sty templates\latex
Added commands to make commands with and without caption behave similar.
- docbookvisitor.cpp
- docbookvisitor.h
- htmldocvisitor.cpp
- latexdocvisitor.cpp
- latexdocvisitor.h
- printdocvisitor.h
- xmldocvisitor.cpp
Created routine to uniformly handle the Caption and size indications in a general way.
- indexpage.xml (testing\022)
- indexpage.xml (testing\031)
- class_receiver.xml (testing\037)
- class_sender.xml (testing\037)
Adjusted example output.
|
|\ \
| | |
| | | |
Add source code possibility for RTF output
|
| | |
| | |
| | |
| | |
| | | |
Analogous to Latex and HTML output the possibility to have source code shown in RTF output is created.
Based on question: http://doxygen.10944.n7.nabble.com/RTF-lack-of-source-code-tc6936.html
|
|\ \ \
| | | |
| | | | |
Convert FORTRAN modules to namespaces
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
This helps fix linking issues and ambiguity related to the difference between classes and modules in FORTRAN 2003+.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Markdown
|
| | | |
| | | |
| | | |
| | | | |
XML comments
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
section (fixed regression)
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
fix docbookgen.cpp to support other than english
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
1. support other than english
2. fix broken example link id
3. fix incomplete TOC : no Classe etc.
4. add brief description for Functions etc.
5. Comply with REPEAT_BRIEF
6. Do not output duplicated contents when detailed descripton is missing.
7. set table colwidth for Param/RetVal
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Bug 722940 - classes with same name in different namespace adding to same group
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
If two classes with the same name, but in different namespaces (so different qualified names) were added to the same group, only one of them would end up in the group.
The problem is caused by qualifiedName of the class not containing the qualified name but the class name when a class is added to the group.
A workaround is to use the name attribute of the class, which does contain the qualified name.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fortran color CALL as keyword
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Color the word CALL as keyword.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a regression on pull request 259.
Fortran code like:
end if
was not colored properly anymore. This has been corrected with this patch.
|
|\ \ \ \
| | | | |
| | | | | |
Bug 687576 - Add support for LATEX_EXTRA_STYLESHEET
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Added the possibility for LATEX_EXTRA_STYLESHEET analogous to HTML_EXTRA_STYLESHEET. Special attention has been paid to the extension as ".sty" is automatically added by the \usepackage
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Extra empty line in source fragments
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
In case of a language that does not uses curly brackets to define blocks (such as Fortran) there was a newline character in the variable c and this was written in the "code fragment" buffer and subsequently written to the output resulting in and extra empty line on top. I languages using curly brackets this is later overwritten by the while loop searching for the open curly bracket.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Support for INLINE_SOURCES in Fortran
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Fortran does not yet support the INLINE_SOURCES, with this patch (part of) this omission is solved.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
albert-github/feature/bug_fortran_source_continuation
Fortran continuation character seen as begin of function call
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
In case in fixed format code a line like:
" x ( " existed and the x was on position 6 the "x (" was seen as the start of a function call.
|
|/ / / /
| | | |
| | | |
| | | | |
The color for the single END in Fortran code was of the color of the flow type entities though for all the flow entities the entity name is mandatory. For the entity statements of some keywords e.g. SUBROUTINE and FUNCTION the entity name is not mandatory with the END statement. The color of the single END statement has been changed from the flow type to the normal keyword type.
|