| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having debug output one expects to have an overview what goes into the markdown processor and comes out of it. For markdown this happens but there can be a small step in front of it (page handling) and than the input is confusing as some processing already took place.
When having a file aa.md:
```
This is a .md file
```
we get with `doxygen -d markdown`:
```
======== Markdown =========
---- input -------
@page md_aa aa\ilinebr This is a .md file
---- output -----
@page md_aa aa\ilinebr This is a .md file
=========
```
whilst it would be less confusing when we have:
```
======== Markdown =========
---- input -------
This is a .md file
---- output -----
@page md_aa aa\ilinebr This is a .md file
=========
```
|
| |\ |
|
| | |
| |
| |
| | |
- stored value was overwritten probably due to compiler optimisation bug
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit changes the following in relation to string use
- The implicit convert from 'QCString' to 'const char *' is removed
- Strings parameters use 'const QCString &' as much as possible in favor
over 'const char *'
- 'if (s)' where s is a QCString has been replaced by 'if(!s.isEmpty())'
- data() now always returns a valid C-string and not a 0-pointer.
- when passing a string 's' to printf and related functions 'qPrint(s)' is
used instead of 's.data()'
- for empty string arguments 'QCString()' is used instead of '0'
- The copy() operation has been removed
- Where possible 'qstrcmp(a,b)==0' has been replaces by 'a==b' and
'qstrcmp(a,b)<0' has been replaced by 'a<b'
- Parameters of string type that were default initialized with '= 0' are
no initialized with '= QCString()'
|
| |/
|
|
|
| |
Especially with commands like `\f$\mbox{\LaTeX}\f$`MathJax has some problem as it is not, yet, able to use the commands `\raise` and `lower` inside the `\mbox` as used in this LaTeX command.
Also switching in and out of math-mode doesn't work as the resulting code either doesn't work in MathJax or in LaTeX, hence the new command s `\f(` and `\f)`.
|
| |
|
|
|
| |
- direct use of std::stringstream and std::ostream gave a 30%
drop in performance.
|
| | |
|
| |
|
|
| |
vice versa
|
| | |
|
| |
|
|
|
| |
- FileInfo is based on ghc::filesystem, a std::filesystem compatible
implementation that does not require C++17.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In case we have in markdown image definition like:
```
```
This would result, besides the image in the text:
```
Image 1""Image 1""Image 1""Image 1""
```
due to the fact that besides the HTML image also the image code for other output formats (latex, rtf, docbook) was written and the double quote was not escaped properly.
|
| |
|
|
| |
Skip block commands.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When having e.g. markdown files like:
```
0.3.1.md
0.3.2.md
```
we get in the treeview twice the item "0" instead of the, more, expected "0.3.1" and "0.3.2".
This is due to the fact that the filename is seen as `0` and the extension `.3.1.md` and `.3.2.md` instead of
filename `0.3.1` and `0.3.2` and extension in both cases `.md`.
The problem was found by Fossies in the Buildbot project.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having the following code:
```
# The page
~~~
ABC
~~~
~~~
DEF
~~~
~~~
GHI ~~~
~~~
JKL~~~
\line17
```
we get the warnings:
```
.../aa.md:16: warning: Found unknown command '\line17'
```
instead of
```
.../aa.md:17: warning: Found unknown command '\line17'
```
The last character of the fenced code block is not handled in the code block.
This problem has been solved (and also checked against the previous examples of #8045 and #8123).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having a simple file like:
```
# The page
# a section
##### a h5 section
\error7
```
we get as warning:
```
.../aa.md:8: warning: Found unknown command '\error7'
```
instead of
```
.../aa.md:7: warning: Found unknown command '\error7'
```
This is due to the fact that the
```
##### a h5 section
```
is translated into:
```
\anchor autotoc_md2
<h5>a h5 section</h5>
```
instead of
```
\anchor autotoc_md2\ilinebr <h5>a h5 section</h5>
```
|
| | |
|
| | |
|
| |
|
|
| |
Replace the respective characters by an underscore.
|
| |\
| |
| | |
issue #8130 Markdown relative links - not working for other folders
|
| | |
| |
| |
| | |
Always convert links to absolute path even when path exists
|
| |/
|
|
| |
see to it that the `\ilinebr` cannot be seen as part of the file name (backslashes can be present as path especially in case of windows).
|
| |\
| |
| | |
Miscounting lines with markdown backtick section
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we have a program like:
```
# test
~~~
npm
~~~
\aa5
~~~
npm ~~~
\aa8
```
we get the warnings like:
```
.../aa.md:6: warning: Found unknown command '\aa5'
.../aa.md:10: warning: Found unknown command '\aa8'
```
instead of:
```
.../aa.md:5: warning: Found unknown command '\aa5'
.../aa.md:8: warning: Found unknown command '\aa8'
```
This has been corrected.
Note: in the example tildes are used so the backticks show up in the github issue as well.
|
| |\ \
| | |
| | | |
Miscounting lines with markdown table
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we have a program like:
```
# Test1
| \aa3 |
| ---- |
| \aa5 |
\aa6
```
we get the warnings like:
```
.../cc.md:3: warning: Found unknown command '\aa3'
.../cc.md:4: warning: Found unknown command '\aa5'
.../cc.md:6: warning: Found unknown command '\aa6'
```
instead of:
```
.../cc.md:4: warning: Found unknown command '\aa3'
.../cc.md:5: warning: Found unknown command '\aa5'
.../cc.md:6: warning: Found unknown command '\aa6'
```
The external counting was correct, not the internal counting.
This has been corrected.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we have a program like:
```
# test
\aa2
> \aa3
\aa4
```
we get the warnings like:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:4: warning: Found unknown command '\aa3'
.../aa.md:6: warning: Found unknown command '\aa4'
```
instead of:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:3: warning: Found unknown command '\aa3'
.../aa.md:4: warning: Found unknown command '\aa4'
```
This has been corrected.
|
| |\
| |
| | |
Miscounting in case of markdown wanted newline due to spaces at end of line
|
| | |
| |
| | |
Added size check
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`\aa2`, `\bb2` and `\ccs2` to give in markdown a newline):
```
First test: 2 extra spaces after first line with error no extra empty lines
\aa2
\aa3
```
and
```
First test: 2 extra spaces after first line with error one extra empty line
\bb2
\bb4
```
and
```
First test: 2 extra spaces after first line with error two extra empty lines
\cc2
\cc5
```
we get warnings like:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:4: warning: Found unknown command '\aa3'
.../bb.md:2: warning: Found unknown command '\bb2'
.../bb.md:5: warning: Found unknown command '\bb4'
.../cc.md:2: warning: Found unknown command '\cc2'
.../cc.md:6: warning: Found unknown command '\cc5'
```
whilst this should be:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:3: warning: Found unknown command '\aa3'
.../bb.md:2: warning: Found unknown command '\bb2'
.../bb.md:4: warning: Found unknown command '\bb4'
.../cc.md:2: warning: Found unknown command '\cc2'
.../cc.md:5: warning: Found unknown command '\cc5'
```
This has been corrected by placing the `<br>` straight after the extra spaces and by not adding an extra newline.
|
| |\ \
| | |
| | | |
Miscounting of line in case of markdown `\ref` image
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case we have:
```
The page
\aa2 Doxygen's Doxygen Documentation: <a href="https://codedocs.xyz/doxygen/doxygen/"><img src="https://codedocs.xyz/doxygen/doxygen.svg"/></a>\aa2
\aa3
\aa4  \aa4
\aa5
\aa9
```
we get the warnings:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:3: warning: Found unknown command '\aa3'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:8: warning: Found unknown command '\aa4'
.../aa.md:9: warning: Found unknown command '\aa5'
.../aa.md:17: warning: Found unknown command '\aa9'
```
instead of the expected
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:3: warning: Found unknown command '\aa3'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:5: warning: Found unknown command '\aa5'
.../aa.md:9: warning: Found unknown command '\aa9'
```
this is due to the fact that the markdown convertor adds some extra line wit `\n` instead of an internal line break `\ilinebr`.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having code like:
```
A horizonal ruler by means of underscores
\aa2
____
\aa4
A horizonal ruler by means of hyphens
\bb7
- ---
\bb9
A horizonal ruler by means of asterisks
\cc12
****
\cc14
```
we get wanungs like:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:5: warning: Found unknown command '\aa4'
.../aa.md:8: warning: Found unknown command '\bb7'
.../aa.md:11: warning: Found unknown command '\bb9'
.../aa.md:14: warning: Found unknown command '\cc12'
.../aa.md:17: warning: Found unknown command '\cc14'
```
instead of
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:7: warning: Found unknown command '\bb7'
.../aa.md:9: warning: Found unknown command '\bb9'
.../aa.md:12: warning: Found unknown command '\cc12'
.../aa.md:14: warning: Found unknown command '\cc14'
```
This has been fixed.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we have simple input files like:
```
Chrome's trace viewer (Catapult) following the
[instructions](
https://chromium.googlesource.com/catapult/+/refs/heads/master/tracing/docs/embedding-trace-viewer.md). This directory contains
the helper files to embed Chrome's trace viewer.
The current resources were generated/copied from
[`Catapult@9508452e18f130c98499cb4c4f1e1efaedee8962`
](
https://chromium.googlesource.com/catapult/+/9508452e18f130c98499cb4c4f1e1efaedee8962).
\aa11
```
or
```
Add new exported module Text.Pandoc.Writers.AnnotatedTable [API change]
(#6655, Christian Despres). This module (which should generally
\bb3
```
one gets (in the current master version, a5ac10888f6c0b0fc00678f67aa49036b33aa4cf):
```
.../aa.md:8: warning: Found unknown command '\aa11'
.../bb.md:3: warning: Found unknown command '\bb4'
```
instead of
```
.../aa.md:11: warning: Found unknown command '\aa11'
.../bb.md:4: warning: Found unknown command '\bb4'
```
this is due to the fact that the newlines inside the links are not taken into consideration during the conversion.
We can add the extra newlines but have to do this inside the `<...>` as than they are handled correctly later on:
- when adding them before the `<` doxygen sees a newline and will start a new paragraph starting with the link instead of keeping it in its place.
- when adding them after the `>` we can get a warning about `warning: End of list marker found without any preceding list items` when after the closing `)` of the link there is directly a `.`
|
| |\
| |
| | |
issue #8078 Warning and extra text when using Markdown as mainpage
|
| | |
| |
| |
| | |
Also replace the `@` in a label.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
* More compact Define test for PRETTY_FUNCTION
* corrected synthax issue
Co-authored-by: ZAMPIERI Armand <armand.zampieri@cmigroupe.com>
|
| |\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_md_pg_cnt
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| |/
|/| |
Miscounting of lines in case of fenced code block
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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".
|
| |/ |
|
