| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Doxygen test 54, when generating LaTeX / PDF, gave the error message:
Runaway argument?
Second paragraph of the param description. \end {DoxyVerb} \\ \hline \ETC.
! Paragraph ended before \verbatim@ was complete.
<to be read again>
\par
l.41 \end{DoxyParams}
The tabu package documentation (and Stack Exchange LaTeX) give some hints in to the problem about the verbatim command in the different environments and has been implemented here for the longtabu table.
|
| |\
| |
| | |
-Fixed: some of remained work to support RTL in HTML output
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
- Fixed: fragment lines overlap floating elements in html
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
HTML output
|
| |\ \
| | |
| | | |
Changed the navtree collapsed list icon to be more symmetric to the expanded list icon
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Full support for strong and typed enums in the XML output
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
There's a new boolean `strong` attribute on the `<memberdef>` element
that defines whether the enum is a classic or a strong one.
Tests were updated to verify both cases.
|
| |\ \ \
| | | |
| | | | |
Expose TOC placeholder in XML output
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently the XML output for a page was generated the same
independently of whether the \tableofcontents command was present in
the page source or not. Because of that, the users of the XML output
had no chance of knowing whether given page should have a TOC or not.
There's now a new <tableofcontents> element that gets added in case
the TOC was requested. As it is trivial to populate the TOC on user
side by simply enumerating the <sectN> elements, the element is empty
and acts just as a boolean.
|
| |\ \ \
| | | |
| | | | |
Encode invalid XML characters instead of skipping them
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The <sp> element in <programlisting> has a new optional attribute
`value`, which contains value of given invalid ASCII character. In
case of space, the `value` attribute is omitted.
Use cases for this: including snippets of *very esoteric* languages,
markup that makes use of the advanced ASCII formatting characters or
for example highlighting a console output containing ANSI color codes
(which is my case, in fact).
Regarding backwards compatibility -- as files with such ASCII
characters are very rare, I don't expect this minor difference in the
output to be a problem. Besides that, such ASCII characters are often
replaced by a space in many applications anyway.
A test snippet was extended to contain a special character so this
difference in behavior could be verified.
|
| |/ /
| |
| |
| |
| | |
Super trivial typos
Some are in qtools/ which I know is a 3rd party dependency but as we know is now obsolete upstream. I reckon it wouldn't be much of an issue to merge neverthless
Tacked on several more commits
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is based on work done in 141dbfd5a4f79c98da14a1b414c6db4e1b34618b
through ed9acb6e1bb81a2eec334180f7b8c1bf0598b444 and makes a few
behavioral changes to it.
There's a new attribute called `filename` and the `language` was removed,
because it could provide misleading information. This allows for more
flexibility on the user side. In particular:
* For historical reasons, `*.txt` files are marked by Doxygen as C++
(see https://bugzilla.gnome.org/show_bug.cgi?id=760836 for details).
In particular, code snippet included from a CMakeLists.txt file would
be marked and highlighted as C++. So in this case, the language
attribute would be very misleading.
* Doxygen is aware only of a very small subset of languages and thus a
lot of information can be lost when relying on its
extension-to-language-name conversion -- in particular, all
extensions that are not recognized are assumed to be C++. On the other
hand, putting more effort into its language detection algorithms is
not worth the time, as there will always be new languages that fail to
detect. So let's leave that on the user of the XML output instead.
* Using just file extension is not enough, it has to be a full filename.
For example, `*.txt` can be either a plain text file or a
`CMakeLists.txt`.
* The path is not stripped from the filename, as it also may contain
additional information that helps to detect the language better.
In addition to that, filenames of code snippets included via the \include
command and related are propagated to the <programlisting> element as
well.
With this change, (1) code snippets using simply
\code
some code
\endcode
will not produce any `filename` attribute and it's up to the user what to
do -- assume C++, detect language from contents or not highlight
anything.
<programlisting>
some code
</programlisting>
(2) Code snippets using
\code{.cmake}
some code
\endcode
will produce the following:
<programlisting filename=".cmake">
some code
</programlisting>
(3) And finally, \include, \dontinclude and related \skip, \skipline etc.
commands
\include path/to/some-file.py
will produce
<programlisting filename="path/to/some-file.py">
some code
</programlisting>
The tests were updated to check all three cases.
On the user side, when using Pygments for example, it's then just a
matter of calling pygments.lexers.find_lexer_class_for_filename() with
value of the `filename` attribute value and optionally also the code
snippet for additional language analysis.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
add language attribute (optional) to listingType
Changes to be committed:
modified: templates/xml/compound.xsd
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Marking the resulting JS in this way ensures that visitors to the
resulting HTML documentation do not have to choose between running
non-free JS and experiencing the HTML documentation as it was
intended.
The JS was already freely licensed, so this change just
ensures that the appropriate labelling occurs so that GNU LibreJS [0]
parses the JS correctly as freely licensed.
[0] https://www.gnu.org/software/librejs/
Signed-off-by: zachwick <zach@zachwick.com>
|
| | |
|
| |\
| |
| | |
Bug 774138 - Please add HTML classes to "Definition at..." & "Referenced by..." for CSS
|
| | |
| |
| |
| |
| |
| |
| | |
by..." for CSS
Added class= to html output for "Definition at..." resulting in p.definition in the css file and for "Referenced by .. " and "References ..." resulting in p.definition in css file.
(also corrected some error messages).
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
| |
in PDF output Data Fields
|
| | |
|
| |\
| |
| | |
New classes for generated HTML div elements.
|
| | |
| |
| |
| | |
Dot, Msc and Plantuml have their own classes for the generated div element.
|
| |/
|
|
| |
Documentation section
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
Added missing semicolon in navtree,css
|
| |/
|
|
| |
Android OS
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Make the line number not selected by user.
The user case is when you want to copy the raw source code content, you would not want to automatically select the line number.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
resulting in vulnerability
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In case an image is included in a table and this image has a caption the generation of a PDF stops with the message:
! Misplaced \noalign.
\caption ->\noalign
\bgroup \@ifnextchar [{\egroup \LT@c@ption \@firstofone ...
l.45 \end{longtabu}
This problem has in general been described in: http://tex.stackexchange.com/questions/85919/adding-a-caption-to-a-graphic-inside-a-longtable
In this patch the suggestion from this reference is implemented by defining \doxyfigcaption and using this where a caption is required.
|
| | |
|
