summaryrefslogtreecommitdiffstats
path: root/src/latexdocvisitor.cpp
Commit message (Collapse)AuthorAgeFilesLines
* issue #8193: Better warning in case of error in dot / msc / dia imageDimitri van Heesch2021-05-031-13/+21
|
* Merge branch 'vertical_alignment_table' of ↵Dimitri van Heesch2021-05-021-1/+16
|\ | | | | | | https://github.com/DuyDang007/doxygen into DuyDang007-vertical_alignment_table
| * Add check for middle vertical alignmentDuy Dang2021-02-011-0/+2
| |
| * Support vertical alignment in multirow tableDuy Dang2021-02-011-1/+14
| |
* | Merge branch 'master' into feature/bug_code_langDimitri van Heesch2021-05-021-133/+166
|\ \
| * \ Merge branch 'feature/bug_startuml' of ↵Dimitri van Heesch2021-05-011-1/+1
| |\ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_startuml
| | * | Extending startuml with extra figure typesalbert-github2021-04-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Not all diagrams can be created with the PlantUML `@startuml` command but need another PlantUML `@start...` command. This wil look like `@start<engine>` where currently supported are the following `<engine>`'s: `uml`, `bpm`, `wire`, `dot`, `ditaa`, `salt`, `math`, `latex`, `gantt`, `mindmap`, `wbs`, `yaml`, `creole`, `json` and `flow`. By default the `<engine>` is `uml`. The `<engine>` can be specified as an option. Explicitly the option variant has been chosen so we won't get an explosion of extra commands.
| * | | issue #8522 Javadoc: type attribute of ordered lists not preserved (in xml)albert-github2021-04-291-0/+46
| | | | | | | | | | | | | | | | | | | | The problem was a bit deeper, it was also valid for other output formats. Implemented the `type` and `start` attribute for all relevant output types.
| * | | Refactoring: remove implicit conversion from QCString to const char *Dimitri van Heesch2021-04-221-11/+11
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit changes the following in relation to string use - The implicit convert from 'QCString' to 'const char *' is removed - Strings parameters use 'const QCString &' as much as possible in favor over 'const char *' - 'if (s)' where s is a QCString has been replaced by 'if(!s.isEmpty())' - data() now always returns a valid C-string and not a 0-pointer. - when passing a string 's' to printf and related functions 'qPrint(s)' is used instead of 's.data()' - for empty string arguments 'QCString()' is used instead of '0' - The copy() operation has been removed - Where possible 'qstrcmp(a,b)==0' has been replaces by 'a==b' and 'qstrcmp(a,b)<0' has been replaced by 'a<b' - Parameters of string type that were default initialized with '= 0' are no initialized with '= QCString()'
| * | Refactoring: Add TextStream buffer to improve output writing performanceDimitri van Heesch2021-03-281-5/+5
| | | | | | | | | | | | | | | - direct use of std::stringstream and std::ostream gave a 30% drop in performance.
| * | Refactoring: replace QMIN/QMAX by std::min/std::maxDimitri van Heesch2021-03-261-1/+4
| | |
| * | Refactoring: replace QFile/FTextStream with fstream/stringstreamDimitri van Heesch2021-03-181-42/+43
| | |
| * | Refactoring: Replaced QFileInfo with FileInfoDimitri van Heesch2021-03-181-7/+7
| |/ | | | | | | | | - FileInfo is based on ghc::filesystem, a std::filesystem compatible implementation that does not require C++17.
| * Fix size_t related compiler errors & warnings for win64Dimitri van Heesch2021-01-221-2/+2
| |
| * Refactoring: modernize PlantumlManagerDimitri van Heesch2021-01-221-2/+2
| |
| * Refactoring: modernize LatexDocVisitor::m_tableStateStackDimitri van Heesch2021-01-221-25/+18
| |
| * Refactoring: move Doc*Visitor::push/popEnabledDimitri van Heesch2021-01-221-19/+6
| | | | | | | | New class & name: DocVisitor::push/popHidden
| * Refactoring: modernize HtmlAttribListDimitri van Heesch2021-01-221-7/+18
| |
| * Refactoring: modernize docparser and clientsDimitri van Heesch2021-01-221-17/+9
| |
* | Use language name to get code coloringalbert-github2021-01-171-1/+1
|/ | | | | | | | | | | In a `\code` or `~~~` or ` ``` ` environment we can define the language of a code block by specifying an extension. In markdown we see quite often the language name as code block name (especially for `python`) One can specify it by means of an `EXTENSION_MAPPING` but this is quite unnatural as it it not an extension. - see to it that the extension (and thus `EXTENSION_MAPPING`) still has precedence - in case not a known extension, try the language names. Note: with docbook the explicit name usage was missing.
* Layout in doxywizard documentationalbert-github2020-12-291-0/+21
| | | | | When looking at page 100 of the doxygen 1.9.0 manual (i.e. chapter Doxywizard usage, bold part "Configure doxygen using the Wizard and/or Expert tab..Configure doxygen using the Wizard and/or Expert tab...") we see that the word "Wizard tab" in comparison to "Expert tab" are a bit on a strange place. In the HTML documentation this looks OK The problem is caused by the fact that we have her nested description (`<dl>` lists), a new paragraph should be started / the line should be properly filled and this can be done by means of the `\hfill`.
* Fix for broken LaTeX output.Dimitri van Heesch2020-09-271-6/+6
| | | | | | Fixes error: "\begin{DoxyCodeInclude} on input line 93 ended by \end{DoxyCode}" while generating the LaTeX version of the manual
* Refactoring: prepare output generators for multi-threaded useDimitri van Heesch2020-09-271-93/+83
|
* Regression: further fixes to make the documentation build againDimitri van Heesch2020-06-101-82/+83
|
* Restructure citation handlingDimitri van Heesch2020-02-161-1/+2
|
* Adding commands `\rtfinclude`, `\docbookinclude`, `\maninclude` and ↵albert-github2020-01-091-0/+4
| | | | | | `\xmlinclude` Adding for consistency with `\*only`, `\htmlincclude` and `\latexinclude` the commands: `\rtfinclude`, `\docbookinclude`, `\maninclude` and `\xmlinclude`
* Merge pull request #7223 from albert-github/feature/bug_formula_quoteDimitri van Heesch2019-12-261-1/+1
|\ | | | | Error in LaTeX with single quote in formula / math mode.
| * Error in LaTeX with single quote in formula / math mode.albert-github2019-08-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a text like: ``` \f$ text t' text \f$ ``` and conversion this to a pdf (latex directory) we get the error: ``` ! Undefined control sequence. l.3 $ text t\text {'} text $ ? ```
* | Merge branch 'feature/bug_html_s' of ↵Dimitri van Heesch2019-12-261-0/+1
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_html_s
| * | Adding HTML s tag, XML corrections for other tagsalbert-github2019-08-161-0/+1
| |/ | | | | | | | | | | Adding the HTML `<s>` tag (https://www.w3schools.com/tags/tag_s.asp). Adding 's' and correcting 'inc' to 'ins' in compound.xsd
* | Merge pull request #7237 from albert-github/feature/bug_table_hrDimitri van Heesch2019-12-171-1/+4
|\ \ | | | | | | Problem with `<hr>` in LaTeX multicolumn cell
| * | Problem with `<hr>` in LaTeX multicolumn cellalbert-github2019-08-291-1/+4
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | Split language parser into "outline parser" and "code parser"Dimitri van Heesch2019-12-031-12/+12
|/
* Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-1/+1
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * Correction warning messagealbert-github2019-06-011-1/+1
| | | | | | | | Consistency
* | Merge branch 'feature/issue_6831' of ↵Dimitri van Heesch2019-08-041-2/+4
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_6831
| * | issue #6831 Failure to recognize class array with PHP in @varalbert-github2019-02-151-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | 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.*)
* | | Merge branch 'fetaure/bug_html_ins_del_tag' of ↵Dimitri van Heesch2019-08-031-0/+2
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-fetaure/bug_html_ins_del_tag
| * | | Adding HTML tags ins and delalbert-github2019-04-041-0/+2
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Remove not used classalbert-github2019-07-071-8/+0
| | | | | | | | | | | | | | | | | | | | | As per comment in `docvisitor.h`: ``` class DocCopy; // TODO: no longer generated => remove ```
* | | High consequence coverity mesagesalbert-github2019-07-021-1/+1
| | | | | | | | | | | | | | | - initializing fd (analogous to htmldocvisitor) - always good to close file pointers
* | | issue #7033 Syntax highlighting doesn't work when calling \dontinclude from ↵albert-github2019-06-061-2/+4
|/ / | | | | | | | | | | 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.
* | Merge branch 'feature/bug_lineno_split_examples' of ↵Dimitri van Heesch2019-03-091-4/+19
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_lineno_split_examples
| * | Show line numbers in "split" examplesalbert-github2019-03-031-1/+16
|/ / | | | | | | | | | | 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.
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2019-02-281-1/+1
|\ \
| * | Section title runs into marginalbert-github2019-02-101-1/+1
| |/ | | | | | | | | | | 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)
* | Refactored Definition and derived classes such that they are abstract interfacesDimitri van Heesch2019-02-281-4/+6
|/
* Merge branch 'cheoljoo-run_java_once_3rd_trial'Dimitri van Heesch2019-01-081-2/+2
|\
| * Merge branch 'run_java_once_3rd_trial' of ↵Dimitri van Heesch2019-01-081-2/+2
| |\ | | | | | | | | | https://github.com/cheoljoo/doxygen into cheoljoo-run_java_once_3rd_trial
| * \ Merge branch 'run_java_once_3rd_trial' of ↵Dimitri van Heesch2018-12-271-1/+1
| |\ \ | | |/ | | | | | | https://github.com/cheoljoo/doxygen into cheoljoo-run_java_once_3rd_trial
generated by cgit v0.12 at 2024-07-01 01:52:01 (GMT)