doxygen-develop Mailing List for Doxygen (Page 7)
Brought to you by:
dimitri
Menu
▾
▴
doxygen-develop — List for discussing new features, submitting patches, etc.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(4) |
Jul
(29) |
Aug
(8) |
Sep
(8) |
Oct
(17) |
Nov
(34) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(20) |
Feb
(14) |
Mar
(11) |
Apr
(9) |
May
(8) |
Jun
(7) |
Jul
(25) |
Aug
(12) |
Sep
(12) |
Oct
(24) |
Nov
(27) |
Dec
(12) |
| 2003 |
Jan
(12) |
Feb
(14) |
Mar
(15) |
Apr
(11) |
May
(17) |
Jun
(20) |
Jul
(32) |
Aug
(13) |
Sep
(34) |
Oct
(12) |
Nov
(16) |
Dec
(33) |
| 2004 |
Jan
(20) |
Feb
(6) |
Mar
(20) |
Apr
(15) |
May
(16) |
Jun
(28) |
Jul
(7) |
Aug
(7) |
Sep
(17) |
Oct
(16) |
Nov
(17) |
Dec
(43) |
| 2005 |
Jan
(15) |
Feb
(5) |
Mar
(14) |
Apr
(4) |
May
(3) |
Jun
(8) |
Jul
(17) |
Aug
(16) |
Sep
(7) |
Oct
(17) |
Nov
(1) |
Dec
(7) |
| 2006 |
Jan
(7) |
Feb
(6) |
Mar
(10) |
Apr
(6) |
May
(3) |
Jun
(4) |
Jul
(3) |
Aug
(3) |
Sep
(18) |
Oct
(11) |
Nov
(10) |
Dec
(3) |
| 2007 |
Jan
(12) |
Feb
(12) |
Mar
(23) |
Apr
(5) |
May
(13) |
Jun
(6) |
Jul
(5) |
Aug
(4) |
Sep
(8) |
Oct
(10) |
Nov
(6) |
Dec
(7) |
| 2008 |
Jan
(7) |
Feb
(13) |
Mar
(35) |
Apr
(14) |
May
(13) |
Jun
(4) |
Jul
(9) |
Aug
(6) |
Sep
(12) |
Oct
(9) |
Nov
(6) |
Dec
(3) |
| 2009 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(15) |
May
(1) |
Jun
(2) |
Jul
(7) |
Aug
(3) |
Sep
(4) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2010 |
Jan
(4) |
Feb
|
Mar
(5) |
Apr
(1) |
May
(5) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(11) |
Oct
(2) |
Nov
(1) |
Dec
(5) |
| 2011 |
Jan
(12) |
Feb
(3) |
Mar
(28) |
Apr
(4) |
May
(3) |
Jun
(4) |
Jul
(15) |
Aug
(12) |
Sep
(2) |
Oct
(3) |
Nov
(6) |
Dec
(3) |
| 2012 |
Jan
(1) |
Feb
(4) |
Mar
(9) |
Apr
(5) |
May
(6) |
Jun
(6) |
Jul
(3) |
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(9) |
Dec
(7) |
| 2013 |
Jan
(8) |
Feb
(14) |
Mar
(15) |
Apr
(21) |
May
(29) |
Jun
(34) |
Jul
(3) |
Aug
(7) |
Sep
(13) |
Oct
(1) |
Nov
(3) |
Dec
(5) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(2) |
Jun
(4) |
Jul
(2) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(2) |
| 2015 |
Jan
(7) |
Feb
(4) |
Mar
(3) |
Apr
(15) |
May
(4) |
Jun
(9) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
(3) |
Dec
(7) |
| 2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(9) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(5) |
| 2018 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
(7) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2021 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Markus G. <mg...@we...> - 2014-04-09 17:35:03
|
Hi, The attached patch fixes a bug in generating references to subpages (and potentially also other items) in the LaTeX output when PDF_HYPERLINKS is set to NO. I also included a minimal example. Cheers, Markus |
|
From: Phil M. <phi...@br...> - 2014-04-09 14:07:15
|
Hi,
When I run doxygen built from git head on some of my source the resulting html has meta tags that are not properly closed (and fail to pass the w3c validator as a result). The following is a sample of the html output (from html/search/all_0.html):
<html><head><title></title>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta name="generator" content="Doxygen 1.8.6">
Note that the second meta tag is not properly closed (and as the doctype of this file is XHTML it needs to be).
This trivial patch resolves this issue:
diff --git a/src/searchindex.cpp b/src/searchindex.cpp
index 7aa8216..a550eb1 100644
--- a/src/searchindex.cpp
+++ b/src/searchindex.cpp
@@ -1027,7 +1027,7 @@ void writeJavascriptSearchIndex()
" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">" << endl;
t << "<html><head><title></title>" << endl;
t << "<meta http-equiv=\"Content-Type\" content=\"text/xhtml;charset=UTF-8\"/>" << endl;
- t << "<meta name=\"generator\" content=\"Doxygen " << versionString << "\">" << endl;
+ t << "<meta name=\"generator\" content=\"Doxygen " << versionString << "\"/>" << endl;
t << "<link rel=\"stylesheet\" type=\"text/css\" href=\"search.css\"/>" << endl;
t << "<script type=\"text/javascript\" src=\"" << baseName << ".js\"></script>" << endl;
t << "<script type=\"text/javascript\" src=\"search.js\"></script>" << endl;
Hope this is useful
Regards
Phil
|
|
From: Ross R. <ros...@gm...> - 2013-12-19 19:38:56
|
Hello, Regarding the ancient thread http://sourceforge.net/mailarchive/message.php?msg_id=3321410 , was ditaa ever integrated into doxygen or is there a generalized mechanism for doing external text->image processing? - Ross |
|
From: mkk <mk...@gm...> - 2013-12-18 19:55:25
|
see http://plantuml.sourceforge.net/doxygen.html -- View this message in context: http://doxygen.10944.n7.nabble.com/Doxygen-VHDL-tp6240p6409.html Sent from the Doxygen - Development mailing list archive at Nabble.com. |
|
From: Dimitri v. H. <do...@gm...> - 2013-12-17 20:32:15
|
Hi David, On 17 Dec 2013, at 20:20 , David Binderman <dc...@ho...> wrote: > Hello there, > > I just ran the static analyser "cppcheck" over the source > code of doxygen-1.8.5. It said many things, including > > [doxygen.cpp:3572]: (warning) Logical conjunction always evaluates to false: EXPR != -1 && EXPR == -1. > > Source code is > > if (md->getStartBodyLine()!=-1 && md->getStartBodyLine()==-1) > > Suggest code rework. Thanks, I've push this change to GitHub to fix it: https://github.com/doxygen/doxygen/commit/585efafb18dbdc371a46063cbeb272e5bb292628 > > The analyser also said > > [fortranscanner.cpp:1307]: (style) Array index 'i' is used before limits check. > [markdown.cpp:541]: (style) Array index 'i' is used before limits check. > [markdown.cpp:1317]: (style) Array index 'i' is used before limits check. > [markdown.cpp:1323]: (style) Array index 'i' is used before limits check. > > which may also be worth fixing. These appeared to be false positives, all concern an array 'a' with size 's', where the check has the form: if (i<s) { ... if (a[i]==x && i<s-1 && a[i+1]==y) { ... } } cppcheck apparently doesn't see the first guard and is triggered by the second guard, which makes use of the fact that && is evaluated conditionally. Regards, Dimitri |
|
From: David B. <dc...@ho...> - 2013-12-17 19:20:31
|
Hello there, I just ran the static analyser "cppcheck" over the source code of doxygen-1.8.5. It said many things, including [doxygen.cpp:3572]: (warning) Logical conjunction always evaluates to false: EXPR != -1 && EXPR == -1. Source code is if (md->getStartBodyLine()!=-1 && md->getStartBodyLine()==-1) Suggest code rework. The analyser also said [fortranscanner.cpp:1307]: (style) Array index 'i' is used before limits check. [markdown.cpp:541]: (style) Array index 'i' is used before limits check. [markdown.cpp:1317]: (style) Array index 'i' is used before limits check. [markdown.cpp:1323]: (style) Array index 'i' is used before limits check. which may also be worth fixing. Regards David Binderman |
|
From: Szabolcs P. <sz...@sz...> - 2013-12-11 02:09:01
|
Hello Everyone, Just wanted to give a heads up that on page http://www.stack.nl/~dimitri/doxygen/helpers.html at the end of section JavaScript, the link to Xie Wenjie's approach is broken. Cheers, Szasza |
|
From: Tom G. <tom...@ex...> - 2013-11-04 10:33:30
|
Hi all, I filed this as BUG 711387 ( https://bugzilla.gnome.org/show_bug.cgi?id=711387 ) With best regards, Tom. On ma, 2013-11-04 at 10:15 +0100, Tom Ghyselinck wrote: > Hi all, > > There is a bug in doxygen-1.8.5 with TCL classes with a dot in their > name. > > When we want to use \link to these members, the resolution of the name > fails. > > This is due to the fact that the any dot in a name is subsituted by > '::' as > if it was a scope separator. > This is very suitable and convenient for C++ / Java / etc., where a > dot > in function names and class members is not allowed, > but TCL does allow a dot in function names. > > I wrote a (quick and (maybe not so) dirty) patch for doxygen-1.8.5. > > The function resolveRef in util.h/util.c now has an additional > argument dotIsScopeSeparator. When this is set to FALSE, > a 'dot' in the reference name won't be translated to '::'. > > For compatibility, it defaults to TRUE. > The Q&D part now exists in the fact that, the rest of the code > still uses the compatible call. The function itself tries to resolve > with dotIsScopeSeparator = FALSE when resolving with > dotIsScopeSeparator = TRUE fails. > > I added a simple test project with several links as suggested by > http://www.stack.nl/~dimitri/doxygen/manual/autolink.html > > With best regards, > Tom. > > > -- ________________________________________________________________________ | tom...@ex... | | Tom Ghyselinck | Senior Engineer | Excentis N.V. | Gildestraat 8 B-9000 Ghent, Belgium | Tel: +32 9 269 22 91 - Fax: +32 9 329 31 74 ________________________________________________________________________ |
|
From: Tom G. <tom...@ex...> - 2013-11-04 10:25:58
|
Hi all, I filed this as bug report 711386 https://bugzilla.gnome.org/show_bug.cgi?id=711386 With best regards, Tom. On ma, 2013-11-04 at 09:03 +0100, Tom Ghyselinck wrote: > Hi all, > > We have a special use case of doxygen: > > 1. We have TCL classes which are implemented in C++. > To generate the documentation, we create a "dummy" (TCL) source file > (api.tcl) > which just defines the class and the methods (with their arguments) > without implementation. > > During documentation generation, the source code in the file is > filtered out > Doxyfile: > > FILTER_SOURCE_FILES = YES > FILTER_SOURCE_PATTERNS = *api.tcl="api_source_filter.sh" > > with api_source_filter.sh being an empty file. > > This source code is not desired in our doxygen files listing output, > nor do we want any link to the "filtered-out" source code. > > > This would work great if we have SOURCE_BROWSER = NO in our Doxyfile, > but: > > 2. We also provide documentation for wrapper scripts for our TCL API. > This part includes (open-source) scripts and tools to ease the use of > our API (described in 1.). > This documentation is listed in the Files section of doxygen. So we > explicitly need > SOURCE_BROWSER = YES in order to make this work. > > > Another option is to split up the documentation it 2 parts, but: > > 3. There are some restrictions to do this: > > * The API and TCL wrapper scripts refer to each other > * We also have example pages which refer to the API and > wrapper and vice versa. > > So the documentation MUST be in one Doxygen project. > > > To remove the linking to the source file in classes and class members, > we created a patch for doxygen 1.8.5 release (see attachment). > It can be controlled by the SOURCE_DEFINITION configuration item. > Linking to the source is still enabled by default. > > Note that our patch does not remove the links to source code > for documentation in the Files section! > > Any comments or other suggestions for our change are very welcome! > > If there are any other suggestions for our flexible documentation, > please let us know! > > With best regards, > Tom. > > > -- ________________________________________________________________________ | tom...@ex... | | Tom Ghyselinck | Senior Engineer | Excentis N.V. | Gildestraat 8 B-9000 Ghent, Belgium | Tel: +32 9 269 22 91 - Fax: +32 9 329 31 74 ________________________________________________________________________ |
|
From: Markus G. <mg...@we...> - 2013-10-02 10:51:17
|
Hi, please find two patches attached regarding the definition of ALIASES. The first one simply fixes a typo in an error message. The second patch implements escaping of commands using the \-syntax in the value part of ALIASES. Rationale: So far, there was no way to disambiguate a forced newline (via '\n') from a command using the \-syntax starting with 'n'. While special handling was implemented for some internal commands, self-defined commands or LaTeX commands inside a \latexonly environment were not recognized. For example, it was impossible to properly define a command inserting a newline followed by a page break only for the LaTeX output, as the '\newpage' in newpage="\latexonly\n\newpage\endlatexonly" was recognized as '\n' followed by the text 'ewpage'. Proposed solution: The attached patch implements C-style escaping for the value part of ALIASES. That is, '\n' inserts a newline, '\"' a quote character, '\\' a backslash, and '\<num>' expands the corresponding argment. The aforementioned command can therefore now be defined as either newpage="\\latexonly\n\\newpage\\endlatexonly" or newpage"@latexonly\n\\newpage@endlatexonly" While this solution is admittedly not backwards-compatible, it is IMO preferable over only escaping '\n's as it provides a consistent escaping scheme that is easy to remember. Cheers, Markus |
|
From: Markus G. <mg...@we...> - 2013-09-30 14:54:23
|
Hi, Today I noticed that the '@ref' command is not working as documented. Here is a quote from the docs: For LaTeX documentation the reference command will generate a section number for sections or the text followed by a page number if <name> refers to an anchor. However, all versions of doxygen I tried (1.7.1, 1.7.3, 1.8.4, git) *always* generated a link using the name of the section/page instead of a numbered reference. Please find a simple example to reproduce this behavior attached. I attempted to fix this by messing around in the visitPre(DocRef*) method of LatexDocVisitor, but everything I tried led to some ill side effects, i.e., there seems to be something more required. Any help would be appreciated. Thanks, Markus |
|
From: Jan D. <jan...@gm...> - 2013-09-30 05:09:45
|
On 9/29/13 9:39 PM, Dimitri van Heesch wrote: >> Feedback wanted: https://bugzilla.gnome.org/show_bug.cgi?id=707713 >> >> What is the preferred way for receiving enhancement patches -- via >> bugzilla, using github .. or other ..? > > Either bugzilla with attached patch or a github pull request are fine methods. > Github has a slight preference as it makes it easier to update the patch. Noted for future reference. > I haven't gotten around to try you patch and investigate if it makes sense to > have the \diafile command in doxygen (as opposed to having to add the dia->png conversion in a > batch file together with running doxygen). That's fair. For historical context, note that I added the dia-support to get away from generating png's and eps's during the build stage for the documentation; it was causing some annoyances (inconsistently updated platform-specific scripts, where to put generated files on various platforms/systems, and such). As you imply; the diafile support is not a "missing feature" as much as it's scratching an annoying itch. /Jan |
|
From: Dimitri v. H. <do...@gm...> - 2013-09-29 19:39:41
|
Hi Jan, On Sep 29, 2013, at 11:47 , Jan Danielsson <jan...@gm...> wrote: > Hello, > > Feedback wanted: https://bugzilla.gnome.org/show_bug.cgi?id=707713 > > What is the preferred way for receiving enhancement patches -- via > bugzilla, using github .. or other ..? Either bugzilla with attached patch or a github pull request are fine methods. Github has a slight preference as it makes it easier to update the patch. I haven't gotten around to try you patch and investigate if it makes sense to have the \diafile command in doxygen (as opposed to having to add the dia->png conversion in a batch file together with running doxygen). Regards, Dimitri |
|
From: Jan D. <jan...@gm...> - 2013-09-29 09:47:39
|
Hello, Feedback wanted: https://bugzilla.gnome.org/show_bug.cgi?id=707713 What is the preferred way for receiving enhancement patches -- via bugzilla, using github .. or other ..? -- Kind regards, Jan Danielsson |
|
From: Dimitri v. H. <do...@gm...> - 2013-09-28 10:53:39
|
On Sep 28, 2013, at 12:14 , Markus Geimer <mg...@we...> wrote: > Hi folks, > > Please find a small patch attached addressing some inconsistencies > with the index and bibliography ToC entries in generated LaTeX > output. Thanks, I'll include it in the next git update. Regards, Dimitri |
|
From: Markus G. <mg...@we...> - 2013-09-28 10:14:34
|
Hi folks, Please find a small patch attached addressing some inconsistencies with the index and bibliography ToC entries in generated LaTeX output. Cheers, Markus |
|
From: <Eck...@t-...> - 2013-09-16 16:13:01
|
Hello Everybody. After 4 years of refactoring the first milestone having the next major release of Moritz the nassi-shneiderman generator for Doxygen is nearly reached. The completely new developed Moritz2 presents with the demo-version 8 its first release-candidate (under https://www.moritz.sourceforge.net or https://www.sourceforge.net/projects/moritz/ use "Browse All Files"). Most of the features already known from the older Moritz1 are still available: 1. Generation of Nassi-Shneiderman diagrams based on HTML. 2. Control of the diagrams by using special commands inside of comments. Furthermore new features are available: 1.Generation of uml-like activity-diagrams based on dot( http://www.graphviz.org ). 2.Support of more programming-languages (C/Cpp, Python, Matlab, Pascal) Another new feature is an own parser. Thus Moritz can be used independently from other tools to generate its output. Furthermore the xml-output created by the parser represents the parser-tree of the source in other words the algorithm and not the document-structure. The new release contains one windows-distribution and one linux-distribution together with documentation-files (please use "Browse All Files" and ignore the download-proposal). To use Moritz for different source projects an user-project is available, that contains only the needed output-folders and templates for the basic configurations. It should be copied near to the source-project and combined with the distribution (please refer the page User-Project of the documentation) If you want to build the binaries (abc2xml and xml2abc) by your self, you will find the sources of xml2abc in the current release of Moritz and the sources of abc2xml in the current release of its partner-project MuLanPa (under https://www.mulanpa.sourceforge.net or https://www.sourceforge.net/projects/mulanpa/ ) If you have questions or doubts you will find in both projects forum-places: Source-Parser: Discussion: https://sourceforge.net/p/mulanpa/discussion/ Bugs: https://sourceforge.net/p/mulanpa/tickets/ Diagram-Generator: Discussion: https://sourceforge.net/p/moritz/discussion/ Bugs: https://sourceforge.net/p/moritz/bugs/ Even the development has reached a nearly stable point this means not that it is perfect. Thus please don't hesitate to use the forum. Best Regards, Eckard Klotz. |
|
From: Jan D. <jan...@gm...> - 2013-09-11 11:48:13
|
Hello, We use mscgen, dot and dia for generating/drawing graphs for documentation. Doxygen can use mscgen and dot files directly, so for dia we've been manually exporting bitmaps and eps files. It was fun the first 43957395 times, but I started getting tired of it, so I added a \diafile keyword to doxygen. The patch is available at: https://bugzilla.gnome.org/show_bug.cgi?id=707713 Feedback wanted. For some reason the pre-built Mac OS X version of dia won't accept command line arguments. I built dia from pkgsrc so I could use \diafile on my Mac as well. /Jan |
|
From: Markus G. <mg...@we...> - 2013-09-08 16:40:34
|
Hi all, For some time, doxygen inserts additional hyphenation points before each uppercase letter in it's LaTeX output. While this makes sense for identifiers in CamelCase, for descriptions with "normal text" using names such as OpenMP, OpenGL or the like this is typically not what one wants and can lead to surprising results (besides the fact that the inserted '\-' suppresses hyphenation at all other places). Therefore I was wondering whether this behavior could be restricted to identifiers only. What do you think? Markus |
|
From: Trond D. <tro...@no...> - 2013-09-05 07:13:09
|
Nice. This solved my issue. Thank you for your support! 2013/9/3 Dimitri van Heesch <do...@gm...> > > On Sep 3, 2013, at 9:03 , Trond Danielsen <tro...@no...> > wrote: > > > Hi, > > > > do you have a copy of this patch or a branch on Github for others to try? > > The patch has been pushed to GitHub now. > > Regards, > Dimitri > > -- Trond Danielsen <tro...@no...> Project Engineer Norbit Subsea AS <http://www.norbit.no> +47 404 94 711 Email written on eco-friendly reusable memory |
|
From: Dimitri v. H. <do...@gm...> - 2013-09-03 19:05:01
|
On Sep 3, 2013, at 9:03 , Trond Danielsen <tro...@no...> wrote: > Hi, > > do you have a copy of this patch or a branch on Github for others to try? The patch has been pushed to GitHub now. Regards, Dimitri |
|
From: Trond D. <tro...@no...> - 2013-09-03 07:03:36
|
Hi, do you have a copy of this patch or a branch on Github for others to try? 2013/9/2 mkk <mk...@gm...> > I posted Dimitri a patch for this bug. > Try the next GIT update. > > > > -- > View this message in context: > http://doxygen.10944.n7.nabble.com/VHDL-2008-and-arrays-on-unconstrained-elements-tp6236p6241.html > Sent from the Doxygen - Development mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > -- Trond Danielsen <tro...@no...> Project Engineer Norbit Subsea AS <http://www.norbit.no> +47 404 94 711 Email written on eco-friendly reusable memory |
|
From: mkk <mk...@gm...> - 2013-09-02 16:55:26
|
I posted Dimitri a patch for this bug. Try the next GIT update. -- View this message in context: http://doxygen.10944.n7.nabble.com/VHDL-2008-and-arrays-on-unconstrained-elements-tp6236p6241.html Sent from the Doxygen - Development mailing list archive at Nabble.com. |
|
From: Brilliantov K. V. <bri...@by...> - 2013-08-30 07:12:16
|
Hello! Doxygen 1.8.5, revision d65f3313739177d4d8ce27f607edf9517dc66de3 not ok 12 - [012_cite.dox]: test the \cite command # Failed test '[012_cite.dox]: test the \cite command' # at runtests.pl line 249. # Difference between generated output and reference: # --- test_output_012/indexpage.xml 2013-08-30 11:05:50.879745956 +0400 # +++ 012/indexpage.xml 2013-08-30 11:03:43.500761137 +0400 # @@ -4,7 +4,7 @@ # <compoundname>index</compoundname> # <title>My Project</title> # <detaileddescription> # - <para>See <ref refid="citelist_1CITEREF_knuth79" kindref="member">knuth79</ref> for more info. </para> # + <para>See <ref refid="citelist_1CITEREF_knuth79" kindref="member">[1]</ref> for more info. </para> # </detaileddescription> # </compounddef> # </doxygen> After change testing/012/indexpage.xml error in citelist.xml: not ok 12 - [012_cite.dox]: test the \cite command # Failed test '[012_cite.dox]: test the \cite command' # at runtests.pl line 249. # Difference between generated output and reference: # --- test_output_012/citelist.xml 2013-08-30 11:10:14.208843783 +0400 # +++ 012/citelist.xml 2013-08-29 14:14:02.035699978 +0400 # @@ -4,6 +4,17 @@ # <compoundname>citelist</compoundname> # <title>Bibliographic References</title> # <detaileddescription> # + <para> # + <variablelist> # + <varlistentry> # + <term><anchor id="_1CITEREF_knuth79"/>[1]</term> # + </varlistentry> # + <listitem> # + <para>Donald<nonbreakablespace/>E. Knuth. <emphasis>Tex and Metafont, New Directions in Typesetting</emphasis>. American Mathematical Society and Digital Press, Stanford, 1979.</para> # + <para/> # + </listitem> # + </variablelist> # + </para> # </detaileddescription> # </compounddef> # </doxygen> -- Best regards, Brilliantov Kirill Vladimirovich |
|
From: Brilliantov K. V. <bri...@by...> - 2013-08-29 12:30:03
|
Signed-off-by: Brilliantov Kirill Vladimirovich <bri...@by...>
---
src/translator_ru.h | 177 ++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 176 insertions(+), 1 deletion(-)
diff --git a/src/translator_ru.h b/src/translator_ru.h
index 7bd40f1..ada8142 100644
--- a/src/translator_ru.h
+++ b/src/translator_ru.h
@@ -26,7 +26,7 @@
#ifndef TRANSLATOR_RU_H
#define TRANSLATOR_RU_H
-class TranslatorRussian : public TranslatorAdapter_1_7_5
+class TranslatorRussian : public Translator
{
public:
/*! Used for identification of the language. */
@@ -1794,6 +1794,181 @@ class TranslatorRussian : public TranslatorAdapter_1_7_5
}
return sdate;
}
+
+//////////////////////////////////////////////////////////////////////////
+// new since 1.7.5
+//////////////////////////////////////////////////////////////////////////
+
+ /*! Header for the page with bibliographic citations */
+ virtual QCString trCiteReferences()
+ { return "Библиографические ссылки"; }
+
+ /*! Text for copyright paragraph */
+ virtual QCString trCopyright()
+ { return "Авторство"; }
+
+ /*! Header for the graph showing the directory dependencies */
+ virtual QCString trDirDepGraph(const char *name)
+ { return QCString("Директория графа зависимостей ")+name+":"; }
+
+//////////////////////////////////////////////////////////////////////////
+// new since 1.8.0
+//////////////////////////////////////////////////////////////////////////
+
+ /*! Detail level selector shown for hierarchical indices */
+ virtual QCString trDetailLevel()
+ { return "уровень детализации"; }
+
+ /*! Section header for list of template parameters */
+ virtual QCString trTemplateParameters()
+ { return "Параметры шаблона"; }
+
+ /*! Used in dot graph when UML_LOOK is enabled and there are many fields */
+ virtual QCString trAndMore(const QCString &number)
+ { return "и "+number+" больше..."; }
+
+ /*! Used file list for a Java enum */
+ virtual QCString trEnumGeneratedFromFiles(bool single)
+ { QCString result = "Документация для этого перечисления сгенерерирована из файл";
+ if (!single) result += "ов";
+ result+="а:";
+ return result;
+ }
+
+ /*! Header of a Java enum page (Java enums are represented as classes). */
+ virtual QCString trEnumReference(const char *name)
+ { return QCString(name)+" Ссылки на перечисление"; }
+
+ /*! Used for a section containing inherited members */
+ virtual QCString trInheritedFrom(const char *members,const char *what)
+ { return QCString(members)+" унаследованные от "+what; }
+
+ /*! Header of the sections with inherited members specific for the
+ * base class(es)
+ */
+ virtual QCString trAdditionalInheritedMembers()
+ { return "Дополнительные унаследованные члены"; }
+
+//////////////////////////////////////////////////////////////////////////
+// new since 1.8.2
+//////////////////////////////////////////////////////////////////////////
+
+ /*! Used as a tooltip for the toggle button that appears in the
+ * navigation tree in the HTML output when GENERATE_TREEVIEW is
+ * enabled. This tooltip explains the meaning of the button.
+ */
+ virtual QCString trPanelSynchronisationTooltip(bool enable)
+ {
+ QCString opt = enable ? "включить" : "выключить";
+ return "нажмите на "+opt+" для синхронизации панелей";
+ }
+
+ /*! Used in a method of an Objective-C class that is declared in a
+ * a category. Note that the @1 marker is required and is replaced
+ * by a link.
+ */
+ virtual QCString trProvidedByCategory()
+ {
+ return "По группам @1.";
+ }
+
+ /*! Used in a method of an Objective-C category that extends a class.
+ * Note that the @1 marker is required and is replaced by a link to
+ * the class method.
+ */
+ virtual QCString trExtendsClass()
+ {
+ return "Расширяет класс @1.";
+ }
+
+ /*! Used as the header of a list of class methods in Objective-C.
+ * These are similar to static public member functions in C++.
+ */
+ virtual QCString trClassMethods()
+ {
+ return "Методы класса";
+ }
+
+ /*! Used as the header of a list of instance methods in Objective-C.
+ * These are similar to public member functions in C++.
+ */
+ virtual QCString trInstanceMethods()
+ {
+ return "Методы экземпляра";
+ }
+
+ /*! Used as the header of the member functions of an Objective-C class.
+ */
+ virtual QCString trMethodDocumentation()
+ {
+ return "Документация метода";
+ }
+
+ /*! Used as the title of the design overview picture created for the
+ * VHDL output.
+ */
+ virtual QCString trDesignOverview()
+ {
+ return "Обзор дизайна";
+ }
+
+//////////////////////////////////////////////////////////////////////////
+// new since 1.8.4
+//////////////////////////////////////////////////////////////////////////
+
+ /** old style UNO IDL services: implemented interfaces */
+ virtual QCString trInterfaces()
+ { return "Экспортируемые интерфейсы"; }
+
+ /** old style UNO IDL services: inherited services */
+ virtual QCString trServices()
+ { return "Включённые сервисы"; }
+
+ /** UNO IDL constant groups */
+ virtual QCString trConstantGroups()
+ { return "Постоянные группы"; }
+
+ /** UNO IDL constant groups */
+ virtual QCString trConstantGroupReference(const char *namespaceName)
+ {
+ QCString result=namespaceName;
+ result+=" Ссылка на постоянную группу";
+ return result;
+ }
+ /** UNO IDL service page title */
+ virtual QCString trServiceReference(const char *sName)
+ {
+ QCString result=(QCString)sName;
+ result+=" Ссылка на сервис";
+ return result;
+ }
+ /** UNO IDL singleton page title */
+ virtual QCString trSingletonReference(const char *sName)
+ {
+ QCString result=(QCString)sName;
+ result+=" Ссылка на одиночку";
+ return result;
+ }
+ /** UNO IDL service page */
+ virtual QCString trServiceGeneratedFromFiles(bool single)
+ {
+ // single is true implies a single file
+ QCString result=(QCString)"Документация для этого сервиса "
+ "сгенерированна из следующего файл";
+ if (single) result+="а:"; else result+="ов:";
+ return result;
+ }
+ /** UNO IDL singleton page */
+ virtual QCString trSingletonGeneratedFromFiles(bool single)
+ {
+ // single is true implies a single file
+ QCString result=(QCString)"Документация по этому одиночке "
+ "сгенерированна из следующего файл";
+ if (single) result+="а:"; else result+="ов:";
+ return result;
+ }
+
+//////////////////////////////////////////////////////////////////////////
};
#endif
--
1.7.10.4
|
28 messages has been excluded from this view by a project administrator.
