| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| |
| |
| |
| | |
Consistency
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are 2 different situations here:
- @var, here a special change is necessary to check and handle whether or not we are in PHP (declinfo.*, doxygen.cpp)
- @param
- the type recognition for the PHP type has to be extended with the `[]` possibility and subsequently the `[]` part has to be handled separately from the 'datatype' (doctokinizer.l, docparser.*).
- In the output we now can have multiple text strings resulting in a small change in handling of the separator between the data type (*docvisitor.*)
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-fetaure/bug_html_ins_del_tag
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Github does not support the `<u>` tag for underlined text, in HTML there exists the tag `<ins>`. On https://www.w3schools.com/tags/tag_ins.asp is written:
The `<ins>` tag defines a text that has been inserted into a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<ins>` element with the following default values:
```
ins {
text-decoration: underline;
}
```
analogous there exists the tag `<del>` (https://www.w3schools.com/tags/tag_del.asp):
The `<del>` tag defines text that has been deleted from a document.
Browsers will normally strike a line through deleted text and underline inserted text.
Most browsers will display the `<del>` element with the following default values:
```
del {
text-decoration: line-through;
}
```
Definitions analogue to the underline and strike through tag the implementation for the other formats has been chosen.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As per comment in `docvisitor.h`:
```
class DocCopy; // TODO: no longer generated => remove
```
|
| | |
| | |
| | |
| | |
| | | |
- initializing fd (analogous to htmldocvisitor)
- always good to close file pointers
|
|/ /
| |
| |
| |
| |
| | |
Markdown files
Don't use the file name extension of the including file but of the included file. In case of no included filename or no extension, fall back of the file extension of the including file.
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_lineno_split_examples
|
|/ /
| |
| |
| |
| |
| | |
With the commands like `\skip`, `\skipline` it is possible to show parts of a file for further explanation / tutorials. They can be started with `\include` or `\dontinclude` but in case `\include` specifies that the line numbers have to be shown they are only shown in the full example and not in the split up example
- show line numbers in split up example in case `lineno` is required
- add `lineno` option to `\dontinclude` so here also line numbers can be shown.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
In the PDF version of the doxygen manual we see that for the `\image` command the chapter title the text runs into the margin (due to an unbreakable part).
With this fix the problem is solved.
(see also: https://tex.stackexchange.com/questions/474055/section-title-running-into-margin and , for the ifstar part, https://tex.stackexchange.com/questions/376375/using-ifstar-to-define-a-star-variant)
|
|/ |
|
|\ |
|
| |\
| | |
| | |
| | | |
https://github.com/cheoljoo/doxygen into cheoljoo-run_java_once_3rd_trial
|
| |\ \
| | |/
| | |
| | | |
https://github.com/cheoljoo/doxygen into cheoljoo-run_java_once_3rd_trial
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | | |
not final
|
|/ / /
| | |
| | |
| | | |
In LaTeX the `<hr>` was implemented as a"new paragraph", now as a horizontal line.
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Changes:
- Use of `@emoji name` instead of `:name:`
- Support only GitHub emojis (i.e. without spaces or special characters in the name)
- Provided script to download images for LaTeX support.
- XML output now has <emoji> tag with name an unicode sequence.
|
|\ \
| | |
| | | |
Consistency in headings and layout for template parameters (tparam)
|
| | |
| | |
| | |
| | |
| | | |
- at some places the translation of the "Template Parameters" was not yet done
- layout of the template parameters table in HTML had no default. Should be analogous to the table for normal parameters
|
|\ \ \
| | | |
| | | | |
Remove debug statements
|
| |/ /
| | |
| | |
| | | |
Removing some debug statements
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_inline_image
|
| | | |
| | | |
| | | |
| | | | |
Create the possibility of inline images with the `\image` command by means of the option `inline`.
|
|\ \ \ \
| |_|/ /
|/| | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_6517
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added issue support for the different output types.
- Sources of the emoji
- based on the Unicode definition v11.0:
- https://unicode.org/emoji/charts/full-emoji-list.html
- http://www.unicode.org/emoji/charts/full-emoji-modifiers.html
- github definition list:
- https://api.github.com/emojis
- Input of emoji: :<test>: with the restriction that direct after the opening colon and direct before the closing colon no space is allowed
- doctokinizer.l, adding detection of emoji and new command `\:`
- doktokinizer.h, adding "word" type TK_EMOJI
- docparser.* handling of new "word" type TK_EMOJI (analogous to HTML Entities), handling of new command `\:`
- cmdmapper,cpp, cmdmapper.h, adding new command `\:`
- htmlentity.cpp, adding new definition required for new command `\:`
- Emoji
- emoji.cpp, emoji.h, class for handling emoji analogous to HTML Entities, including small directions on how to update the code when a new emoji is defined. Not everything is converted to lowercase for comparison and accents are removed.
- doxygen.cpp possibility to create list of supported emoji
- handling emoji for output types (analogous to HTML Entities), see documentation for different output types
- docparser.h, *docvisitor.*
- rtfdocvisitor.* converting output to UTF-16 (based on http://scruss.com/blog/2017/03/12/in-the-unlikely-event-you-need-to-represent-emoji-in-rtf-using-perl/)
- latexdocvisitor.*, handling arguments for emoji in output (see also latexgen.cpp for meaning of the arguments of doxygenemoji).
- latexgen.cpp, adding new latex command for doxygen (doxygenemoji) and prevent too many open file (code before documentclass)
- config.xml, definition of `LATEX_EMOJI_DIRECTORY` with path to images required for LaTeX output
- Documentation:
- emojisup.doc, user description
- commands.doc, description of new command `\:`
- index.doc, reference to emoji chapter
- xmlcmds.doc, adjust reference to next chapter as a new chapter is added
- Doxyfile*, adding emoji chapter
Build system
- CMakeLists.txt adding new files
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Issue_6456 Using # in links causes errors in PDF generation
|
| |/ /
| | |
| | |
| | |
| | | |
- The # sign in an URL needs to be escaped as longtabu reads the table body as the argument to a command, so the self-escaping mechanism of \href cannot work (from https://tex.stackexchange.com/questions/447461/having-a-hash-sign-in-href-in-a-longtabu-cell)
- a regression regarding the change from `\tt` to `\texttt` (needed `{ ... }` as `\href` has 2 arguments )
|
| |/
|/|
| |
| | |
Note: especially latexdocvisitor (dead code that should not be dead code).
|
|\ \
| |/
|/|
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_667993
|
| |
| |
| |
| | |
Added underline possibility and strike through possibility for the different output formats insofar it is possible (other similar possibilities are not always possible for all output formats either).
|
|\ \
| |/
|/| |
Bug 796355 - LaTeX: Class scrbook Error: undefined old font command `\tt'
|
| |
| |
| |
| |
| |
| | |
- Replaced \tt by \texttt
- Replaced the left over \bf by \textbf
and taking care that { } still match.
|
|\ \
| | |
| | | |
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).
|
|/
|
|
|
|
|
|
|
|
|
|
| |
- 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)
|
|
|
|
|
| |
Removing the automatic line breaking after 108 characters (also didn't work properly with e.g. executive paper size).
Due to new implementation some character encodings had to be changed as well as well as handling of the single quote in formulas.
|
|
|
|
| |
contains a \code block
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_783134
|
| |
| |
| |
| |
| |
| |
| | |
contains a \code block
General problem regarding having a code / verbatim section inside a table.
Besides handling of the $ some other characters need special handling as well as the \n.
|
|/
|
|
|
| |
When a hyperlink splits across a page boundary it can come to the problem of "\pdfendlink ended up in different nesting level than \pdfstartlink".
To overcome this problem the \hyperlink is packed into a "\mbox" construct (as suffested e.g. in https://tex.stackexchange.com/questions/1522/pdfendlink-ended-up-in-different-nesting-level-than-pdfstartlink)
|
|
|
|
|
| |
The newest version of scrbook (from Ubuntu 16.10) otherwise bails out with
"scrbook Error: undefined old font command `\bf'"
|
|
|
|
| |
in PDF output Data Fields
|
|
|
|
|
|
| |
When looking at the index of the doxygen (pdf) manual we see that __init__ is on a bit strnge place (between "\" items) and that the item "\@" is missing.
Made handling of the index consistent by using latex... routines and adjusting the label routine in respect to the @.
|
|
|
|
|
|
|
|
|
| |
This patch makes the handling of the \snippet and other commands consistent between the different languages (no line numbers anymore with python) and also introduces analogous to \includelineno the command \snippetlineno.
Some non relevant changes:
- *code.l Calculation of the end line was incorrect, in case of a snippet the end line was the number of lines of the snippet and not reltive to the start line.
- *code.l made consistent over the different laguages, enabling exBlock and inlineFragment
- testing/indexpage.xml in test 14 the \snippet command was used with python and giving line numbers, linenumbers are now gone (consistency)
|