doxygen-develop Mailing List for Doxygen (Page 42)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Sorry, I wanted to know how it is possible to contribute to doxygen
developpement.

How can I add code or patch ?

Thanks.

Hi Stathis,

this is really cool. I've forwarded it to the gtk-doc mailinglist as well.
To me it looks like a good way to integrate simple diagraphs into source-code
docs. Such diagraphs that desribe concepts is something that imho is often
missing. The big advantage of your approach over e.g. dor is that your diagraphs
are readable in the source as well ;-)

Ciao
  Stefan

Stathis Sideris wrote:
> Hello everyone, (sorry if you receive this twice)
> 
> I have developed a small Java utility that can generate PNG diagrams
> from ascii-art:
> 
> http://ditaa.sourceforge.net
> 
> What I would like to know is, what you think is the best way to try and
> integrate this into doxygen, so that any ascii-diagrams included in the
> comments would be rendered and the appropriate <img> tag would be
> inserted into the resulting HTML documentation.
> 
> I thought of using preprocessing, but wouldn't that require my
> preprocessor to be able to parse comments in the same way that doxygen
> does? (and what's worse, in all the languages doxygen parses!)
> 
> And another thing: do you think that's a worthwhile project (the
> intergration with doxygen)
> 
> Thanks,
> 
> Stathis
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop
> 

-- 
      \|/            Stefan Kost
     <@ @>           private            business
+-oOO-(_)-OOo------------------------------------------------------ - - -  -   -
|       __  Address  Simildenstr. 5     HTWK Leipzig, Fb IMN, Postfach 301166
|      ///           04277 Leipzig      04251 Leipzig
| __  ///            Germany            Germany
| \\\///    Phone    +49341 2253538     +49341 30766101
|  \__/     EMail    st_kost_at_gmx.net kost_at_imn.htwk-leipzig.de
|           WWW      www.sonicpulse.de  www.imn.htwk-leipzig.de/~kost/about.html
===-=-=--=---=---------------------------------- - - -  -    -

On 17 Nov 2004 18:19:13 +0000, Stathis Sideris <im...@sa...> wrote:
> Hello everyone, (sorry if you receive this twice)
> 
> I have developed a small Java utility that can generate PNG diagrams
> from ascii-art:
> 
> http://ditaa.sourceforge.net

Nice!

> What I would like to know is, what you think is the best way to try and
> integrate this into doxygen, so that any ascii-diagrams included in the
> comments would be rendered and the appropriate <img> tag would be
> inserted into the resulting HTML documentation.
> 
> I thought of using preprocessing, but wouldn't that require my
> preprocessor to be able to parse comments in the same way that doxygen
> does? (and what's worse, in all the languages doxygen parses!)

I would suggest to add a pair of commands (\ditaa .. \endditaa) 
to doxygen that work in a similar way as the \dot ... \enddot commands
(which can now be used to include graph descriptions and let dot
convert them into images).

> And another thing: do you think that's a worthwhile project (the
> intergration with doxygen)

Yes, I believe so.

Regards,
  Dimitri

Hello everyone, (sorry if you receive this twice)

I have developed a small Java utility that can generate PNG diagrams
from ascii-art:

http://ditaa.sourceforge.net

What I would like to know is, what you think is the best way to try and
integrate this into doxygen, so that any ascii-diagrams included in the
comments would be rendered and the appropriate <img> tag would be
inserted into the resulting HTML documentation.

I thought of using preprocessing, but wouldn't that require my
preprocessor to be able to parse comments in the same way that doxygen
does? (and what's worse, in all the languages doxygen parses!)

And another thing: do you think that's a worthwhile project (the
intergration with doxygen)

Thanks,

Stathis

Dimitri,

I have come across a style bug with unumbered lists. It's only a bug if 
you try to set a custom style on <ul>. I use doxygen  to document a  
large C++ project - it's great, thank you! I want to give the unnumbered 
lists that are used to list the class members at the top of the 
generated HTML pages a custom background color, so they stand out more 
as a group. I added an entry for <ul> to my custom CSS file. I use a 
light page background color (darker than white) and have the list 
background color a few shades lighter. On its own it doesn't look good 
but when you give the list a much darker one pixel border I looks great. 
The subtle difference in shades becomes more obvious and the lists 
appears to stand out from the page.

Unfortunately this is where the style bug occurs. The custom style also 
gets applied to the nested <ul> that are used to display the class 
hierarchy entries in the 'hierarchy.html' file. Not only does the top 
level <ul> have a border but all the nested <ul> do as well - and it 
looks ugly. So I have to manually edit the file to remove the borders, 
and its a long file - about 420 classes across two libraries. Everywhere 
else top level lists look OK.

