From 4ab73bb872b443ad798be384171c5ff222cb2ba2 Mon Sep 17 00:00:00 2001 From: albert-github Date: Sun, 6 Oct 2019 13:40:14 +0200 Subject: Textual error Correcting textual error --- doc/commands.doc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/commands.doc b/doc/commands.doc index 4e0a6f9..5c6d067 100644 --- a/doc/commands.doc +++ b/doc/commands.doc @@ -2277,8 +2277,8 @@ Commands for displaying examples The `option` `lineno` can be used to enable line numbers for the included code if desired. The `option` `doc` can be used to treat the file as documentation rather than code. - \note Some that when using the `{doc}` option, - commands like \ref cmdcond "\\cond" and \ref cmdif "\\if" don't work with + \note When using the `{doc}` option, + some commands like \ref cmdcond "\\cond" and \ref cmdif "\\if" don't work with this command due to the moment of parsing. \note The included documentation should not have comment signs in it as they will appear @@ -2409,8 +2409,8 @@ Commands for displaying examples The `option` `lineno` can be used to enable line numbers for the included code if desired. The `option` `doc` can be used to treat the file as documentation rather than code. - \note Some that when using the `{doc}` option, - commands like \ref cmdcond "\\cond" and \ref cmdif "\\if" don't work with + \note When using the `{doc}` option, + some commands like \ref cmdcond "\\cond" and \ref cmdif "\\if" don't work with this command due to the moment of parsing. \note The included documentation should not have comment signs in it as they will appear -- cgit v0.12 From 844159503ac32293f1a11761687843b1ecf5fb3e Mon Sep 17 00:00:00 2001 From: albert-github Date: Thu, 21 Nov 2019 13:50:03 +0100 Subject: Correct style in table header in case of paragraph is used In case a paragraph is used in a table header (quite unusual but can happen with 2 lines and an empty line in between), a `

` tag is added and therewith the layout is incorrect. This problem was detected based on #7409 This has been corrected (and tested with some available browsers FF, IE, Chrome, Opera). --- templates/html/doxygen.css | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/templates/html/doxygen.css b/templates/html/doxygen.css index ffba793..2c9dfd5 100644 --- a/templates/html/doxygen.css +++ b/templates/html/doxygen.css @@ -66,6 +66,11 @@ p.startli, p.startdd { margin-top: 2px; } +th p.starttd, p.intertd, p.endtd { + font-size: 100%; + font-weight: 700; +} + p.starttd { margin-top: 0px; } -- cgit v0.12 From e6d4940246e42bedca2c4faa925ddfa2813d7f01 Mon Sep 17 00:00:00 2001 From: albert-github Date: Mon, 25 Nov 2019 10:59:05 +0100 Subject: Adding some links in search documentation The search chapter was missing some links --- doc/extsearch.doc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/extsearch.doc b/doc/extsearch.doc index ead7ea8..e139408 100644 --- a/doc/extsearch.doc +++ b/doc/extsearch.doc @@ -77,7 +77,7 @@ Since we didn't create or install a doxysearch.db it is OK for the test to fail for this reason. How to correct this is discussed in the next section. Before continuing with the next section add the above -URL (without the `?test` part) to the `SEARCHENGINE_URL` tag in +URL (without the `?test` part) to the \ref cfg_searchengine_url "SEARCHENGINE_URL" tag in doxygen's configuration file: SEARCHENGINE_URL = http://yoursite.com/path/to/cgi/doxysearch.cgi @@ -135,7 +135,8 @@ and then copy the resulting `doxysearch.db` to the directory where also The `searchdata.xml` file doesn't contain any absolute paths or links, so how can the search results from multiple projects be linked back to the right documentation set? -This is where the `EXTERNAL_SEARCH_ID` and `EXTRA_SEARCH_MAPPINGS` options come into play. +This is where the \ref cfg_external_search_id "EXTERNAL_SEARCH_ID" and +\ref cfg_extra_search_mappings "EXTRA_SEARCH_MAPPINGS" options come into play. To be able to identify the different projects, one needs to set a unique ID using \ref cfg_external_search_id "EXTERNAL_SEARCH_ID" @@ -168,8 +169,8 @@ and the search results will link to the right documentation set. When you modify the source code, you should re-run doxygen to get up to date documentation again. When using external searching you also need to update the -search index by re-running `doxyindexer`. You could wrap the call to doxygen -and doxyindexer together in a script to make this process easier. +search index by re-running `doxyindexer`. You could wrap the call to `doxygen` +and `doxyindexer` together in a script to make this process easier. \section extsearch_api Programming interface -- cgit v0.12