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

Re: [Doxygen-develop] autolink to a group (module)

[Dimitri v. H. <di...@st...>]

On Wed, Jan 07, 2004 at 01:44:10PM +0100, Stefan Kost wrote:
> hi hi,
> 
> after reading 'doxygen/html/autolink.html' I am still in the dark of how to
> create autolinks to module (group) pages.
> Has anyone an idea?

\ref label_of_the_group "Text to show as link"

should work.

Regards,
  Dimitri

[Doxygen-develop] autolink to a group (module)

[Stefan K. <ko...@im...>]

hi hi,

after reading 'doxygen/html/autolink.html' I am still in the dark of how to
create autolinks to module (group) pages.
Has anyone an idea?

Ciao
  Stefan
-- 
      \|/            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
===-=-=--=---=---------------------------------- - - -  -    -

Re: [Doxygen-develop] CALL_GRAPH is missing function

[Stefan K. <ko...@im...>]

Hi Dimitri,

can you please comment on this. I can easily provide more examples. here is the
code and the images is attached.

gboolean gitk_dialog_trans(GitkDialogPtr const dialog) {
	gitk_log("  before domain");
	if(!gitk_dialog_trans_domain(dialog)) return(FALSE);
	gitk_log("  after domain");
	//gitk_dialog_dump(dialog->dst);
	gitk_log("  before style");
	if(!gitk_dialog_trans_style(dialog)) return(FALSE);
	gitk_log("  after style");
	//gitk_dialog_dump(dialog->dst);

	//-- do these as the last ones, so that nodes created during the transformation
are translated as well

	gitk_log("  before i18n");
	if(!gitk_dialog_trans_i18n(dialog)) return(FALSE);
	gitk_log("  after i18n");
	//gitk_dialog_dump(dialog->dst);
	gitk_log("  before expansion");
	if(!gitk_dialog_trans_expand(dialog)) return(FALSE);
	gitk_log("  after expansion");
	return(TRUE);
}

Stefan Kost wrote:
> hi dimitri,
> 
> for the following code the callgraph is missing the gitk_init() function, but
> has two arows pointing to gitk-done(). The graph is attached.
> 
> int test_gitk_init(void {
>   gitk_init(&test_argc,&test_argvptr,PACKAGE,LOCALEDIR);
>   gitk_done();
> }
> 
> 
> If have used the following statements in Doxyfile :
> 
> PREDEFINED             = "LOCALEDIR=\"/usr/share/locale\""
> EXCLUDE_PATTERNS       = config.h
> 
> 1.) How can I verify that the parser not stumbles upon something like
> gitk_init(&test_argc,&test_argvptr,,);
> due to uninitialized macros. Is the above definition for PREDEFINED correct when
> I want LOCALEDIR to resolve to "/usr/share/locale"?
> 
> 2.) When I ask that "config.h" should be excluded from the documentation, will
> doxygen still read the file when it hits an include statement, so that the
> defines from that file are expanded?
> 
> Ciao
>   Stefan
> 
> 
> ------------------------------------------------------------------------
> 

-- 
      \|/            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
===-=-=--=---=---------------------------------- - - -  -    -

[Doxygen-develop] patches

[Akos K. <ak...@us...>]

Hi,

I'm glad to see that most of my patches got into the CVS, but there are two
of them for which I got no feedback and are not in the CVS. Any chance of
inserting them into the sources?

Regards,
Akos


2003-12-15  Akos Kiss  <ak...@us...>

        * classdef.cpp (ClassDef::writeDocumentation,
        ClassDef::writeMemberList): File title and page title made the same.
        * filedef.cpp (FileDef::writeDocumentation): Likewise.
        * namespacedef.cpp (NamespaceDef::writeDocumentation): Likewise.

2003-12-12  Akos Kiss  <ak...@us...>

        [...]

        * src/config.l (HTML_SHOW_LOGO): New configuration option.
        * doc/config.doc (HTML_SHOW_LOGO): Document it.
        * src/htmlgen.cpp (HtmlGenerator::init, writePageFooter): Use it.

