summaryrefslogtreecommitdiffstats
path: root/src/docparser.h
Commit message (Collapse)AuthorAgeFilesLines
* Formulas with a new environment handled as inline formulasalbert-github2021-05-131-1/+5
| | | | As a regression of #8509 formulas that start a new environment (`\f{`) were considered as inline formulas as teh inline test looked for a `\{` but should look for `\begin{`.
* issue #8193: Better warning in case of error in dot / msc / dia imageDimitri van Heesch2021-05-031-122/+116
|
* Merge branch 'vertical_alignment_table' of ↵Dimitri van Heesch2021-05-021-0/+2
|\ | | | | | | https://github.com/DuyDang007/doxygen into DuyDang007-vertical_alignment_table
| * Support vertical alignment in multirow tableDuy Dang2021-02-011-0/+2
| |
* | Merge pull request #8509 from albert-github/feature/bug_formula_mjDimitri van Heesch2021-05-011-1/+1
|\ \ | | | | | | Problems with some commands in MathJax
| * \ Merge branch 'master' into feature/bug_formula_mjDimitri van Heesch2021-04-281-11/+11
| |\ \
| * | | Problems with some commands in MathJaxalbert-github2021-04-201-1/+1
| | | | | | | | | | | | | | | | | | | | Especially with commands like `\f$\mbox{\LaTeX}\f$`MathJax has some problem as it is not, yet, able to use the commands `\raise` and `lower` inside the `\mbox` as used in this LaTeX command. Also switching in and out of math-mode doesn't work as the resulting code either doesn't work in MathJax or in LaTeX, hence the new command s `\f(` and `\f)`.
* | | | Merge branch 'feature/bug_startuml' of ↵Dimitri van Heesch2021-05-011-0/+3
|\ \ \ \ | |_|/ / |/| | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_startuml
| * | | Extending startuml with extra figure typesalbert-github2021-04-041-0/+3
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | 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: make qcstring.h a local includeDimitri van Heesch2021-03-261-2/+1
| |
* | Refactoring: remove unused QString dependenciesDimitri van Heesch2021-03-231-3/+0
| |
* | Refactoring: some cleanup and removed text direction logicDimitri van Heesch2021-03-041-51/+2
|/
* Refactoring: modernize docparser and clientsDimitri van Heesch2021-01-221-61/+58
|
* Refactor: modernize markdown and make it thread-safeDimitri van Heesch2020-06-161-50/+53
|
* Enabled stricter compiler warnings and fixed all new warningsDimitri van Heesch2020-03-081-34/+32
|
* Compilation warningsalbert-github2020-02-221-1/+0
| | | | | | | | | | | | | | | Due to ``` Commit: 1a56a39b4a97452a5c7c2d8e9d39ab28ca33dff0 [1a56a39] Commit Date: Friday, February 21, 2020 9:07:13 PM Restructure section handling ``` a number of compilation warnings (Windows) appeared: ``` c:\projects\doxygen\src\section.h(51): warning C4099: 'SectionInfo': type name first seen using 'struct' now seen using 'class' [C:\projects\doxygen\build\src\_doxygen.vcxproj] c:\projects\doxygen\src\section.h(50): note: see declaration of 'SectionInfo' ```
* Adding commands `\rtfinclude`, `\docbookinclude`, `\maninclude` and ↵albert-github2020-01-091-1/+1
| | | | | | `\xmlinclude` Adding for consistency with `\*only`, `\htmlincclude` and `\latexinclude` the commands: `\rtfinclude`, `\docbookinclude`, `\maninclude` and `\xmlinclude`
* Merge branch 'feature/bug_html_s' of ↵Dimitri van Heesch2019-12-261-1/+2
|\ | | | | | | 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-1/+2
| | | | | | | | | | | | Adding the HTML `<s>` tag (https://www.w3schools.com/tags/tag_s.asp). Adding 's' and correcting 'inc' to 'ins' in compound.xsd
* | Minor tweaksDimitri van Heesch2019-12-251-2/+2
| |
* | Merge branch 'master' into feature/bug_style_changeDimitri van Heesch2019-12-251-63/+63
|\ \
| * \ Merge branch 'master' into spellingDimitri van Heesch2019-12-231-61/+61
| |\ \
| | * | Coverity uninitializedalbert-github2019-12-021-61/+61
| | | | | | | | | | | | | | | | Fixing a number of uninitialized variables based on the coverity output of November 30, 2019
| * | | spelling: embeddingJosh Soref2019-11-121-2/+2
| |/ /
* | | Warning with XML / HTML style commandsalbert-github2019-10-201-2/+4
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /// set <var> var start_interp </em> void fie(void); /// set <i> i start_interp void fie1(void); ``` we get the warnings (doubles omitted): ``` .../bb.h:5: warning: end of comment block while expecting command </em> ``` so - discrepancy between `<var>` and closing `</em>` is not reported, but wrong for as opening and closing tag should have the same tag name. - the missing `</i>` is reported as a missing `</em>` The problems here are due to the fact that `<var>`, `<i>` and `<em>` share all the style `HTML_EMPHASIS`, this problem has been fixed by adding the used tag name to the style information and testing o n the name and not the style type. The result is now: ``` .../bb.h:1: warning: found </em> tag while expecting </var> .../bb.h:2: warning: end of comment block while expecting command </var> .../bb.h:5: warning: end of comment block while expecting command </i> ``` so now the real problems are reported.
* | Reduce the use of QString in favor of the more efficient QCStringDimitri van Heesch2019-09-211-0/+1
| |
* | issue #7216: non-const getGroupDef() called on aliased member (cleanup + ↵Dimitri van Heesch2019-08-261-2/+1
|/ | | | null pointer fix)
* Merge branch 'feature/issue_6831' of ↵Dimitri van Heesch2019-08-041-1/+15
|\ | | | | | | 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-1/+15
| | | | | | | | | | | | | | | | 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-1/+3
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-fetaure/bug_html_ins_del_tag
| * | Adding HTML tags ins and delalbert-github2019-04-041-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Non existing MSC file crashes doxygenDimitri van Heesch2019-07-291-3/+3
| | |
* | | Remove not used classalbert-github2019-07-071-18/+0
| | | | | | | | | | | | | | | | | | | | | As per comment in `docvisitor.h`: ``` class DocCopy; // TODO: no longer generated => remove ```
* | | Improved const correctness and added support for inline namespacesDimitri van Heesch2019-04-211-6/+6
|/ /
* | Merge branch 'feature/bug_lineno_split_examples' of ↵Dimitri van Heesch2019-03-091-1/+6
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_lineno_split_examples
| * | Show line numbers in "split" examplesalbert-github2019-03-031-1/+6
| | | | | | | | | | | | | | | | | | 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.
* | | Minor refactoringDimitri van Heesch2019-03-031-1/+12
|/ /
* | a named anchor does not need custom attributes and minor other corrections.Dimitri van Heesch2019-02-171-4/+2
| |
* | Bug 136299 - attributes to <p> tag get lostalbert-github2019-02-041-3/+20
|/ | | | | | | | | | | Besides the `p` tag there were a number of other tags were also the attributes were lost: - `br` - `hr` - `a` in case of used as an anchor i.e. with the `name=` attribute In case of a `caption` with a `table` and no `id=` attribute with the `caption` there was still an anchor generated In scanner.l the warnings message was a bit unclear.
* Issue #6039: Links on image in Markdown (Origin: bugzilla #769223)Dimitri van Heesch2019-01-031-0/+1
|
* Merge branch 'feature/bug_escaped_equal_sign' of ↵Dimitri van Heesch2018-12-261-1/+1
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_escaped_equal_sign
| * Create command for escaped equal signalbert-github2018-11-071-1/+1
| | | | | | | | This command writes an equal sign (`=`) to the output. This character sequence has to be escaped in some cases, because it is used in Markdown header processing.
* | Improved robustness of the emoji featureDimitri van Heesch2018-12-231-6/+7
| | | | | | | | | | | | | | | | 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.
* | Merge pull request #6643 from albert-github/feature/bug_xhtml_test_30Dimitri van Heesch2018-12-031-2/+4
|\ \ | | | | | | Incorrect number tag sequence for xhtml with htmlinclude command possible
| * | Incorrect number tag sequence for xhtml with htmlinclude command possiblealbert-github2018-11-251-2/+4
| | | | | | | | | | | | | | | | | | Analogous to the `\htmlonly` also with the `\htmlinclude` command it is possible that some parts are added that cannot be inside a `<p> ... <\/p>` and thus we have to temporary close (and later reopen) the paragraph. The option `[block]` has been added to the `\htmlinclude` command (analogous to the `\htmlonly` command). Problem can be seen with the default doxygen test 30 (`[030_htmlinclude.dox]: test the \htmlinclude command`).
* | | Restructured code to avoid the need for global stateDimitri van Heesch2018-11-251-1/+1
|/ /
* | Merge branch 'feature/bug_inline_image' of ↵Dimitri van Heesch2018-11-111-1/+3
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_inline_image
| * | Inline imagesalbert-github2018-08-091-1/+3
| | | | | | | | | | | | Create the possibility of inline images with the `\image` command by means of the option `inline`.
* | | Merge branch 'feature/issue_6517' of ↵Dimitri van Heesch2018-11-111-2/+18
|\ \ \ | |_|/ |/| | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_6517