summaryrefslogtreecommitdiffstats
path: root/src/doctokenizer.l
Commit message (Collapse)AuthorAgeFilesLines
* 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
| |
* | Merge branch 'feature/bug_warning_msg' of ↵Dimitri van Heesch2018-10-271-9/+10
|\ \ | |/ |/| | | https://github.com/albert-github/doxygen into albert-github-feature/bug_warning_msg
| * Correcting warning messages and echoing unknown commandalbert-github2018-08-261-9/+10
| | | | | | | | | | | | - In case an unknown command is given this was shown as a warning but not as normal text in the output, for this also a distinction between `\`and `@` commands has to be made - corrected command name in warning messages when handling arguments - making handling of some warning messages consistent
* | Merge pull request #6419 from albert-github/feature/bug_env_consistencyDimitri van Heesch2018-09-021-1/+2
|\ \ | | | | | | Consistency of environment variables between config and code
| * | Consistency of environment variables between config and codealbert-github2018-08-021-2/+2
| | | | | | | | | | | | Made consistent with pull request #6420
| * | Consistency of environment variables between config and codealbert-github2018-08-021-1/+2
| | | | | | | | | | | | In a configuration file it was possible to have an environment variable like PROGRAMFILES(X86) but in the code this was not possible.
* | | Merge pull request #6388 from albert-github/feature/bug_740046_regressionDimitri van Heesch2018-09-011-1/+1
|\ \ \ | | | | | | | | Section label with minus sign not recognized properly.
| * | | Section label with minus sign not recognized properly.albert-github2018-07-101-1/+1
| |/ / | | | | | | | | | | | | | | | | | | This is a regression on: Bug 740046 - Negative sign in -Foo::Bar ruins hyperlink in generated output only the first character is has to be handled in the new way. (Reference to old github pull request #704 and issue #5677)
* | | Merge branch 'feature/bug_667993' of ↵Dimitri van Heesch2018-08-261-2/+2
|\ \ \ | |_|/ |/| | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_667993
| * | Bug 667993 - HTML tags <u> and </u> not supportedalbert-github2018-07-071-2/+2
| |/ | | | | | | 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 691689 - Line numbers for examplesDimitri van Heesch2018-08-191-0/+17
|/
* Merge pull request #704 from albert-github/feature/bug_704046Dimitri van Heesch2018-04-221-1/+4
|\ | | | | Bug 740046 - Negative sign in -Foo::Bar ruins hyperlink in generated output
| * Bug 740046 - Negative sign in -Foo::Bar ruins hyperlink in generated outputalbert-github2018-04-121-1/+4
| | | | | | | | Excluded digits and '+' sign and '-' sign from determination of Words.
* | Bug 688387 - JavaDoc @linkplain is not recognizedalbert-github2018-02-261-1/+1
|/ | | | See to it that the, JavaDoc version of the, command @link cannot be confused with @linkplain.
* Fix/New: add variadic function args '...' support to @refMatthew White2017-08-031-1/+2
| | | | | | | | | | | | | * src/doctokenizer.l: add VARARGS, aka variadic function args '...' * src/util.cpp (linkToText): call substitute() with skip_seq set to 3 to keep each '...' sequence of chars unchanged For instance, the command '@ref fun(int,...)' now is able to parse each '...' sequence of chars correctly to reference fun(int,...). Before this patch, the '...' part was skipped. Also, linkToText() is fixed to not substitute '...' with '::::::' in the text representation of the link.
* Bug 776988 - Too greedy behavior of @ref const matchingDimitri van Heesch2017-01-171-4/+16
|
generated by cgit v0.12 at 2024-11-05 07:41:58 (GMT)