| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
with no extension
Better handling of the determination of what is an extension.
- don't see a file references like: `./LICENSE` as extension
- use the qt way of extension determination and in case of no extension use the no extension placeholder for it.
|
|
|
|
| |
For an URL also the percentage (`%`)sign has to be escaped
|
| |
|
|\
| |
| | |
issue #7033 Syntax highlighting doesn't work when calling \dontinclude from Markdown files
|
| |
| |
| |
| |
| |
| | |
Markdown files
Don't use the file name extension of the including file but of the included file. In case of no included filename or no extension, fall back of the file extension of the including file.
|
|\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_case_sense
|
| | |
| | |
| | |
| | | |
In case special characters in a filename need escaping into something like: `_0` the `0` should not be followed by an uppercase character as this would be in contradiction wit the setting `CASE_SENSE_NAMES=NO`.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we have a construct like:
```
template <typename Element, size_t N>
class StlContainerView<Element[N]> {
public:
typedef internal::NativeArray<RawElement> type;
};
```
this will lead to files with `[` and `]` in it, as such not nice, but it is used in ids inside the code as well like:
```
id="aclass_stl_container_view_3_01_element[_n]_4_html_a1bf60158ff15896f2b53af11c09524fb"
```
running
```
xmllint --path ..../testing/dtd --noout --nonet --postvalid html_org/*html
```
this leads to the message:
```
Syntax of value for attribute id of div is not valid
Document html_org/test_8h_source.html does not validate
```
escaping the `[` and `]` as done with other special characters solves this problem
|
|/
|
|
|
| |
Cygwin should by default also have `CASE_SENS_NAMES=NO` like is the case for the underlying Windows.
In case of Cygwin the define `_WIN32` is not set so we also have to test for `__CYGWIN__`
|
|\
| |
| | |
Markdown file as internet link
|
| |
| |
| |
| |
| |
| |
| |
| | |
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)
```
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
issue #6917 Crash in php with UTF-8 character
|
| |/
| |
| |
| |
| |
| | |
Problem is that a value is fed to isspace that is not in the correct range and has to be converted to this range.
compare also Assertion failure generation documentation (fdefe70a955c8140f080974319bbf97364d3e610 of March 30 2016).
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
In case in code 2 consecutive minus signs are present they are shown as endash.
using the same code as in the non code part solves the issue.
Issue can e.g. be seen in cpp source code (with e.g. i--) and in the doxygen documentation in the paragraph "Comment blocks in VHDL"
This is a regression in 1.8.15
|
|/ |
|
|
|
|
| |
After small discussion conclusion was better to remove the obsolete `doxygen=`
|
|
|
|
| |
operators in 1.8.15
|
| |
|
|
|
|
| |
An empty string was defined in a `<a href="">` resulting in a null pointer access.
|
|
|
|
| |
Convert name / url based on HTML / XML conventions and don't do double conversions (XML).
|
| |
|
| |
|
| |
|
|
|
|
| |
bisect] (Origin: bugzilla #791942)
|
| |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Add commands to handle referenced by relation and references relation
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Analogous to call graph and caller graph this patch provides an implementation for the referenced by relation and references relation.
Providing the commands:
- referencedbyrelation
- hidereferencedbyrelation
- referencesrelation
- hidereferencesrelation
Motivation is that some lists can get extremely large and also there is now more symmetry between the textual and graphical out.
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | | |
Not only the documentation, but also the (x)refitems.
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_latex_index_sorting
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In case of LaTeX the sorting was so that lowercase came after uppercase e.g.: `username` came after `useSsl`, although the index should be case insensitive.
Te problem was that the sort key was filtered in such a way that a.o. uppercase symbols were preceded by `\+` for hyphenation. The key doesn't need this hyphenation (as there is a separate field for the display name).
The `\+` has been filtered out now.
|
| |\ \ \
| | |_|/
| |/| | |
Issue_6456 Using # in links causes errors in PDF generation
|
| | |/
| | |
| | |
| | |
| | | |
- The # sign in an URL needs to be escaped as longtabu reads the table body as the argument to a command, so the self-escaping mechanism of \href cannot work (from https://tex.stackexchange.com/questions/447461/having-a-hash-sign-in-href-in-a-longtabu-cell)
- a regression regarding the change from `\tt` to `\texttt` (needed `{ ... }` as `\href` has 2 arguments )
|
|/ /
| |
| |
| | |
Added a Slice-optimized output mode.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Till now docbook had its own output generator, but lot of possibilities were missing (see remark about updating below), with this patch the (more than) basic implementation has been made.
Added some docbook tests to the current tests and updated documentation where necessary
Tried updating current version but too many issues remained that were generically handled in the standard generator, code is in current version behind '#if 0' construct in doxygen.cpp and name with '_v1' and in docbookgen.cp'
|
|\ \
| | |
| | | |
Correct typing error in warning message.
|
| | | |
|
| |/
|/| |
|
|/
|
|
|
|
|
|
|
|
| |
Based on the travis messages (in total 4):
/home/travis/build/doxygen/doxygen/src/util.cpp:7952:20: warning: comparison of
constant -1 with expression of type 'char' is always false
[-Wtautological-constant-out-of-range-compare]
((inBuf.at(0)==-1 && inBuf.at(1)==-2) || // Little endian BOM
~~~~~~~~~~~^ ~~
and subsequent tests, the automatic detection of the UCS-2 BOM failed, this has been corected.
|
|
|
|
|
|
| |
- In case a corrupted character is found LaTeX shows this as a U+FFFD , the character in the code is 0xef 0xbf oxbd. This character was in the LaTex Code already replaced with `\ucr` but this didn't work properly with TexLive 2015 and the code is now detected i the doxygen code and directly replaced `\ucr`
- other special characters are now handled, in a way that works in all engines, by means of `\newunicodechar`
- the size of the `\ucr` was not set in case it was used in 'running text' and not inside e.g. a code section.
|
|\
| |
| | |
Small problems when having code in LaTeX output
|