[Doxygen-develop] Windows binaries available for Doxygen-1.3.5-20040105

[Petr P. <Pr...@sk...>]

Hi,
=20
If interested, you can download the doxygen binaries
compiled for MS Windows from
=20
  http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
=20
This is the place where you should find also the next
releases.  The name of the archive is constructed=20
from the date of CVS release.
=20
The binaries are NOT created automatically, so it may
happen that some newer CVS sources were not compiled
because I am not present to do that or I forgot... ;)
=20
Regards,
  Petr
=20
--=20
Petr Prikryl (prikrylp at skil dot cz)

[Doxygen-develop] Tag & localization

[<ca...@cr...>]

	Happy New New!
Some problems in localized version of tag file:
- invalid code page in tag file
- invalid chars conversation at tag file

	Patch is attached:
Index: src/doxygen.cpp
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /u/kp3softd/cvsroot/src/doxygen.cpp,v
retrieving revision 1.156
diff -u -r1.156 doxygen.cpp
--- src/doxygen.cpp	21 Nov 2003 13:10:38 -0000	1.156
+++ src/doxygen.cpp	5 Jan 2004 14:23:35 -0000
@@ -8262,7 +8262,10 @@
       exit(1);
     }
     Doxygen::tagFile.setDevice(tag);
-    Doxygen::tagFile << "<?xml version=3D'1.0' encoding=3D'ISO-8859-1' =
standalone=3D'yes'?>" << endl;
+#if QT_VERSION >=3D 200
+    Doxygen::tagFile.setEncoding(QTextStream::Latin1);
+#endif
+    Doxygen::tagFile << "<?xml version=3D'1.0' encoding=3D'" + =
theTranslator->idLanguageCharset() + "' standalone=3D'yes'?>" << endl;
     Doxygen::tagFile << "<tagfile>" << endl;
   }
=20
Thanks.

Re: [Doxygen-develop] Problems running dot. Check your installation!

[Dimitri v. H. <di...@st...>]

On Tue, Dec 30, 2003 at 06:55:31PM +0100, Stefan Kost wrote:
> Hi Dimitri,
> 
> recently when running doxygen(1.3.5) it display this message :
> 
> Generating graph info page...
> Problems running dot. Check your installation!
> 
> dot is from graphviz-1.7.15.
> any ideas? couldn't you pass through the message you received from running dot
> (or alternatively send it e.g. to /tmp/doxygen.log).

Try running "dot -V" from the command-line. If that works it should be ok.
If not try graphviz-1.10, since older versions may not support .png output
out of the box. I currently only check the exit code of the program, so 
I cannot easily pass on a message I receive from dot.

Regards,
  Dimitri

[Doxygen-develop] Problems running dot. Check your installation!

[Stefan K. <ko...@im...>]

Hi Dimitri,

recently when running doxygen(1.3.5) it display this message :

Generating graph info page...
Problems running dot. Check your installation!

dot is from graphviz-1.7.15.
any ideas? couldn't you pass through the message you received from running dot
(or alternatively send it e.g. to /tmp/doxygen.log).

Ciao
  Stefan
-- 
      \|/            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
===-=-=--=---=---------------------------------- - - -  -    -

Re: [Doxygen-develop] xml & inner page

[Dimitri v. H. <di...@st...>]

On Fri, Dec 26, 2003 at 03:45:19PM +0300, ???????? ????????? ?????????? wrote:
> 	Hi!
> 	There is error when generating inner page to xml, e.g. standart doxygen example examples\group:
> 	File group__group5.xml contain documentation only for mypage2 (last page at group5), and dosn't contain documentation for group5 & page1.
> 
> 	In fact, doxygen generate documentation step by step:
> 	- for group5
> 	- for page1
> 	- for page2
> 	but it has same names group_group5.xml. Another fact: index.xml contain references to group, page1 & page2
> 
> 	The PageDef::getOutputFileBase() return page name as inner group name, this is valid for html output, but doubtful for xml.

