summaryrefslogtreecommitdiffstats
path: root/src/markdown.cpp
Commit message (Collapse)AuthorAgeFilesLines
* 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`).
* | issue #7113 Doxygen doesn't process markdown tables correctlyalbert-github2019-07-101-1/+1
| | | | | | | | Better to have the end tag start at a new line so it cannot be added to a command that runs till the end of the line
* | issue #7043 html output for markdown: different output when using '# Header ↵albert-github2019-06-091-1/+4
| | | | | | | | | | | | {#mainpage}' and 'Header {#mainpage}\n====' In case of an ATX header the id was overwritten again by the subsequent call to extractTitleId, this should only happen in case of a non ATX header ('===' headers returned already beforehand).
* | Bug 757574 - Warning regarding subsection with anchor in markdownDimitri van Heesch2019-06-021-4/+14
|/
* Bug 757574 - Warning regarding subsection with anchor in markdownDimitri van Heesch2019-05-271-3/+25
|
* Bug 757574 - Warning regarding subsection with anchor in markdownDimitri van Heesch2019-05-201-15/+8
|
* Merge pull request #6983 from albert-github/feature/bug_utf8_nbspDimitri van Heesch2019-05-181-6/+19
|\ | | | | Special handling of the UTF8 nbsp sequence
| * Special handling of the UTF8 nbsp sequencealbert-github2019-05-111-6/+19
| | | | | | | | | | | | | | | | | | | | The UTF8 nbsp sequence 0xc2 0xa0 is not seen as a whitespace sequence and not handled properly. This can lead to: ``` warning: found </c> tag without matching <c> ``` when we have e.g. ```e.g. `linux`<br>``` where the space between the `.` and the backtick is actually the UTF8 nbsp sequence Replacing the the UTF8 nbsp sequence with the `&nbsp;` sequence.
* | Merge pull request #6913 from albert-github/feature/url_to_md_fileDimitri van Heesch2019-05-121-1/+1
|\ \ | |/ |/| Markdown file as internet link
| * Markdown file as internet linkalbert-github2019-04-051-2/+0
| | | | | | | | Removed debug statements.
| * Markdown file as internet linkalbert-github2019-04-051-1/+3
| | | | | | | | | | | | | | | | See a link in case of a md file only as local link if it doesn't start with a supported protocol. Example found was: ``` [Ansibullbot](https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md) ```
* | Improved const correctness and added support for inline namespacesDimitri van Heesch2019-04-211-2/+2
|/
* Merge pull request #6784 from albert-github/feature/issue_6781_2Dimitri van Heesch2019-03-171-24/+12
|\ | | | | issue #6781 Unable to use math in markdown table headers
| * issue #6781 Unable to use math in markdown table headersalbert-github2019-01-191-24/+12
| | | | | | | | | | | | Due to the change of the place where the markdown processing is done the end of the line must be calculated a little bit differently. Note: translator.py gave an error due to a strange indentation (did surface now), so had to be corrected as well.
* | issue #6840 Hash character in Markdown code span not rendered correctlyalbert-github2019-02-161-0/+1
| | | | | | | | A hash sign has a special meaning, so it should be escaped in a code span.
* | Minor tweaksDimitri van Heesch2019-01-311-3/+7
| |
* | issue #6800 Markdown line ending problems in 1.8.15 and masteralbert-github2019-01-281-3/+5
|/ | | | | In case of a completely empty line with 2 spaces at the end don't consider this as a 2 space terminated line. Regression of #6448
* issue #6679 Multiple use of section label warning for Setex-stype headers in ↵albert-github2019-01-181-22/+0
| | | | | | | | markdown Due to the move of the markdown code to another place the adding of the section info of section, subsection etc. would be attempted to add twice (first in markdown and later on again when translating the resulting '`section`, `\subsection` commands. The adding should only take place when handling the (replaced) commands. Removing the test in `addSection` won't work as in that case using twice a sectioning command with the same label would not be signaled anymore.
* Merge: moved example from 081 to 084, improved check if last char is newlineDimitri van Heesch2019-01-131-1/+1
|
* No translation of markdown in <pre>albert-github2019-01-111-1/+3
| | | | | | | | | According to the documentation: Doxygen does not have this requirement, and will also process Markdown formatting inside such HTML blocks. The only exception is <pre> blocks, which are passed untouched (handy for ASCII art). Though in case the `</pre>` is the last statement in a non block type comment the markdown is processed. C has block type /* ... */ and /// is translated to this, Fortran, Python are line type comments. Adding a `\n` at the when no `\n` is present at the end solves the problem.
generated by cgit v0.12 at 2024-11-18 10:39:36 (GMT)