summaryrefslogtreecommitdiffstats
path: root/src/markdown.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Miscounting of lines in respect to page command (ATX header)albert-github2020-10-101-0/+1
| | | | | | | | | | In case of an ATX header for a page at the beginning of a file (i.e. `#...`) there is a line miscounting. Analogous as done for lines type: ``` The page ==== ``` in pull request #8056 we have to add an extra newline.
* Incorrect counting of markdown verbatim blockalbert-github2020-10-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have a file aa.md like: ``` Initial text 1 verbatim text? Some text \aa5 ``` and a file bb.md like ``` Initial text 1 verbatim text? Some text \aa4 `` we get the warnings like (with current master, with 1.8.20 it is even further off): ``` aa.md:6: warning: Found unknown command '\aa5' bb.md:5: warning: Found unknown command '\aa4' ``` instead of ``` aa.md:5: warning: Found unknown command '\aa5' bb.md:4: warning: Found unknown command '\aa4' ``` This has been corrected
* added support for mingw PRETTY_FUNC (#8059)ArmandZampieri2020-10-051-1/+1
| | | | | | | | | * added support for mingw PRETTY_FUNC * More compact Define test for PRETTY_FUNCTION * corrected synthax issue Co-authored-by: ZAMPIERI Armand <armand.zampieri@cmigroupe.com>
* Merge branch 'feature/bug_md_pg_cnt' of ↵Dimitri van Heesch2020-10-031-17/+19
|\ | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/bug_md_pg_cnt
| * Miscounting of lines in respect to page commandalbert-github2020-09-241-17/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All examples together are a bit big so they are all in the attached file together with the warnings before and after this patch. When looking at the output we see that a number of lines are off by 1 ore more due to the insertion of extra lines in the code or due to the fact that there is a reference to the start of the documentation of the page and not the line of the page command. - commentscan.l in case of a rule contaiinge {DOCNL} this can be `=n` or `\ilinebr` in the later case this should not be replaced by `\n` as this results in an increase of the line count later on. in case of a page like command also register the line of the command as "topline". - entry.h, entry.cpp storage space for the "topline" registering the line of the page like commands. - doxygen.cpp setting and using the "topline" - markdown.cpp, markdown.h don't add a `\n` as this increases the line count but use the `\ilinebr` to get correct warnings see to it that when having empty lines at the top of the page and a page is added that the empty lines appear after the page command. - index.cpp using the "topline" instead of the "docLine" to get the correct warning - pagedef.cpp, pagedef.h set and retrieve the "topline" for page like commands. - util.cpp, util.h setting and using the "topline" in `addRelatedPage` use the known file name and line for the warning regarding the section label - cite.cpp, context.cpp, reflist.cpp changed to have good function calls.
* | No warning for unbalanced brackets in markdownalbert-github2020-09-251-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have the input files qq.md. ``` @page xxx0 yyy0 @} Start of text @page xxx1 yyy1 @{ Start of text ``` and qqh.h: ``` /** @page xxxh0 yyyh0 @} Start of texth */ /** @page xxxh1 yyyh1 @{ Start of texth */ ``` we get the warnings: ``` qq.md:3: warning: unbalanced grouping commands qqh.h:4: warning: unbalanced grouping commands qqh.h:15: warning: end of file with unbalanced grouping commands ``` ``` so we are missing ``` qq.md:9: warning: end of file with unbalanced grouping commands ``` due to the fact that the closing routine was not called (also the open routine was not called, always good to call it the set variables to their proper values.
* | Merge pull request #8045 from albert-github/feature/bug_md_fenced_cntDimitri van Heesch2020-09-241-1/+1
|\ \ | |/ |/| Miscounting of lines in case of fenced code block
| * Miscounting of lines in case of fenced code blockalbert-github2020-09-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have an example like: ~~~ Page ======= test text test text \error1 ``` make ``` ``` make ``` test text \error2 ~~~ we get the warnings: ``` aa.md:5: warning: Found unknown command '\error1' aa.md:17: warning: Found unknown command '\error2' ``` instead of ``` aa.md:5: warning: Found unknown command '\error1' aa.md:15: warning: Found unknown command '\error2' ``` this is due to the fact that there are 2 returns in case of a fenced code block, one with the ``endcode` but with the detection of the fenced code block (`isFencedCodeBlock`) it is not "removed".
* | issue #8037: Links using @ref stopped working in doxygen 1.8.19Dimitri van Heesch2020-09-211-0/+1
|/
* 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
| |
generated by cgit v0.12 at 2024-11-16 02:00:19 (GMT)