Petr Prikryl | 5 Apr 2005 08:55
Picon

Translators revisited (searching for volunteers)

(Posted to doxygen-develop, copied to doxygen-users.)

Translators revisited? Again? (Dust covers the old doc.)

Do you think that the things below should have
some wiki page (for discussion)?

This is related to possible future implementation
of the translation of Doxygen output to the
supported human languages. The below mentioned
document was last touched in August 2001 (when
Doxygen's XML output support just begun or even
was not there -- I am not sure). Some experimental 
work was also done in that time to replace the code 
of the translator classes by string templates that could
possibly be placed outside the doxygen executable,
in text files (entity definitions, or so). 

The full doxygenable source and the html of 
the document is available at
http://www.skil.cz/doxygen/TranslatorsRevisited.zip
(Note that it was done more than 3 years earlier, 
with older Doxygen.)

Some experimental C++ sources that show how the
things could be done are available at 
http://www.skil.cz/doxygen/Conversion.zip
It contains also doxy.exe (Windows) and the
generated results from the translator_xx.h files
(as mentioned in the document).
(Continue reading)

Binsan | 11 Apr 2005 16:01

API Doc of Doxygen Parse Tree available ?

I am trying to implement a new output generator by modifying the
RTFGenerator. But I am having trouble understanding the parsing mechanism. 

As I am lost many times tracing the code, I wonder if there is any extra
documentation for developers (besides that already present in the source
code) of the structure of the DocNode and its children.

Any other documentation for developers?

Binsan

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Max Bowsher | 11 Apr 2005 18:07

Member group syntax

In Doxygen 1.4.1, this worked:

/**  <at> {
 * This is a member group. */
#define FOO "bar"
/**  <at> } */

In Doxygen 1.4.2, member groups got seriously broken.

In Doxygen 1.4.2-20050410, member groups are a lot better, but the above 
syntax still doesn't work.
Is it valid? Or was it merely accidental that it used to work?

Thanks,

Max.

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Pierre Blanchard | 22 Apr 2005 11:16
Picon

Problem to compile the wintool doxygen project for windows

I'm trying to compile doxygen for Windows using Microsoft's Visual C++
(version 6.0).

I use the .dsw file found in the wintools directory provided with the source
distribution.

Unfortunatly while linking I have the message belows which warns me about 2
errors, and I can't build the .exe :

>Linking...
>scanner.obj : error LNK2001: unresolved external symbol "bool __cdecl
parseCommentBlock(class Entry *,class QCString const &,class QCString >const
&,int,bool,bool,enum Protection &)"
(?parseCommentBlock <at>  <at> YA_NPAVEntry <at>  <at> ABVQCString <at>  <at> 1H_N2AAW4Protection
> <at>  <at>  <at> Z)
>Debug/Doxygen.exe : fatal error LNK1120: 1 unresolved externals
>Error executing link.exe.

To resolve this problem I had to change in the project the location of the
commentscan.h file from the "External Dependencies" folder to the "Source
Files" folder of "Doxygen Files".

I would like to know from the .dsw file maintainer or anyone else, whether
this change may affect the final result of the wintools project, and if it
was possible to update this file.

Regards.

Pierre

(Continue reading)


Gmane