Would it be possible to implement a nested <ul> class in the CSS that 
could be used to reverse any style changes applied to a top level <ul>. 
Then all nested <ul> could be generated with this nested <ul> class 
instead of a standard <ul>. I don't know if you ever intended such a 
style to be applied to lists but it looks good, and I'm sure it would 
add new design possibilites to Doxygen documentation.

Regards,
Jeff Franks.

On Tue, Oct 26, 2004 at 01:32:54PM -0500, Jim Witte wrote:
> Hi, 
> 
>   Does doxygen support documentation in multiple languages?   
> 
> As an example, the basic schema is that somewhere at the "top" of the 
> source definition (or in a configuration file), a "default language" is 
> defined.  Then a set of "Alternate Languages" is defined, in a 
> Scheme-style list (language identifiers are [a-zA-Z0-9]* )  Then 
> certain '///' comments that have a '< [Identifier]' and directly follow 
> default-language comments would define one of the alternate language 
> comments.  Then the command-line for generating the documentation would 
> have an optional language setting (something like 'doxygen -l EN'). 

Doxygen has a language setting via OUTPUT_LANGUAGE in the configuration
file. It also supports switching between languages via the \~ command.
There is the example from the documentation:

/*! \~english This is english \~dutch Dit is Nederlands \~german Dieses ist
    deutsch. \~ output for all languages.
 */

Regards,
  Dimitri

Hi,

   Does doxygen support documentation in multiple languages?

As an example, the basic schema is that somewhere at the "top" of the =20=

source definition (or in a configuration file), a "default language" is =20=

defined.  Then a set of "Alternate Languages" is defined, in a =20
Scheme-style list (language identifiers are [a-zA-Z0-9]* )  Then =20
certain '///' comments that have a '< [Identifier]' and directly follow =20=

default-language comments would define one of the alternate language =20
comments.  Then the command-line for generating the documentation would =20=

have an optional language setting (something like 'doxygen -l EN').