This is indeed broken. Should be fixed in the next CVS update.

Regards,
  Dimitri

[Doxygen-develop] xml & tab

[<ca...@cr...>]

	Hi, all again!
	Xml generator insert tab symbols direct into xml source (&example) =
output, thus there are no way to differ tab from space at XSLT =
transformation.
	Simple attached patch change tab to appropriated count of <sp/> tags in =
compliance with TAB_SIZE Doxyfile setting.
	Thanks, - Alexandr -

[Doxygen-develop] xml & inner page

[<ca...@cr...>]

	Hi!
	There is error when generating inner page to xml, e.g. standart doxygen =
example examples\group:
	File group__group5.xml contain documentation only for mypage2 (last =
page at group5), and dosn't contain documentation for group5 & page1.

	In fact, doxygen generate documentation step by step:
	- for group5
	- for page1
	- for page2
	but it has same names group_group5.xml. Another fact: index.xml contain =
references to group, page1 & page2

	The PageDef::getOutputFileBase() return page name as inner group name, =
this is valid for html output, but doubtful for xml.

	Thanks, - Alexandr -

[Doxygen-develop] Enhancement Request (Line number references)

[Rick E. <ri...@ev...>]

OK ... Ref/anchors are useful ...
But, 
I would really like to refer to source line numbers with \todo
\bug and \test ... seems the cleanest way is to introduce a new
command maybe \location which expands to file:lineno 
(eg.   foo.c:104 )

This is useful when reading code and annotating for review. I've been
using doxygen as part of a translation project and using the
\todo, \bug and \test tags as ways to know what I still need in
the way of tests and code...

It is hard with 8,000 lines of code to get back to specific 
areas that code reading has indicated I should check further.
The tags help but \location tag would be very very useful.

I looked at doxygen sources and all the lexers seem to swallow
"\n" so this is probably not that easy to implement ...

in the past I let the parser handle \n and the lexer only
counts the lines... tricky issues with lexicals that cover
more than one line ... they have to could \n 's themselves

Just a thought and request for enhancement ... 

I have too many other projects going to rip into 
doxygen and patch... it does not look to be a quick fix ...

