summaryrefslogtreecommitdiffstats
path: root/src/doctokenizer.l
Commit message (Collapse)AuthorAgeFilesLines
* Replaced \_fakeform by \_formDimitri van Heesch2019-12-261-3/+3
|
* Merge branch 'feature/bug_formula' of ↵Dimitri van Heesch2019-12-261-3/+3
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_formula
| * Better warning in case of `@form`albert-github2019-11-061-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /** \file */ /** * The fie * * @form: the new format * @content: the content of the form * * Sets @form content to be @content. * * \f$ \alpha \f$ \f[ \beta \f] */ void fie(char *form, char *content); ``` we get warnings like: ``` .../aa.h:5: warning: Wrong formula id -1 .../aa.h:6: warning: Found unknown command '\content' .../aa.h:8: warning: Wrong formula id -1 .../aa.h:8: warning: Found unknown command '\content' ``` The `@form:` is in RST analogue to the doxygen `@param form` but not understood by doxygen. The result is that it is seen as an formula as doxygen translates the formula commands to `\form`. For `@content` is handled properly as this is not a doxygen command. In this patch a more unique name is chosen so these type of conflicts don't appear (that easy). The resulting, better, warnings are now: ``` .../aa.h:5: warning: Found unknown command '\form' .../aa.h:6: warning: Found unknown command '\content' .../aa.h:8: warning: Found unknown command '\form' .../aa.h:8: warning: Found unknown command '\content' ```
* | Merge branch 'feature/bug_html_s' of ↵Dimitri van Heesch2019-12-261-2/+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-2/+2
| | | | | | | | | | | | | | | | | | Adding the HTML `<s>` tag (https://www.w3schools.com/tags/tag_s.asp). Adding 's' and correcting 'inc' to 'ins' in compound.xsd
* | | Merge branch 'feature/bug_unsupported_html' of ↵Dimitri van Heesch2019-12-181-3/+5
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_unsupported_html
| * | | Output of unknown xml/html tagalbert-github2019-11-061-10/+21
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a problem like: ``` /** \file - Just name <name> - name plus subname <name subname> - name plus twice subname <name subname subname> - name plus subname subname="" <name subname subname=""> */ ``` we get correctly the warnings: ``` .../aa.h:3: warning: Unsupported xml/html tag <name> found .../aa.h:4: warning: Unsupported xml/html tag <name> found .../aa.h:5: warning: Unsupported xml/html tag <name> found .../aa.h:6: warning: Unsupported xml/html tag <name> found ``` but the output doesn't look good as there is `=""` added: ``` Just name <name> name plus subname <name subname=""> name plus twice subname <name subname="" subname=""> name plus subname subname="" <name subname="" subname=""> ``` This patch fixes this output.
* | | Made regexp more strictDimitri van Heesch2019-12-181-5/+6
| | |
* | | Merge branch 'feature/bug_nospam_email' of ↵Dimitri van Heesch2019-12-181-0/+5
|\ \ \ | | | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_nospam_email
| * | | Simple nospam email addressalbert-github2019-11-051-0/+5
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a simple nospam email address coded like: ``` /** \file * Big Unknown <big at none dot com> */ ``` this results in the warning: ``` aa.c:2: warning: Unsupported xml/html tag <big> found ``` and in the HTML output it looks like: ``` Big Unknown <big at none dot com> ``` instead of: ``` Big Unknown <big at none dot com> ``` (Found in a couple of open source projects).
* | | Renamed Portables to PortableDimitri van Heesch2019-12-081-1/+1
| | |
* | | Merge branch 'memory_leakage_fix' of https://github.com/virusxp/doxygen into ↵Dimitri van Heesch2019-12-081-1/+1
|\ \ \ | | | | | | | | | | | | virusxp-memory_leakage_fix
| * | | Refactoring of portable.h and portable.cpp functions to be contained in a ↵Tobias Off2019-11-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | namespace Fixing some memory issues caused by not correctly freed pointers
* | | | Remove bogus flex codeDimitri van Heesch2019-11-181-5/+0
|/ / /
* | | Spelling corrections for src directoryalbert-github2019-11-051-2/+2
|/ / | | | | | | | | | | | | | | Spelling corrections as found by codespell and in #561. Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.): - "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...) - "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
* | HTML attribute namealbert-github2019-09-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | A HTML attribute name can have e.g. a XML namespace in it and thus containing a colon (`:`) like: ``` <span xmlns:dct="http://purl.org/dc/terms/" property="dct:title">Social Icons</span> ``` but this results in ``` warning: found </span> tag without matching <span> ``` and grabled outpuzt. allowing a colon in the attribute name solves this problem
* | Merge branch 'feature/bug_consistency_state_2' of ↵Dimitri van Heesch2019-09-121-0/+2
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_consistency_state_2
| * | Consistent way to show scanner statealbert-github2019-09-051-0/+2
| | | | | | | | | | | | | | | Create a consistent way to display the state mnemonics of the different scanners (analogous to the fortranscanner.l) Use an automatic procedure to generate the routine with the translation of the states to a string.
* | | Bogus explicit link warning message from irc protocol namealbert-github2019-09-111-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having: ``` * IRC: irc://irc.gimp.org/#gsconnect ``` we get: ``` warning: explicit link request to 'gsconnect' could not be resolved ``` When using the 'news:" protocol we don't get this message, adding 'irc' to the list of possibilities. (Found in https://github.com/andyholmes/gnome-shell-extension-gsconnect )
* | | issue #6715: Errorneous matching of the immediately following block command ↵Dimitri van Heesch2019-09-071-2/+2
|/ / | | | | | | after @ref (try 2)
* | issue #7216: non-const getGroupDef() called on aliased member (cleanup + ↵Dimitri van Heesch2019-08-261-10/+4
|/ | | | null pointer fix)
* Problem with '<td nowrap>'albert-github2019-08-101-1/+1
| | | | | | In the docbook ouput this was shown with the attribute `nowrap>=''`, in HTML this empty tag was skipped. Normally a HTML attribute will have a value but in some cases it is possible without attribute and when this is the last attribute the `>` was accidently added to the attribute (in case of the value the `>` was already considered). Furthermore `In XHTML, attribute minimization is forbidden, and the nowrap attribute must be defined as <td nowrap="nowrap">.`, this is now handled for HTML and docbook as well.
* Merge branch 'feature/bug_endblock_msg' of ↵Dimitri van Heesch2019-08-041-5/+5
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
| * Correction warning messagealbert-github2019-06-011-5/+5
| | | | | | | | Consistency
* | Merge branch 'feature/issue_6831' of ↵Dimitri van Heesch2019-08-041-1/+1
|\ \ | | | | | | | | | 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/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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-2/+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-2/+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.
* | Merge pull request #7017 from albert-github/feature/bug_rcs_perlDimitri van Heesch2019-05-311-1/+1
|\ \ | | | | | | Conflict between RCS tag and (e.g.) php description
| * | Conflict between RCS tag and (e.g.) php descriptionalbert-github2019-05-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some languages the `$` is used to start a variable name (php, perl). When having a description like: ``` <b>$RRDp::error_mode</b>, <b>$RRDp::error</b> ``` this will lead to a message like: ``` warning: found </b> at different nesting level (4) than expected (2) ``` because the part `$RRDp:` is seen as start of a RCS tag and runs till the next `$`. Though the `::` indicates here a class / namespace separator and in case of `$...:` directly followed by a `:` this should not be seen as RCS tag.
* | | issue 7015 Parsing issue with @includedoc and @startumlalbert-github2019-05-291-0/+1
|/ / | | | | | | In case of `\includedoc` the `\n` was not handled on the first line (`@startuml`)
* | issue #6917 Crash in php with UTF-8 characteralbert-github2019-04-191-5/+5
|/ | | | Also in HTML tag handling.
* issue #6796 Bad link to section, subsection if pointing at item past ↵albert-github2019-01-261-1/+1
| | | | | | suspicious text To escape `\` and `@` not only `\\` and `@@` should be possible but also `\@` and `@\`
* 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-46/+14
| | | | | | | | | | | | | | | | 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 #6699 from albert-github/feature/bug_emoji_false_positiveDimitri van Heesch2018-12-201-4/+4
|\ \ | | | | | | issue #6691 Multiple issues with emoji matching
| * | issue #6691 Multiple issues with emoji matchingalbert-github2018-12-201-4/+4
| | | | | | | | | | | | | | | This fix is regarding the false positive emoji detection of scope rules like: `Platform::*Application::viewportEvent(const Vector2i&)` In case the "emoji" is followed by and extra `:` it is not seen as an emoji anymore.
* | | Fix for unbounded memory usage due to a bug in \ref const matching #6689Dimitri van Heesch2018-12-201-1/+1
|/ /
* | XHTML incorrect attribute values for align and valignalbert-github2018-12-081-0/+6
| | | | | | | | | | | | The attribute values of the `align` and `valign` attribute have to be in lowercase and the `valign` attribute value `center` does not exist but has to be `middle`. Most browsers do accept the 'incorrect' values but it is better to have the right values present. (Found by means of the CGAL/cgal repository)
* | Incorrect number tag sequence for xhtml with htmlinclude command possiblealbert-github2018-11-251-0/+13
| | | | | | | | | | | | 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`).
* | Extending \cite command with '-' and '?' characters.albert-github2018-11-171-4/+12
| | | | | | | | In the `\cite` label some extra characters are enabled, '-' and '?', as the '--' and '---' have been converted beforehand they have to be converted back and the corresponding labels also have to between double quotes (which are striped away).
* | issue 6612 Issue with handling of emojialbert-github2018-11-121-10/+39
| | | | | | | | | | | | Regression on adding emoji. - in case of multiple levels of `::` (e.g. `U::V::W`) this resulted in the fact that `:V:` was seen as an emoji and handled as such - in a citelist it is possible to have `pages = {104:1--104:8},`, `number = {4},` and `volume = {28},` but this is translated into `28(4):104:1&ndash;104:8` giving a false positive on `:104:`. the citelist has been excluded from emoji handling.
* | Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2018-11-111-1/+1
|\ \
| * | Invalid warnings regarding todos when source file name contains a '-'albert-github2018-11-091-1/+1
| |/ | | | | | | Handling also filenames in scope environment
* | Merge branch 'feature/issue_6517' of ↵Dimitri van Heesch2018-11-111-0/+20
|\ \ | |/ |/| | | https://github.com/albert-github/doxygen into albert-github-feature/issue_6517
| * issue_6517: Emoji supportalbert-github2018-10-011-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Bug 795568 - "unexpected token TK_EOF as the argument of ref" when target ↵albert-github2018-11-021-2/+2
| | | | | | | | | | | | starts with a digit Enable possibility to reference to file names as well (some filenames ere supported as side effect of other rules).
* | Renamed command and moved duplicated code into a macroDimitri van Heesch2018-10-271-13/+15
| |
generated by cgit v0.12 at 2024-07-05 07:40:39 (GMT)