Here is an example of how this might look (taken from the Desktop =20
Connection Library, which uses Doxygen): (see =20
http://www.kallisys.com/newton/dcl/)

/// DefaultLang =3D EN
/// AltLangs =3D (FR)
@interface DeliveryController : NSObject < IDCLObjCApplication >
{
	// C++
	TDCLCommLayer*			mCommLayer;		///< =
Couche de communication
	///<EN Communications layer
	TDCLServer*				mServer;		=
///< Serveur (\c nil s'il ne tourne pas)
	///<EN Server (\c nil if it returns no *?
}

   I don't know whether Doxygen interprets comments following function =20=

definition headings.. (I haven't actually used it, just looked at it's =20=

use in the source files.

// =20
------------------------------------------------------------------------=20=

- //
//  * main
// =20
------------------------------------------------------------------------=20=

- //
// Point d'entr=E9e de l'application Delivery.
// EN> Entry point for the Delivery Application
int
main( int argc, const char *argv[] )
{
	return NSApplicationMain( argc, argv );
}

Jim Witte
js...@bl...
Indiana University CS=

On Sat, Oct 09, 2004 at 12:23:03PM -0700, Brown, Dave wrote:
> 
> So has it been confirmed that the \example command no longer works? There is
> a bugzilla #135270 which has been around a while, though never confirmed.

I don't think there is a problem with the \example command, but more with
the way you try to use it. I've added a description to the bug that hopefully
clarifies things.

Regards,
  Dimitri

So has it been confirmed that the \example command no longer works? There is
a bugzilla #135270 which has been around a while, though never confirmed.

Anyone?

Thanks,

Dave

On Fri, Oct 08, 2004 at 07:53:30PM +0200, George Varga wrote:
> Hello Dmitri!
> 
> I have found that you should place doxygen.app on a path that does not 
> contain spaces if you want to use dot.
> 
> If the path contains spaces the dot tool will not run and the following 
> error will be printed in the log:
> 
> sh: line 1: /<pathUntilFirstSpace>: No such file or directory
> Problems running dot. Check your installation!
> 
> 
> I think you need to quote the path to dot in the sh command.

I see what you mean and will add the quotes.

Regards,
  Dimitri

Err... yeah, sorry about that. I hit the reply button a few too many times 
when subscribing to mailing lists today.

On Friday 08 October 2004 15:16, dox...@li... 
wrote:
> Welcome to the Dox...@li... mailing list!
>
> To post to this list, send your email to:
>
>   dox...@li...
>
> General information about the mailing list is at:
>
>   https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>
> If you ever want to unsubscribe or change your options (eg, switch to
> or from digest mode, change your password, etc.), visit your
> subscription page at:
>
>  
> https://lists.sourceforge.net/lists/options/doxygen-develop/spartacus%40spe
>akeasy.net
>
>
> You can also make such adjustments via email by sending a message to:
>
>   Dox...@li...
>
> with the word `help' in the subject or body (don't include the
> quotes), and you will get back a message with instructions.
>
> You must know your password to change your options (including changing
> the password, itself) or to unsubscribe.  It is:
>
>   nguwkx
>
> If you forget your password, don't worry, you will receive a monthly
> reminder telling you what all your lists.sourceforge.net mailing list
> passwords are, and how to unsubscribe or change your options.  There
> is also a button on your options page that will email your current
> password to you.
>
> You may also have your password mailed to you automatically off of the
> Web page noted above.

Hello Dmitri!

I have found that you should place doxygen.app on a path that does not 
contain spaces if you want to use dot.

If the path contains spaces the dot tool will not run and the following 
error will be printed in the log:

sh: line 1: /<pathUntilFirstSpace>: No such file or directory
Problems running dot. Check your installation!

I think you need to quote the path to dot in the sh command.

Doxygen: 1.3.8
MacOS X: 10.6.5

George Varga

On Fri, Oct 08, 2004 at 06:47:21PM +0200, Dimitri van Heesch wrote:

> On Fri, Oct 08, 2004 at 03:32:51PM +0100, Chris Croughton wrote:
> > 
> > What does Doxygen do if the same option occurs more than once?  Take the
> > last?  That would make an easy way to override options for special
> > cases.
> 
> It will indeed take the last. To append to an option instead of overriding it 
> you can use OPTION += value.

I can see I'm going to have fun with some makefiles.  Better than my
idea of having command-line switches.  I can just set things up to
append to the temporary control file as it runs through the make, then
cat it on the end of the base one into doxygen...

Thanks,

Chris C

On Fri, Oct 08, 2004 at 03:32:51PM +0100, Chris Croughton wrote:
> On Fri, Oct 08, 2004 at 03:49:53PM +0200, Dimitri van Heesch wrote:
> > If you use a decent shell, you could use something like this:
> > 
> > (cat Doxyfile ; echo "PROJECT_NUMBER=0.2") | doxygen -
> 
> Ah, taking the config stuff from stdin was something I had missed,
> thanks.  Yes, that would work fine, as would piping it through sed to
> change options.  Or rules setting up an additional file and then cat-ing
> both of them into doxygen.
> 
> What does Doxygen do if the same option occurs more than once?  Take the
> last?  That would make an easy way to override options for special
> cases.

It will indeed take the last. To append to an option instead of overriding it 
you can use OPTION += value.

Regards,
  Dimitri

On Fri, Oct 08, 2004 at 03:49:53PM +0200, Dimitri van Heesch wrote:

> Doxygen already produces XML. It could be improved to add more semantic
> information about the bodies of functions, for instance to indicate if
> something is a declaration, control statement, loop or assigment. 
> Doxygen does not have this information explicitly available somewhere already
> even though it can do syntax highlighting and linking.

Yes, it's the bodies of functions that I (and the OP) was thinking of.
I suspect that a general C/C++ to XML translator is more than Doxygen
wants to contain, however (let alone any other supported languages).

> > While I'm thinking about switches, it would be very useful to have
> > options settable from the command line, not just in the configuration
> > file.  For some purposes I have to maintain three or more versions of
> > the config file (implementer detail, user detail, overview, sometimes
> > with or without relationship charts as well), a switch to set options
> > would be a lot easier to put in a makefile with a common config file for
> > all the messy stuff (include/exclude lists, etc.).  Oh, and the version
> > number.  Or have I missed something which already allows this?
> 
> If you use a decent shell, you could use something like this:
> 
> (cat Doxyfile ; echo "PROJECT_NUMBER=0.2") | doxygen -

Ah, taking the config stuff from stdin was something I had missed,
thanks.  Yes, that would work fine, as would piping it through sed to
change options.  Or rules setting up an additional file and then cat-ing
both of them into doxygen.

What does Doxygen do if the same option occurs more than once?  Take the
last?  That would make an easy way to override options for special
cases.

Thanks,

Chris C

On Fri, Oct 08, 2004 at 11:50:25AM +0100, Chris Croughton wrote:
> (Emailed to OP as well as to the list, the sourceforge list server was
> bouncing my mails, I don't know if it still is doing so...)
> 
> On Tue, Oct 05, 2004 at 01:42:07PM -0700, Pau...@no... wrote:
> 
> > Doxygen's XML schema is a good starting point to add to if I want a
> > complete XML representation of the code, so I would like to add to it
> > rather than invent another schema. Also can anyone give me some
> > pointers where I would change the Doxygen code to output more source
> > code structure? Doxygen must know much of this information anyway, as
> > it has some more detailed information in the highlight elements of the
> > source file XML files.
> 
> I would very much like a C/C++ to XML translator, which seems to be what
> you are suggesting as a possibility (or an extreme version of what you
> are suggesting).  As you say it opens up a lot of possibilities for
> extra tools, as well as for having doxygen produce internal
> documentation (like local variables, tables of which functions use which
> global variables (set and read), etc.  It needs to be switchable,
> though.

Doxygen already produces XML. It could be improved to add more semantic
information about the bodies of functions, for instance to indicate if
something is a declaration, control statement, loop or assigment. 
Doxygen does not have this information explicitly available somewhere already
even though it can do syntax highlighting and linking.

> While I'm thinking about switches, it would be very useful to have
> options settable from the command line, not just in the configuration
> file.  For some purposes I have to maintain three or more versions of
> the config file (implementer detail, user detail, overview, sometimes
> with or without relationship charts as well), a switch to set options
> would be a lot easier to put in a makefile with a common config file for
> all the messy stuff (include/exclude lists, etc.).  Oh, and the version
> number.  Or have I missed something which already allows this?

If you use a decent shell, you could use something like this:

(cat Doxyfile ; echo "PROJECT_NUMBER=0.2") | doxygen -

Regards,
  Dimitri

(Emailed to OP as well as to the list, the sourceforge list server was
bouncing my mails, I don't know if it still is doing so...)

On Tue, Oct 05, 2004 at 01:42:07PM -0700, Pau...@no... wrote:

> Doxygen's XML schema is a good starting point to add to if I want a
> complete XML representation of the code, so I would like to add to it
> rather than invent another schema. Also can anyone give me some
> pointers where I would change the Doxygen code to output more source
> code structure? Doxygen must know much of this information anyway, as
> it has some more detailed information in the highlight elements of the
> source file XML files.

I would very much like a C/C++ to XML translator, which seems to be what
you are suggesting as a possibility (or an extreme version of what you
are suggesting).  As you say it opens up a lot of possibilities for
extra tools, as well as for having doxygen produce internal
documentation (like local variables, tables of which functions use which
global variables (set and read), etc.  It needs to be switchable,
though.

While I'm thinking about switches, it would be very useful to have
options settable from the command line, not just in the configuration
file.  For some purposes I have to maintain three or more versions of
the config file (implementer detail, user detail, overview, sometimes
with or without relationship charts as well), a switch to set options
would be a lot easier to put in a makefile with a common config file for
all the messy stuff (include/exclude lists, etc.).  Oh, and the version
number.  Or have I missed something which already allows this?

Chris C

To all,
I tried sending this directly to Simon, but the mail system complained. =
 Not sure if the problem is on his end or mine.  I downloaded the source=
 for doxygen 1.3.9 and when I tried to build the "Win32 Debug" target I got=
 the following:

doxygen.obj : error LNK2001: unresolved external symbol "void __cdecl=
 buildDirectories(void)" (?buildDirectories@@YAXXZ)
doxygen.obj : error LNK2001: unresolved external symbol "void __cdecl=
 generateDirDocs(class OutputList &)"=
 (?generateDirDocs@@YAXAAVOutputList@@@Z)
filedef.obj : error LNK2001: unresolved external symbol "public: void=
 __thiscall DirDef::writeNavigationPath(class OutputList &)"=
 (?writeNavigationPath@DirDef@@QAEXAAVOutputList@@@Z)
Debug/Doxygen.exe : fatal error LNK1120: 3 unresolved externals
Error executing link.exe.

Doxygen.exe - 4 error(s), 0 warning(s)

I did a search for the "buildDirectories" signature and got hits in=
 "dirdef.cpp" and "dirdef.h".  I added these files to the doxygen project=
 within the doxygen workspace as necessary and doxygen built successfully. =
 I just joined the developer list so I was hoping to verify my solution=
 with Simon before "officially" posting, but since the message was rejected=
 I figured I'd post and accept any deserved consequences.  If these files=
 should be added to a different project within the workspace please don't=
 hesitate to inform me of the correct solution.

Best Regards,

Bill

******************************************
The information contained in, or attached to, this e-mail, may contain=
 confidential information and is intended solely for the use of the=
 individual or entity to whom they are addressed and may be subject to=
 legal privilege.  If you have received this e-mail in error you should=
 notify the sender immediately by reply e-mail, delete the message from=
 your system and notify your system manager.  Please do not copy it for any=
 purpose, or disclose its contents to any other person.  The views or=
 opinions presented in this e-mail are solely those of the author and do=
 not necessarily represent those of the company.  The recipient should=
 check this e-mail and any attachments for the presence of viruses.  The=
 company accepts no liability for any damage caused, directly or=
 indirectly, by any virus transmitted in this email.
******************************************

I sent this mail some time ago about producing richer XML content of =
source code. Can I ask what others have done in this area? In particular =
I got a reply from someone on this list (Fred P. [j2...@ho...]) =
whom I could not contact directly now.

Doxygen's XML schema is a good starting point to add to if I want a =
complete XML representation of the code, so I would like to add to it =
rather than invent another schema. Also can anyone give me some pointers =
where I would change the Doxygen code to output more source code =
structure? Doxygen must know much of this information anyway, as it has =
some more detailed information in the highlight elements of the source =
file XML files.

thanks

paul

-----Original Message-----
From: dox...@li...
[mailto:dox...@li...]On Behalf Of ext=20
Sent: 26 April, 2004 12:01
To: dox...@li...
Subject: [Doxygen-develop] Extracting more source struture in XML output

I have recently been looking at XML and the output Doxygen can produce. =
The richness of information and versatility of what can be done with it =
is impressive given the tools available for processing XML.

Does anyone have any comments on the idea of Doxygen outputting more =
information about the structure of the source code? I am thinking of a =
breakdown in terms of blocks, statements, declarations, etc. This could =
be used for more detailed metrics or a source browser for example, but =
it also opens up more possibilities for independent tools that could use =
the Doxygen XML output, e.g. code checking. This would enhance the =
current rich informational representation of the code in XML.

Paul Mackay

-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
Doxygen-develop mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-develop

Hi there.

Here comes the new version of the Brazilian Portuguese translator. I'm 
still having problems with the CVS repository so it is based on the 
tarball doxygen-1.3.8-20040928.tar.gz.

By the way, my e-mail address has changed to this one (jun-chino at 
uol.com.br). Since I finished my M.Sc. and left the University, I don't 
know for how long my old account (chino at icmc.usp.br) will remain active.

See you...
FJTC

On Tue, Sep 28, 2004 at 10:58:56PM -0300, FJTC (Fabio Jun Takada Chino) wrote:
> Hi.
> 
> I tried to access the CVS repository again today (09/28). This time, the 
> error message is a quite different from my last try:
> 
> cvs -d :pserver:do...@ww...:/u/kp3softd/cvsroot login
> Logging in to :pserver:do...@ww...:2401:/u/kp3softd/cvsroot
> CVS password:
> cvs [login aborted]: Error reading from server www-kp3.gsi.de: -1: 
> Unknown error
> 
> Does anyone knows what is going on ?

This is quite strange. I was able to update and checkout the CVS repository
without problems. The web frontend also worked. Could this perhaps be a local
network issue on your side? Is anyone else experiencing the same problems?

Regards,
  Dimitri

Hi.

I tried to access the CVS repository again today (09/28). This time, the 
error message is a quite different from my last try:

cvs -d :pserver:do...@ww...:/u/kp3softd/cvsroot login
Logging in to :pserver:do...@ww...:2401:/u/kp3softd/cvsroot
CVS password:
cvs [login aborted]: Error reading from server www-kp3.gsi.de: -1: 
Unknown error

Does anyone knows what is going on ?

See you...
FJTC

Is anybody working on todo item #9(The ability 
to include a block of text from a file)?

Hi there.

I tried to get the most recent version from the CVS server when I got 
the following message:

cvs -d :pserver:do...@ww...:/u/kp3softd/cvsroot login
Logging in to :pserver:do...@ww...:2401:/u/kp3softd/cvsroot
CVS password:
cvs [login aborted]: Error reading from server www-kp3.gsi.de: 0: No 
such file or directory

Is there something wrong with the repository or did you moved it to 
another location ? If the later is the right answer then the homepage is 
outdated.

See you...
FJTC

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

doxygen-develop Mailing List for Doxygen (Page 42)

doxygen-develop — List for discussing new features, submitting patches, etc.