On Tue, 2003-12-16 at 00:53, Petr Prikryl wrote:
> Info on the status of the language translators (December 16, 2003) 
> 
> Related to the doxygen 1.3.5-20031215 in CVS. Posted to
> doxygen-develop, copied to doxygen-users. The previous
> report was dated September 24, 2003.
> 
> ATTENTION: Full translator_report.txt is stored (together
> with this text) at
> http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
> as tr2003MMDD.zip where MMDD is replaced by the month and day.
> 
> Summary: 
>  - Doxygen 1.3.5 was released recently.
>  - Total 30 (KoreanEn added), 13 up-to-date (+4), 5 almost 
>    up-to-date (-1), 7 slightly obsolete (-3), 2 obsolete, 
>    1 not maintained, 2 different. 
>  - Searching for the Finnish maintainer and possibly also 
>    for Hungarian and Norwegian ones.
> 
> ------------------------------------------------------------
> 
> Hi,
> 
> Firstly, thanks to all active language maintainers. The
> Christmas time is almost here. Stop to type and enjoy the
> other sides of the life (I know that some of you will not
> follow that hint ;)  There is a great new-year self-promise
> for some of you: "I will bring my language support for
> Doxygen to up-to-date status in January!"
> 
> If you speak Finnish, Hungarian, or Norwegian, please
> consider to help with the language support to the existing
> maintainers or take the maintainership and carve your name
> into the related part of the source files ;)
> 
> ==============
> Current status
> ==============
> 
> The total is 30 languages now. The new one is not really
> new. It is the KoreanEn (mixed Korean and English). Because
> it is derived from TranslatorEnglish, it is reported as
> really obsolete, which is not true (similar case as the
> JapaneseEn). The newer translator.py script will be modified
> not to report such translators this way (later).
> 
> Thirteen of the languages are up-to-date: Brazilian, Chinese
> Traditional, Croatian, Czech, Danish, Dutch, English,
> French, German, Italian, Korean, Russian, and Serbian.
> 
> Five of the languages are very close to the up-to-date
> status. They reflect at least some changes since Doxygen 1.3
> release: Polish, Japanese, Portuguese, Spanish, and Swedish.
> Good job!
> 
> Seven of the languages are slightly obsolete, but they still
> require impementing not more than 18 methods: Catalan,
> Chinese, Greek, Romanian, Slovak, Slovene, and Ukrainian.
> 
> Two of the languages -- Hungarian and Norwegian -- must
> implement about 45 methods to become up-to-date. Please, try
> harder. Or should we search for not-so-tired, new
> maintainers? Keep in mind that the translator adapters, used
> for your translator classes, make Doxygen slightly bigger
> and more complex. After updating your languages, the
> adapters can be removed.
> 
>   -----------------------------------------------
>   We still have not found new Finnish maintainer.  
>   The translator became extremely obsolete, and 
>   it seems that the original maintainer is not
>   in touch with doxygen anymore.
>   -----------------------------------------------
> 
> Reminder: look at the translator report inside
> http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
> tr2003MMDD.zip
> If you think that your language should be listed as
> up-to-date, but it is not, you probably forgot to change the
> base class of your translator class to "Translator". Then,
> you can run the doc/translator.pl script to generate the
> translator report and check the status of your translator
> report and see what has to be done to make it up-to-date.
> 
> Note: The translator.pl is the original script that will be
> replaced by translator.py one day. You can also give it a
> try. In fact, it is almost one-to-one rewrite of the perl
> version, so do not be disappointed if you like Python. It is
> planned to be rewritten using the OO approach.
>   
> With regards,
>   Petr
>  
-- 
Rick Eversole <ri...@ev...>

[Doxygen-develop] XML & examples

[<ca...@cr...>]

	Hi all!
	Output XML documentation dosn't contain reference to examples (e.g. =
doxygen/examples/example.cfg).=20
	As I think Dimitri suggest to generate link to examples from parsed =
source examples. (All comments in doxygen source XML generation file =
contain something like this:// -examples. m_exampleSDict is a protected =
member of class) Is it valid? But it is nontrivial task.
	Dimitri, if above-mentioned assertion failed, please approve public =
const access to m_exampleSDict, and I try to write patch to generate =
simplesect kind=3Dexample (?).

[Doxygen-develop] RFE: join main page and modules page

[Stefan K. <ko...@im...>]

hi all,

would it make sense to join the main page and modules page?
I have a c based project and therefore on the modules page are the modules
defined by @defgroup. This is actually not a lot. The mainpage is not some big
as well (I know it depends on how much one puts into that section).

The advantage would be to save some space in the page header and imho to give a
the reader an immediate entry into the docs.

Anyway this is releate to my previous RFE concerning "consistent style of docs",
especially that the list of the modules hierarchy uses the same style as on the
modules pages and that modules can have a brief description apart from their name.

open question: If this would be accepted, which order is the best - mainpoage,
modules or vice versa?

Any comments?

ciao
  Stefan
-- 
      \|/            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
===-=-=--=---=---------------------------------- - - -  -    -

[Doxygen-develop] Nasser Ahmed/UK/Symbian is out of the office

[<Nas...@Sy...>]

I will be out of the office starting  19/12/2003 and will not return until
19/01/2004.

I will respond to your message when I return. Please contact Dave Jobling
x1842 if the matter is urgent. Thanks.



**********************************************************************
Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 2-6 Boundary Row, London, Southwark, SE1 8HP, UK.
This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify pos...@sy... and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy.
**********************************************************************

