summaryrefslogtreecommitdiffstats
path: root/src/markdown.cpp
Commit message (Collapse)AuthorAgeFilesLines
* issue #7996 \ref commands broken in markdown tablesalbert-github2020-09-021-1/+1
| | | | the `\ilinebr` (internal line break) should be properly be separated from previous text.
* Spelling corrections is commentsalbert-github2020-08-091-1/+1
| | | | Some spelling omissions found by Fossies.
* Simplified code by passing lineNr directlyDimitri van Heesch2020-08-061-3/+1
|
* Coverity uninitialized variablealbert-github2020-08-061-1/+1
| | | | Coverity reported new uninitialized variable
* Fix for markdown emphasis processing regression.Dimitri van Heesch2020-08-051-2/+7
| | | | | Prevent <TT>__BLA</TT> .... <TT>BLA__</TT> from being detected as an emphasis section and causing the wrong output.
* Merge pull request #7782 from wataash/tagend-markdown-emDimitri van Heesch2020-08-031-2/+2
|\ | | | | issue #7781: allow '>' before Markdown emphasis
| * issue #7781: allow '>' before Markdown emphasisWataru Ashihara2020-05-231-2/+2
| |
* | Merge branch 'feature/issue_7923' of ↵Dimitri van Heesch2020-07-281-3/+5
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_7923
| * | issue #7923 source line numbers in warnings output by parser are off by 1albert-github2020-07-271-3/+5
| | | | | | | | | | | | Explicit counting of the removed newlines at the beginning of a documenation block (markdown.cpp) so this number can be added to get a better line number in case of warnings.
* | | Additional tweaks to get markdown tables inside ALIASES workDimitri van Heesch2020-07-271-14/+150
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Changed \_linebr to \ilinebr - \ilinebr is now also passed to doctokenizer - Also fixes issue #7493 regarding \snippet inside markdown tables and dealing with wrong line on issues detected by docparser after a markdown table. - Added function tracing to markdown (enabled with -d markdown in a debug build)
* | | Merge branch 'feature/issue_7787' of ↵Dimitri van Heesch2020-07-251-3/+17
|\ \ \ | |/ / |/| | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_7787
| * | issue #7787 Doxygen 1.8.18: Markdown tables not working in ALIASES anymore?albert-github2020-05-201-3/+17
| | | | | | | | | | | | The artificial newline characters in ALIASES (`^^`) or better said its doxygen replacements (`\\_linebr`) were not seen by the markdown parser as line terminator and as a consequence there was no table seen (it was just 1 long line, without header / data lines)..
* | | issue #7911 markdown table add extra test to "\copybrief"albert-github2020-07-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | The comment speaks of: > // need at least one space on either side of the cell text in > // order for doxygen to do other formatting but in the implementation the end space is missing. Looks like the problem is introduced in version 1.8.17 when some work is done on the line counting (removing artificial `\n`).
* | | Refactor: Modernize clang parser and make it run with multiple threadsDimitri van Heesch2020-07-161-2/+1
| | |
* | | Multi-threaded parsing: added locks around global dataDimitri van Heesch2020-06-171-8/+0
| | |
* | | Refactor: modernize markdown and make it thread-safeDimitri van Heesch2020-06-161-421/+304
| | |
* | | issue #7796 Backticks (`) in Doxygen-markup-in-C in Markdown collapses (#7797)albert-github2020-06-131-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * issue #7796 Backticks (`) in Doxygen-markup-in-C in Markdown collapses The problem occurs when the backtick is just before the end of line. The fenced block will only terminate when the same number of fence characters are present, otherwise the search will continue. * issue #7796 Backticks (`) in Doxygen-markup-in-C in Markdown collapses Removed unintentional tab.
* | | Added experimental multi-thread input processing support.Dimitri van Heesch2020-05-311-10/+8
| |/ |/| | | | | | | This is disabled by default. It can be enabled by setting MULTITHREADED_INPUT to 1 in doxygen.h. Still has many data races, so don't use for anything other than development!
* | issue #7595 Links from one Markdown file to another do not workalbert-github2020-05-211-2/+4
|/ | | | | - the not linking in case of a the relative path (as there was no anchor for it) - (on windows) the created, internal, anchor for a file can contain a `:` but this is not possible in an anchor and has to be escaped.
* Fix for Portable::isAbsolutePathDimitri van Heesch2020-04-061-1/+1
|
* Merge branch 'master' of github.com:doxygen/doxygenDimitri van Heesch2020-04-061-0/+14
|\
| * Relative markdown file reference (#7032)albert-github2020-04-061-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case we have a relative reference to a local markdown file this file is not found when the relative path starts e.g. with `..` So when we have a file: ``` docs\tutorial\security.md ``` and this references the file: ``` ../api/browser-window.md ``` through the markdown syntax: ``` [`BrowserWindow`](../api/browser-window.md) ``` then the link was not found and a warning was given.
* | Replaced FileNameDict/FileNameList by FileNameLinkedMapDimitri van Heesch2020-04-061-57/+57
|/
* issue #7672 Request: use <img> tags instead of <object> tags for SVG imagesalbert-github2020-03-291-1/+1
| | | | | In case of svg and inline images we have to follow a little bit another strategy. In markdown we also have to declare all markdown images to inline images (which is also consistent with the handling on github)
* Fixed unsigned/signed character warningsDimitri van Heesch2020-03-111-4/+4
|
* Remove dead code and fix more warningsDimitri van Heesch2020-03-081-1/+1
|
* Enabled stricter compiler warnings and fixed all new warningsDimitri van Heesch2020-03-081-12/+5
|
* Restructure section handlingDimitri van Heesch2020-02-211-9/+9
|
* A mainpage doesn't have an anchor to jump toalbert-github2020-01-141-0/+2
| | | | | Based on the question: https://stackoverflow.com/questions/59685012/doxygen-markdown-links-to-main-page-do-not-work?noredirect=1#comment105616212_59685012 The markdown mainpage has no anchor so it is not possible to link to it, added an anchor so it is consistent with other page commands.
* Make commentscan.l reentrantDimitri van Heesch2019-12-301-2/+45
|
* Fix for use of non portable strnstr functionDimitri van Heesch2019-12-231-1/+2
|
* Optimize UTF-8 nbsp conversion in markdownDimitri van Heesch2019-12-221-6/+17
|
* Merge branch 'feature/bug_nbsp_code' of ↵Dimitri van Heesch2019-12-221-5/+6
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_nbsp_code
| * Text '&nbsp;' appears in code segmentsalbert-github2019-08-231-5/+6
| | | | | | | | | | In case we have the UTF-8 code for nbsp in our source this is (see #6983) replaced with `&nbsp;`, though in code fragments this is unwanted as here the text appears literally. the UTF-8 nbsp is temporary replaced by a "doxygen" tag and for fenced code blocks, backtick blocks and special bloc commands (code, verbatim, htmlonly, formulas,...) replaced back with the UTF-8 version, the remaining "doxygen" tags are at the end replaced with `&nbsp;`
* | Merge pull request #7231 from albert-github/feature/issue_7228Dimitri van Heesch2019-12-211-5/+5
|\ \ | | | | | | issue #7228 Using markdown causes wrong error and warning line numbers - v. 1.8.16
| * | issue #7228 Using markdown causes wrong error and warning line numbers - v. ↵albert-github2019-08-271-5/+5
| |/ | | | | | | | | | | 1.8.16 Sacrificing some readability of the debug `-d markdown` output for a better approximation of the line numbers by keeping the rows of a markdown table on one line when translating to a HTML table.
* | Changed std::unique_ptr<Entry> to std::shared_ptr<Entry> at avoid use after ↵Dimitri van Heesch2019-12-081-2/+2
| | | | | | | | free issues
* | Split language parser into "outline parser" and "code parser"Dimitri van Heesch2019-12-031-39/+6
| |
* | Problem with horizontal ruler directly after fenced code sectionalbert-github2019-11-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When having a fenced code block directly followed by a horizontal ruler like: ``` ~~~ B ~~~ --- ``` we get the warning: ``` bb.md:5: warning: unexpected command endcode ``` due to the fact that the markdown parser replaces the `~~~` by a `@code` / `endcode` block and then handles the horizontal ruler `---` but this is seen as a level 2 header on the previous part resulting in the markdown code: ``` @page md_bb bb @subsection autotoc_md0 @code B @endcode ``` The problem also occurs when a fenced code block is created with back tics. By adding a `\n` this problem is fixed.
* | 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).
* | Use smartpointers to manage the lifetime of Entry objectsDimitri van Heesch2019-10-071-6/+5
| |
* | Reduce the use of QString in favor of the more efficient QCStringDimitri van Heesch2019-09-211-1/+1
| |
* | Generalized the HTML comment detection and handlingDimitri van Heesch2019-09-161-8/+3
| |
* | Merge branch 'feature/bug_html_comment' of ↵Dimitri van Heesch2019-09-161-1/+6
|\ \ | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_html_comment
| * | HTML start comment with 3 dashesalbert-github2019-09-051-1/+6
| |/ | | | | | | | | | | | | A normal HTML comment `<!--` has 2 `-` signs but it is not prohibited to have 3, but doxygen translates `<!---` into `<!-&ndash;` and thus the comment is not recognized. By checking and consequently handling, doing the right skipping, also the 3 `-` sign version the problem can be solved. An end comment cannot contain 3 `-` signs, so here no changes have to take place. The version with 3 or more `-` are in a start HTML comment does not give a problem with xmllint either.
* | Fix some typos luz.paz2019-09-161-1/+1
|/
* issue #7143 note block not generated properly if there are blanks after italbert-github2019-08-051-1/+1
| | | | In case minimal 2 spaces at the end of a line a line break is inserted, but the line was not terminatd so it was concatinated with the next line.
* 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
* | issue #7151 Doxygen 1.8.15 TOC_INCLUDE_HEADINGS >0 stops html links being ↵albert-github2019-08-011-0/+1
| | | | | | | | | | | | | | generated in markdown Don't create autotoc generated ids for pages. (the `\ref` problem also occurred with `\subage`).
generated by cgit v0.12 at 2024-10-31 18:23:44 (GMT)