summaryrefslogtreecommitdiffstats
path: root/src/markdown.cpp
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* issue #6734 parsing performance worsenedDimitri van Heesch2019-01-071-4/+5
|
* Merge pull request #6516 from albert-github/feature/issue_6513_2Dimitri van Heesch2018-12-011-22/+9
|\ | | | | Does not generate TOC for markdown
| * Does not generate TOC for markdownalbert-github2018-09-161-22/+9
| | | | | | | | | | The markdown handling has been moved to a more logical place and as a consequence the section headers were added and thus checked twice but didn't show the TOC. Also setting up the table of contents level in a more standard way.
* | issue_6601 tparam HTML gobbles up lines after the tparam commentalbert-github2018-11-061-2/+2
| | | | | | | | properly terminate block and see to it that a proper horizontal ruler occurs (as if `<hr>` was used).
* | Merge pull request #6448 from albert-github/feature/bug_markdown_listsDimitri van Heesch2018-10-281-1/+1
|\ \ | | | | | | Markdown list wrong displayed
| * | Markdown list wrong displayedalbert-github2018-08-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some, rare, cases a markdown list was wrongly displayed (regression due to change of place of markdown handling) /** @mainpage * * * elem1 * * elem2 * Some text (actually found due to a table) */
* | | Merge pull request #6553 from albert-github/feature/bug_719541Dimitri van Heesch2018-10-131-14/+25
|\ \ \ | | | | | | | | Bug 719541 - Error with inserting images to PDF with Markdown
| * | | Bug 719541 - Error with inserting images to PDF with Markdownalbert-github2018-10-121-14/+25
| | |/ | |/| | | | | | | Create possibility to use images in other output formats conform the `\image` command.
* | | Merge pull request #6535 from albert-github/feature/issue_6524Dimitri van Heesch2018-10-131-4/+7
|\ \ \ | | | | | | | | issue_6524: Markdown formats missing in doxygen outputs.
| * | | issue_6524: Markdown formats missing in doxygen outputs.albert-github2018-10-021-4/+7
| |/ / | | | | | | | | | | | | | | | Support for strikethrough by means of `~~<text>~~` See also https://help.github.com/articles/basic-writing-and-formatting-syntax/ paragraph about "styling" text".
* | | Bold text terminated by plus signalbert-github2018-10-081-1/+1
|/ / | | | | | | | | No reason to have '+,'-' or '=' with ignore characters. See also: https://stackoverflow.com/questions/52696929/markdown-bold-text
* | Update markdown.cppArmin Müller2018-08-211-1/+1
| |
* | Bug 792373 - Table markdown produces invalid xhtml codealbert-github2018-08-141-5/+3
|/ | | | | <tr class="markdownTableBody" class="markdownTableRowOdd"> The class="markdownTableBody" is not necessary as the "TableRow" part is only emitted for the body, so class="markdownTableBody" has been removed.
* Merge pull request #735 from albert-github/feature/bug_792122_2Dimitri van Heesch2018-06-101-1/+1
|\ | | | | Bug 792122 - XHTML pages are broken several ways (Regression #674)
| * Bug 792122 - XHTML pages are broken several ways (Regression #674)albert-github2018-05-201-1/+1
| | | | | | | | | | The markdown processing of [TOC] was not performed anymore, at the moment of processing there was no g_current. Adding @tableofcontents to the stream (like with images) solves this problem.
* | Bug 792918 - incorrect parsing of markdown tablealbert-github2018-05-291-7/+4
|/ | | | | | | | | Problem due to the fact that for the display of the header line the size of the separator line was used. The headerStart and headerEnd have to be set before the next call to 'findTableColumns' Related to: - pull request 537 Add support for more CSS and column/row spanning in markdown tables - pull request 542 Reverting pull request #537 until it will be fixed - commit on 16/09/2017: New table features mentioned in the documentation were not enabled.
* Wrong determination of begin / end tag of formula in markdown.albert-github2018-04-261-1/+1
| | | | The begin tag for a formula during markdown checking was not determined correctly and thus the end tag was not set and the formula code was interpreted which should not be the case (especially in case of labels with '_' in it were miss interpreted .
* Bug 792122 - XHTML pages are broken several waysalbert-github2018-03-041-1/+3
| | | | | | | | | | | | | | | | | | | The Markdown processing was done after the normal tag processing and splitting the comment in brief, doc, inline. This resulted in that sectioning parts (i.e. e.g. ==== conversion to <h1> ) remained in the brief description whilst similar constructs with HTML commands landed in the doc (details) description. By performing the markdown on the entire comment block this problem has been overcome. commentscan.l - change moment of calling markdown processing - skip start spaces and subsequent empty lines in markdown processed code - small debug correction markdown.cpp - don't convert the dashes in <!-- and --> (HTML type comment) - small debug correction 054 test - update of example for compatibility and adding part about none code result. doxygen.cpp - small textual comment correction
* Misc. typosluz.paz2018-02-061-1/+1
|
* Merge pull request #142 from randomguy3/line-breaksDimitri van Heesch2017-10-241-0/+14
|\ | | | | Implement "double-space line breaks" syntax in Markdown
generated by cgit v0.12 at 2024-10-31 16:27:58 (GMT)