[Doxygen-develop] LaTeX and Math Formula in doxygen

[Rick E. <ri...@ev...>]

I have started a simple user guide for math formulas under doxygen.
My input to doxygen and my configuration file are in the attached
tarball.
This is still be worked on... but I thought I'd release the current
version for comments.

This creates an series of html pages, LaTeX docs and man pages...
I have only been looking at html pages during development.

This is not an exhaustive help (arrays are not explained).

I was forced into a lot of research in order to document a program that
I have that relies on a large set of math equations. Previously, these
equations were separately documented from the code. Doxygen allows me to
embed the equations into the source.

Let me know what you think of the helps ....

-- 
Rick Eversole <ri...@ev...>

[Doxygen-develop] PATCH: hide friend compounds in index

[Akos K. <ak...@us...>]

Hi all,

an earlier patch of mine claimed that it extended the meaning of the 
HIDE_FRIEND_COMPOUNDS to hide friend classes from _everywhere_. Well, I 
realized, that after applying the patch the friend classes remain listed on 
index pages, so attached is a patch which removes friend compounds even from 
indices.

Regards,
Akos

2003-12-19  Akos Kiss  <ak...@us...>

        * src/index.cpp (writeMemberList, countClassMembers): Do not
        include friend compounds into the index.

[Doxygen-develop] hungarian translator

[Akos K. <ak...@us...>]

Hi all,

attached is a new, extended, revised and updated Hungarian translator. All 
feedback is highly appreciated!

Regards,
Akos

Re: [Doxygen-develop] Info on the status of the language translators (December 16, 2003)

[Akos K. <ak...@us...>]

Hi all,

I'm sad to hear that the hungarian translator is so obsolate. Last night
I've extended the translator so that it is now up-to-date in the sense that
it now inherits from Translator and all messages are hungarian. I've also
fixed some typos and made the messages a bit more consistent.

I still have to check all the messages once more, but I'll send the updated
translator as soon as I'm ready (hopefully tonight or tomorrow).

Additionally, if the current hungarian maintainer doesn't want to maintain
the translator I'll apply for maintainership.

Regards,
Akos

Btw, are there any test cases I could use to test all the messages?

----- Original Message -----
From: "Petr Prikryl" <Pr...@sk...>
To: "Doxygen developers" <dox...@li...>
Cc: "Doxygen users" <dox...@li...>
Sent: Tuesday, December 16, 2003 9:53 AM
Subject: [Doxygen-develop] Info on the status of the language translators
(December 16, 2003)


If you speak Finnish, Hungarian, or Norwegian, please
consider to help with the language support to the existing
maintainers or take the maintainership and carve your name
into the related part of the source files ;)

Two of the languages -- Hungarian and Norwegian -- must
implement about 45 methods to become up-to-date. Please, try
harder. Or should we search for not-so-tired, new
maintainers? Keep in mind that the translator adapters, used
for your translator classes, make Doxygen slightly bigger
and more complex. After updating your languages, the
adapters can be removed.

[Doxygen-develop] unsubscribe RE: Doxygen-develop digest, Vol 1 #292 - 1 msg

[<wh...@cu...>]

-----Original Message-----
From: dox...@li... [mailto:doxygen-
dev...@li...] On Behalf Of doxygen-develop-
re...@li...
Sent: Wednesday, December 17, 2003 1:06 PM
To: dox...@li...
Subject: Doxygen-develop digest, Vol 1 #292 - 1 msg

Send Doxygen-develop mailing list submissions to
	dox...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/doxygen-develop
or, via email, send a message with subject or body 'help' to
	dox...@li...

You can reach the person managing the list at
	dox...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Doxygen-develop digest..."


Today's Topics:

   1. Info on the status of the language translators (December 16,
2003) (Petr Prikryl)

--__--__--

Message: 1
Date: Tue, 16 Dec 2003 09:53:52 +0100
From: "Petr Prikryl" <Pr...@sk...>
To: "Doxygen developers" <dox...@li...>
Cc: "Doxygen users" <dox...@li...>
Subject: [Doxygen-develop] Info on the status of the language
translators (December 16, 2003)

Info on the status of the language translators (December 16, 2003) 

Related to the doxygen 1.3.5-20031215 in CVS. Posted to
doxygen-develop, copied to doxygen-users. The previous
report was dated September 24, 2003.

ATTENTION: Full translator_report.txt is stored (together
with this text) at
http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/ 
as tr2003MMDD.zip where MMDD is replaced by the month and day.

Summary: 
 - Doxygen 1.3.5 was released recently.
 - Total 30 (KoreanEn added), 13 up-to-date (+4), 5 almost 
   up-to-date (-1), 7 slightly obsolete (-3), 2 obsolete, 
   1 not maintained, 2 different. 
 - Searching for the Finnish maintainer and possibly also 
   for Hungarian and Norwegian ones.

------------------------------------------------------------

Hi,

Firstly, thanks to all active language maintainers. The
Christmas time is almost here. Stop to type and enjoy the
other sides of the life (I know that some of you will not
follow that hint ;)  There is a great new-year self-promise
for some of you: "I will bring my language support for
Doxygen to up-to-date status in January!"

If you speak Finnish, Hungarian, or Norwegian, please
consider to help with the language support to the existing
maintainers or take the maintainership and carve your name
into the related part of the source files ;)

==============
Current status
==============

The total is 30 languages now. The new one is not really
new. It is the KoreanEn (mixed Korean and English). Because
it is derived from TranslatorEnglish, it is reported as
really obsolete, which is not true (similar case as the
JapaneseEn). The newer translator.py script will be modified
not to report such translators this way (later).

Thirteen of the languages are up-to-date: Brazilian, Chinese
Traditional, Croatian, Czech, Danish, Dutch, English,
French, German, Italian, Korean, Russian, and Serbian.

Five of the languages are very close to the up-to-date
status. They reflect at least some changes since Doxygen 1.3
release: Polish, Japanese, Portuguese, Spanish, and Swedish.
Good job!

Seven of the languages are slightly obsolete, but they still
require impementing not more than 18 methods: Catalan,
Chinese, Greek, Romanian, Slovak, Slovene, and Ukrainian.

Two of the languages -- Hungarian and Norwegian -- must
implement about 45 methods to become up-to-date. Please, try
harder. Or should we search for not-so-tired, new
maintainers? Keep in mind that the translator adapters, used
for your translator classes, make Doxygen slightly bigger
and more complex. After updating your languages, the
adapters can be removed.

  -----------------------------------------------
  We still have not found new Finnish maintainer.  
  The translator became extremely obsolete, and 
  it seems that the original maintainer is not
  in touch with doxygen anymore.
  -----------------------------------------------

Reminder: look at the translator report inside
http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/ 
tr2003MMDD.zip
If you think that your language should be listed as
up-to-date, but it is not, you probably forgot to change the
base class of your translator class to "Translator". Then,
you can run the doc/translator.pl script to generate the
translator report and check the status of your translator
report and see what has to be done to make it up-to-date.

Note: The translator.pl is the original script that will be
replaced by translator.py one day. You can also give it a
try. In fact, it is almost one-to-one rewrite of the perl
version, so do not be disappointed if you like Python. It is
planned to be rewritten using the OO approach.
  
With regards,
  Petr
 
-- 
Petr Prikryl, (prikrylp at skil dot cz)



--__--__--

_______________________________________________
Doxygen-develop mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-develop


End of Doxygen-develop Digest

[Doxygen-develop] Info on the status of the language translators (December 16, 2003)

[Petr P. <Pr...@sk...>]

Info on the status of the language translators (December 16, 2003)=20

Related to the doxygen 1.3.5-20031215 in CVS. Posted to
doxygen-develop, copied to doxygen-users. The previous
report was dated September 24, 2003.

ATTENTION: Full translator_report.txt is stored (together
with this text) at
http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/=20
as tr2003MMDD.zip where MMDD is replaced by the month and day.

Summary:=20
 - Doxygen 1.3.5 was released recently.
 - Total 30 (KoreanEn added), 13 up-to-date (+4), 5 almost=20
   up-to-date (-1), 7 slightly obsolete (-3), 2 obsolete,=20
   1 not maintained, 2 different.=20
 - Searching for the Finnish maintainer and possibly also=20
   for Hungarian and Norwegian ones.

------------------------------------------------------------

Hi,

Firstly, thanks to all active language maintainers. The
Christmas time is almost here. Stop to type and enjoy the
other sides of the life (I know that some of you will not
follow that hint ;)  There is a great new-year self-promise
for some of you: "I will bring my language support for
Doxygen to up-to-date status in January!"

If you speak Finnish, Hungarian, or Norwegian, please
consider to help with the language support to the existing
maintainers or take the maintainership and carve your name
into the related part of the source files ;)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Current status
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The total is 30 languages now. The new one is not really
new. It is the KoreanEn (mixed Korean and English). Because
it is derived from TranslatorEnglish, it is reported as
really obsolete, which is not true (similar case as the
JapaneseEn). The newer translator.py script will be modified
not to report such translators this way (later).

Thirteen of the languages are up-to-date: Brazilian, Chinese
Traditional, Croatian, Czech, Danish, Dutch, English,
French, German, Italian, Korean, Russian, and Serbian.

Five of the languages are very close to the up-to-date
status. They reflect at least some changes since Doxygen 1.3
release: Polish, Japanese, Portuguese, Spanish, and Swedish.
Good job!

Seven of the languages are slightly obsolete, but they still
require impementing not more than 18 methods: Catalan,
Chinese, Greek, Romanian, Slovak, Slovene, and Ukrainian.

Two of the languages -- Hungarian and Norwegian -- must
implement about 45 methods to become up-to-date. Please, try
harder. Or should we search for not-so-tired, new
maintainers? Keep in mind that the translator adapters, used
for your translator classes, make Doxygen slightly bigger
and more complex. After updating your languages, the
adapters can be removed.

  -----------------------------------------------
  We still have not found new Finnish maintainer. =20
  The translator became extremely obsolete, and=20
  it seems that the original maintainer is not
  in touch with doxygen anymore.
  -----------------------------------------------

Reminder: look at the translator report inside
http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/=20
tr2003MMDD.zip
If you think that your language should be listed as
up-to-date, but it is not, you probably forgot to change the
base class of your translator class to "Translator". Then,
you can run the doc/translator.pl script to generate the
translator report and check the status of your translator
report and see what has to be done to make it up-to-date.

Note: The translator.pl is the original script that will be
replaced by translator.py one day. You can also give it a
try. In fact, it is almost one-to-one rewrite of the perl
version, so do not be disappointed if you like Python. It is
planned to be rewritten using the OO approach.
 =20
With regards,
  Petr
=20
--=20
Petr Prikryl, (prikrylp at skil dot cz)

Re: [Doxygen-develop] doxygen preprocessor, not always expands

[Stefan K. <ko...@im...>]

hi dimitri,

Okay and thanks a lot.

> On Tue, Dec 09, 2003 at 03:49:26PM +0100, Stefan Kost wrote:
> 
>>Hi Sigmund,
>>
>>many thanks, that works. I hope that Dimitri will apply the patch.
> 
> 
> I don't think the patch was a complete fix of the problem (that's 
> why I didn't integrate it). I'm now working on a complete solution, which 
> requires teaching the preprocessor routines to cope with comment blocks.
> 
> Regards,
>   Dimitri
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> 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
===-=-=--=---=---------------------------------- - - -  -    -

Re: [Doxygen-develop] doxygen preprocessor, not always expands

[Dimitri v. H. <di...@st...>]

On Tue, Dec 09, 2003 at 03:49:26PM +0100, Stefan Kost wrote:
> Hi Sigmund,
> 
> many thanks, that works. I hope that Dimitri will apply the patch.

I don't think the patch was a complete fix of the problem (that's 
why I didn't integrate it). I'm now working on a complete solution, which 
requires teaching the preprocessor routines to cope with comment blocks.

Regards,
  Dimitri

[Doxygen-develop] PATCH: file titles

[Akos K. <ak...@us...>]

Hi all,

I discovered a small bug in the generation of titles of (HTML) files. The 
title for a template class X looks like " TemplateX class Reference". The 
word "class" should start with a capital C and a space is placed on a wrong 
place.

But! When I analysed how file titles are generated I found that the title 
strings are hardcoded english into the sources and not built using the 
translator technique. In the 4 (at least for me) most important cases I've 
replaced the hardcoded strings with translator calls (and made the file 
titles the same as the titles on the pages). Patch is attached.

However, there are still lots of hardcoded english file titles throughout the 
program, mostly in index.cpp, which should be eliminated. Below is the list 
of problems I've found. In the first 2 cases there is currently no translator 
function which could be used. In the case of classdef.cpp, the signature of 
the called trMemberList should be changed to accept the name of the compound 
as a parameter to give the responsibility of inserting the class name into 
the phrase to the translator function. In index.cpp lots of files are created 
with hardcoded file titles. In those cases translator functions are already 
used to translate the _page_ titles but not the file titles. The best 
solution would be (IMHO) to use the same phrases in the file and page titles, 
with the only difference that on page titles the project name should also 
appear. Unfortunately this solution (and the solutions to the above problems) 
would change the interface of the translator and would need some work on the 
language side.

I don't know who is going to decide, but well, at least now the problem is 
known.

filedef.cpp: " Source File"
doxygen.cpp: "Example Documentation"
classdef.cpp: trMemberList() -> trMemberList(string)
index.cpp: "Hierarchical Index"->trClassHierarchy, "Graphical Class 
Hierarchy"->trGraphicalHierarchy, "File Index"->trFileList, "Package 
Index"->trPackageList, "Namespace Index"->trNamespaceList,"Alphabetical 
index"->trCompoundIndex, "Annotated Index"->trCompoundList, "Compound Member 
Index"->trCompoundMembers, "File Member Index"->trFileMembers, "Namespace 
Member Index"->trNamespaceMembers,"Example Index"->trExamples, "Page 
Index"->trRelatedPages, "Graph Legend"->trLegendTitle, "Module 
Index"->trModules

Regards,
Akos

2003-12-15  Akos Kiss  <ak...@us...>

        * classdef.cpp (ClassDef::writeDocumentation, 
        ClassDef::writeMemberList): File title and page title made the same.
        * filedef.cpp (FileDef::writeDocumentation): Likewise.
        * namespacedef.cpp (NamespaceDef::writeDocumentation): Likewise.

[Doxygen-develop] PATCH: hide friend compounds

[Akos K. <ak...@us...>]

Hi all,

the problem of mine is that the reader of an API documentation does not care 
whether a class is a friend of another or not. This is simply implementation 
issue. In the current version of doxygen a configuration option named 
HIDE_FRIEND_COMPOUNDS is already present, but unfortunately it hides friend 
classes only from the brief descriptions but not from the detailed sections 
and the member lists.

Attached is a patch, which extends the meaning of HIDE_FRIEND_COMPOUNDS to 
hide friend classes from everywhere.

Regards,
Akos

2003-12-14  Akos Kiss  <ak...@us...>

        * src/memberdef.cpp (MemberDef::isDetailedSectionLinkable): Hide
        detailed description of friend compounds.
        * src/classdef.cpp (ClassDef::internalInsertMember): Do not include
        friend compounds into member lists.