doxygen-users — List for users of doxygen

RE: [Doxygen-users] emphasizing multiple words

[Glenn M. <gle...@vo...>]

Try putting in html syntax instead. <b>group of words</b>.

Glenn Maxey
Technical Writer
Voyant Technologies, Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301
Tel. +1 303.223.5164
Fax. +1 303.223.5275
gle...@vo...


> -----Original Message-----
> From: GF...@at... [mailto:GF...@at...]
> Sent: Tuesday, February 05, 2002 9:39 AM
> To: dox...@li...
> Subject: [Doxygen-users] emphasizing multiple words
>=20
>=20
> Hi Goyz & Girlz,
>=20
> Perhaps someone can help me.  (i.e. point me to the correct=20
> page in the
> documentation because I'm blind)  I am trying to emphasize a=20
> group of words
> (lets call it a sentence), but the only tag I can see for this type of
> thing would be the @b or \b tag.  Unfortunatly this tag only=20
> emphersizes
> the 1st word.  Does anyone know if there is a mehtod (other=20
> then putting @b
> before each word) to do this?
>=20
> Thanks,
> Grahame Falvey
> Atronic International GmbH
>=20
>=20
>=20
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>=20

[Doxygen-users] emphasizing multiple words

[<GF...@at...>]

Hi Goyz & Girlz,

Perhaps someone can help me.  (i.e. point me to the correct page in the
documentation because I'm blind)  I am trying to emphasize a group of words
(lets call it a sentence), but the only tag I can see for this type of
thing would be the @b or \b tag.  Unfortunatly this tag only emphersizes
the 1st word.  Does anyone know if there is a mehtod (other then putting @b
before each word) to do this?

Thanks,
Grahame Falvey
Atronic International GmbH

[Doxygen-users] Info on the status of the language translators (February 5th, 200 2)

[Prikryl,Petr <PRI...@sk...>]

Info on the status of the language translators (February 5th, 2002)

(Related to the Doxygen-1.2.13-20020203 in CVS; full
translator_report.txt included in the attached zip file.

Posted to doxygen-develop [for the language
maintainers], copy posted to doxygen-users [searching
for Finnish and Swedish language maintainers].)

Hi,

First of all, my special thanks to all language
maintainers. 

  -----------------------------------------------
  We are still searching for Finnish and Swedish
  maintainers because their translators became
  extremely obsolete.
  -----------------------------------------------
  
The attached traslator_report.txt shows the current
status of the Translator classes.  Here is an excerpt
that can help you to guess how much work it would
require to make your language translator up-to-date.
Notice, that the translator.pl script now shows also
what required methods are implemented by what
translators:

----------------------------------------------------------------------
The following translator classes are up-to-date (sorted alphabetically).
This means that they derive from the Translator class.  Anyway, there still
may be some details listed even for the up-to-date translators.
Please, check the text below if the translator is marked so.

  TranslatorBrazilian
  TranslatorCroatian
  TranslatorCzech
  TranslatorDutch
  TranslatorEnglish
  TranslatorFrench
  TranslatorItalian
  TranslatorRussian

----------------------------------------------------------------------
The following translator classes are obsolete (sorted alphabetically).
This means that they derive from some of the adapter classes.

  TranslatorChinese     (TranslatorAdapter_1_2_13)
  TranslatorDanish      (TranslatorAdapter_1_2_7)
  TranslatorGerman      (TranslatorAdapter_1_2_13)
  TranslatorGreek       (TranslatorAdapter_1_2_11)
  TranslatorHungarian   (TranslatorAdapter_1_2_1)
  TranslatorJapanese    (TranslatorAdapter_1_2_13)
  TranslatorKorean      (TranslatorAdapter_1_2_13)
  TranslatorNorwegian   (TranslatorAdapter_1_2_2)
  TranslatorPolish      (TranslatorAdapter_1_2_1)
  TranslatorPortuguese  (TranslatorAdapter_1_2_13)
  TranslatorRomanian    (TranslatorAdapter_1_2_1)
  TranslatorSlovak      (TranslatorAdapter_1_2_13)
  TranslatorSlovene     (TranslatorAdapter_1_2_13)
  TranslatorSpanish     (TranslatorAdapter_1_2_7)
  TranslatorUkrainian   (TranslatorAdapter_1_2_11)

----------------------------------------------------------------------
The following translator classes are implemented via deriving
from the English translator.  This should be done only in the case
when the language maintainer or the doxygen developers need to update
some really outdated translator.  Otherwise, deriving from
the translator adapter classes should be prefered for obsolete translators.
See details below in the report.

  TranslatorFinnish     (TranslatorEnglish)
  TranslatorSwedish     (TranslatorEnglish)

----------------------------------------------------------------------
The following translator adapter classes are implemented -- the older (with
lower number) are always derived from the newer. They implement the
listed required methods. Notice that some versions of doxygen did not
introduce any changes related to the language translators.  From here you
may
guess how much work should be done to update your translator:
      
  TranslatorAdapter_1_2_13      implements  2 required methods...
    QCString trImplementedFromList(int numEntries)
    QCString trImplementedInList(int numEntries)

  TranslatorAdapter_1_2_11      implements  1 required method...
    QCString trReferences()

  TranslatorAdapter_1_2_7       implements  1 required method...
    QCString trAuthor(bool first_capital, bool singular)

  TranslatorAdapter_1_2_6       implements 13 required methods...
    QCString trRTFansicp()
    QCString trRTFCharSet()
    QCString trRTFGeneralIndex()
    QCString trFile(bool first_capital, bool singular)
    QCString latexLanguageSupportCommand()
    QCString idLanguageCharset()
    QCString trClass(bool first_capital, bool singular)
    QCString trNamespace(bool first_capital, bool singular)
    QCString trGroup(bool first_capital, bool singular)
    QCString trPage(bool first_capital, bool singular)
    QCString trMember(bool first_capital, bool singular)
    QCString trField(bool first_capital, bool singular)
    QCString trGlobal(bool first_capital, bool singular)

  TranslatorAdapter_1_2_5       implements  2 required methods...
    QCString trBug()
    QCString trBugList()

  TranslatorAdapter_1_2_4       implements  8 required methods...
    QCString trInterfaces()
    QCString trClasses()
    QCString trPackage(const char *name)
    QCString trPackageList()
    QCString trPackageListDescription()
    QCString trPackages()
    QCString trPackageDocumentation()
    QCString trDefineValue()

  TranslatorAdapter_1_2_2       implements  2 required methods...
    QCString trProperties()
    QCString trPropertyDocumentation()

  TranslatorAdapter_1_2_1       implements  1 required method...
    QCString trDCOPMethods()

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

Clearly, to pass the 1.2.4 and 1.2.6 translator
adapters requires more work.  Anyway, their methods
are not extremely difficult to implement.  

If you find some time, please do update your
translator.  The comming-soon work on the new
implementation of translators would otherwise be more
difficult for those who develop the core code. 

Thanks, 
  Petr
  

-- 
Petr Prikryl, Skil, spol. s r.o., (pri...@sk...)

[Doxygen-users] File List and Class Hierarchy

[Francois St-A. <fst...@do...>]

All,
=20
Is there anyway to deactivate the generation of the Class Hierarchy
(hierarchy.html) and File List (files.html) files and corresponding =
links at
the top of every HTML file using a Doxyfile setting? Or is =
post-processing
the only way to achieve this?
=20
Regards,
=20
Fran=E7ois St-Arnaud
=20

[Doxygen-users] Latex error.

[Toni M. <ton...@wa...>]

Hi. My LaTeX output is saying me something like this:

! LaTeX Error: Too deeply nested.
=20
See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...
=20
l.49 \begin{CompactItemize}
=20
?

The html output is ok. who can avoid this error ?
--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Toni Moreno Gim=E9nez
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Pje de las rosas  n=BA 22
Vilassar de Mar=20
(Barcelona) Espa=F1a
CP: 08340

[Doxygen-users] Doxygen-1.2.13-20020203 in CVS

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

Hi,

In this week's release the following has changed:
-----------------------------------------------------------------
+ CHG: Doxygen now filters out duplicate input files.
+ ADD: If a comment block contains at least one @param command, doxygen now
       produces warnings if not all parameters of a function are documented or
       if the names of the parameters do not match the argumentlist.
       (Please report any false alarms).
+ ADD: Included language updates for Czech, French, Italian, Brazilian, Russian
+ BUG: Doxygen now exits with code 0 if there is no error (previously it
       returned 1 in some cases were no error occurred).
+ BUG: Calling "doxygen -g -" now writes the config file to stdout
       (this already worked when using "doxygen -g-").
+ BUG: Undocumented classes exposed when setting EXTRACT_ALL to YES, could
       result in broken links in the class hierarchy.
+ BUG: Fixed parser problem for function typedefs inside classes.
+ BUG: Exception specifications in Java were not parsed properly.
+ BUG: If INLINE_INHERITED_MEMB was YES, pure vitual members of base classes
       reachable via multiple paths appeared more than once in the
       documentation.
+ BUG: Removed potential recursive loop when computing reimplements relations
       for template instances.
+ BUG: Fixed argument matching problem when matching "a<int *>" with a<int * >"
+ BUG: Links in the documentation of grouped namespace members were not
       pointing to the group but to the namespace.
+ BUG: For template specializations the title of an html page contained
       plain < and > characters.
+ BUG: When computing source references undocumented members could introduce
       non-existing relations for documented members in front of it.
-----------------------------------------------------------------
Enjoy,
  Dimitri

[Doxygen-users] Documentation tree layout in mozilla 0.9.7

[Alexander S. <Ale...@co...>]

Hi all,

first of all thank you for such a great tool like doxygen!


But ... ;-)

I still have a problem showing the document tree in mozilla 0.9.7.
It seems like the elements have been disarranged. Please have a
look at the attachement, which shows the upper left corner of
an entire mozilla brower window with the questionable part.

Is this (wrong) layout caused by mozilla itsself? Or is the
code generated by doxygen wrong?

Are there any workarounds or fixes?

Thank you in advance.


Regards,

	Alexander

Dipl.-Ing. Alexander Speetzen
Communication Networks, Aachen University of Technology;
Phone: ++49-241-8027954, Fax: ++49-241-8022242;
mailto:Ale...@Sp... | mailto:sp...@co...
http://www.speetzen.de,      | http://www.comnets.rwth-aachen.de/~spee

[Doxygen-users] tex files for source are not generated

[Matt W. <Mat...@sp...>]

Hi all!

I'm trying to generate pdf documents from the latex generated by =
doxygen.  I can generate the docs fine.  However, links to the source =
files do not work properly.  I took a look at refman.log and found the =
following


! pdfTeX warning (dest): name{qw_8c-source} has been referenced but does =
not ex
ist, replaced by a fixed one

This would explain why the link to the source file doesn't work.  Is =
this a bug or is there something I am doing incorrectly?

Thanks,
Matt

Matthew E. Wolf=20
[ Applications Engineer, Government Wireless ]
Spectrum Signal Processing, Inc.

t 301.459.8888 x18 // f  301.459.8887

<http://www.spectrumsignal.com>

> Confidential information may be contained in this message.=20
> If you are not the addressee indicated in this message please=20
> destroy this message and kindly notify the sender by reply email.
>=20

[Doxygen-users] disable doxygen processing for parts of the file

[Francis M. <fra...@so...>]

Hoi,

This is probably a standard question.
I'd like to disable doxygen processing for parts of a source file.
I tried something like this already:

In the INI file I've added

ALIASES                = "doxoff=@ifnot SKIP_DOX" \
                         "doxon=@endif"
ENABLED_SECTIONS       = SKIP_DOX

A source file could look like this:

/// @doxoff
    source code comes here
/// @doxon


It does not work however. Does somebody have another solution?

Thx

---
Kind regards,
francis meyvis

Sony Software Development Center - Europe
+32 2 724 8 643, Sint StevensWoluwestraat 55, B1130 Brussels, Belgium

Re: [Doxygen-users] multi-project .DOX needed? Guidance and questions

[Rod O. <oll...@SE...>]

There are two settings in the configuration file that may assist you:

MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT

However, if limiting the size of the generated graphs is not an option for you, you can at least
open the graph using an image viewer which supports much larger image sizes.

I use S-PicView which can be found at http://www.yukudr.com/imageviewer/.

Regards,
Rod Ollerhead


"John H. Bergman" wrote:

> Hi,
>
>   I've been using Doxygen for a while now, and really have grown to love it.. NICE WORK
> GUYS!  And now that the GraphViz guys have released an update for windows that fixes the
> line problem... even better!
>
>   I do have a small problem and am seeking quidance about how to correct it.  My project
> has gotten so complex that the chart that is generated for the class tree is so large that
> IE 6 (and 5.x) will not display one of the GIF files.  Has anyone else had this problem?  How
> do you get around it?
>
>   Also, I have broken the project up into components, and those generate really well.  How
> do you take the components and merge them together?  I'd like to avoid running the how doxygen
> on the full set of code for this?
>
> John
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] how to avoid bad "more..." when not needed

[Prikryl,Petr <PRI...@sk...>]

Hi,

Alain wrote...
> On every line of the first part of the generated page
> for a specific class, I can see my brief description
> followed by "more..." with a link to the documentation
> part, but with no more information than this brief
> description...

While I am not using only the brief descriptions, I have
also noticed that the "more..." is somehow redundant, 
sometimes.

For example, in the list of methods, the "more..." points
to the same place as the method identifier.  The
question is whether it cannot be removed from here.
On the other hand, it could be replaced by something
like "(Detailed description.)" where it points to the detailed
description.  (But it should be discussed by more users.)

In the Czech translation, I could not find the word that
would look well in all situations.  Because of that, I put
only the "..." string inside the Czech translator.  The side
effect is that it looks better in the cases mentioned by
Alain.  The minus is that it is less visible.  But, frankly,
I am not using this kind of link very often.

Petr

-- 
Petr Prikryl, Skil, spol. s r.o., (pri...@sk...)

[Doxygen-users] Zone problems on the generated bitmaps from dot

[Stephane R. <ste...@sy...>]

Hi,

I just downloaded the new release of dot for win32.
I've seen that some problems are solved ( text doesn't fit the rectangle =
).
But the "clickable areas" are wrong ( you need to click outside the =
rectangle to have the link ).
Is it a problem with doxygen or with dot ?
Who generates this areas ?

Thanks,

Stephane

[Doxygen-users] multi-project .DOX needed? Guidance and questions

[John H. B. <jo...@zo...>]

Hi,

  I've been using Doxygen for a while now, and really have grown to love =
it.. NICE WORK=20
GUYS!  And now that the GraphViz guys have released an update for =
windows that fixes the
line problem... even better!

  I do have a small problem and am seeking quidance about how to correct =
it.  My project
has gotten so complex that the chart that is generated for the class =
tree is so large that
IE 6 (and 5.x) will not display one of the GIF files.  Has anyone else =
had this problem?  How
do you get around it?

  Also, I have broken the project up into components, and those generate =
really well.  How
do you take the components and merge them together?  I'd like to avoid =
running the how doxygen
on the full set of code for this?

John

[Doxygen-users] how to avoid bad "more..." when not needed

[Alain R. <are...@ya...>]

I only use brief descriptions...
On every line of the first part of the generated page
for a specific class, I can see my brief description
followed by "more..." with a link to the documentation
part, but with no more information than this brief
description...

How can I avoid to see ths "more..." when there is no
need to follow the link.

Thanks



__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

[Doxygen-users] Separating comments from the code item

[Glenn M. <gle...@vo...>]

Hi all,

I'm having problems developing a special-case scheme to keep doxygen
comments separate from the source files. I've gotten this to work for
functions (@fn) by supplying the exact prototype.=20

I have not made this work for enumerations (@enum) or typedef's
(@typedef); it doesn't match on short definitions (@typedef enum BOGUS)
or on long definitions (@typedef enum BOGUS {one=3D1; two=3D2} BOGUS;) =
that
try to put in the exact syntax on one line. (We are using the "typedef
enum" syntax.) The long definitions are also cumbersome.

Why do I have this problem?

Our developers do a lot of code generation. This means that the input
files to Doxygen sometimes are generated from one or more source files
by one or more other tools first. Those tools do not pass comments
through. I would normally be exploring updating the tools to pass the
comments through, but we don't have control over all of the code
generation tools.

My goal is to get comments closer to the source code so that they remain
up-to-date and accurate. Right now, I have the information in FrameMaker
that gets exported into the HTML system. Doxgyen exports prototypes into
the HTML system, but there is nothing that tells you about the code
item. If you happen to find it using the index, you'll see both
references and get all needed info. If you access through the doxygen
portion alone, you'll be left hanging (what is this?)

Any ideas on how I can still get the syntax accuracy of Doxgyen together
with the detailed descriptions?

Glenn Maxey
Technical Writer
Voyant Technologies, Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301
Tel. +1 303.223.5164
Fax. +1 303.223.5275
gle...@vo...

[Doxygen-users] rtf NOT support Globals index?

[chen b. <ch...@ya...>]

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogImNoZW4gYmluIiA8Y2hiX3No
QHlhaG9vLmNvbS5jbj4NClRvOiA8ZG94eWdlbi11c2Vyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ+
DQpTZW50OiBXZWRuZXNkYXksIEphbnVhcnkgMTYsIDIwMDIgNDoyMSBQTQ0KU3ViamVjdDogcnRm
IG91dHB1dCBOT1Qgc3VwcG9ydCBPTkUgY29tcGxldGUgR2xvYmFscyBpbmRleD8gYnV0IGh0bWwg
T0shDQoNCg0KPiBQcm9ibGVtOg0KPiAqKioqKioqKg0KPiBJIG91dHB1dCB0aGUgaHRtbCBkb2N1
bWVudCBhbmQgcnRmIGRvY3VtZW50IGF0IHRoZSBzYW1lIHRpbWUuDQo+IGJ1dCBydGYgZG8gbm90
IHByb2R1Y2UgR2xvYmFscyhJIG1lYW4gZ2xvYmFsIGZ1bmN0aW9ucyBhbmQgdmFyaWFibGVzLi4u
KSANCj4gaW5kZXghDQo+IA0KPiBidXQgaHRtbCB2ZXJzaW9uIGRvIGl0Lg0KPiANCj4gSSBtZWFu
IHJ0ZiBwcm9kdWNlIHRoZSBnbG9iYWxzIGluZGV4IGZvciBFVkVSWSBmaWxlKGZvciBleGFtcGxl
LCBtYWluLmMpLA0KPiBidXQgSSBhbHNvIHdhbnQgYSBDT01QTEVURSBnbG9iYWxzIGluZGV4IGZv
ciB0aGUgd2hvbGUgcHJvamVjdC4NCj4gDQo+IA0KPiBJIGNoZWNrZWQgdGhlIGRveHl3aXphcmQn
cyBHZW5lcmFsIHRhYidzIG9wdGlvbnMgYnV0IG5vIGlkZWEuDQo+IA0KPiBFbnZpcm9ubWVudDoN
Cj4gKioqKioqKioqKioqDQo+IERveHlnZW4gdmVyc2lvbiAxLjIuMTMuMTsNCj4gb24gVHVyYm9s
aW51eCBTZXJ2ZXIgNi41Ow0KPiBFbmdsaXNoIGxhbmd1YWdlIHJ0ZiBvdXRwdXQ7DQo+IA0KPiB0
aGUgdGVzdCBzb3VyY2UgY29kZToNCj4gKioqKioqKioqKioqKioqKioqKioqDQo+IA0KPiAvKi0t
LS0tLS0tLS0tLS0tLXNvdXJjZSBjb2RlLS0tLS0tLS0tLS0tLWJlZ2luICovDQo+ICNpbmNsdWRl
IDxzdGRpby5oPg0KPiAjaW5jbHVkZSAibWFpbi5oIg0KPiANCj4gaW50IG1haW4odm9pZCApDQo+
IHsNCj4gIHByaW50ZigiaGVsbG8gd29ybGRcbiIpOw0KPiAgLyogbm93IHByZXBhcmVkIGNhbGwg
Zm4oKSAqLw0KPiAgZm4oKTsNCj4gDQo+IH0NCj4gDQo+IGludCBkLGUsZjsgLyohPCBoZXkhIGxl
dCB1cyBkZWZpbmUgZCwgZSwgZiAqLw0KPiANCj4gLyohXHZlcmJhdGltDQo+ICoqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gfCBG
dW5jdGlvbiBuYW1lICAgICA6IGZuDQo+IHwgRGVzY3JpcHRpb24gICAgIDogDQo+IHwgUmV0dXJu
ICAgIDogc3RhdGljIHZvaWQgDQo+IHwgQXJndW1lbnQgICAgICAgICAgOiB2b2lkDQo+IHwgQ2F1
dGlvbiAgICAgICAgICAgOiANCj4gfC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiB8IENyZWF0ZSAgICAgICAgICAgIDogMjAwMi0x
LTE1IGJ5IENoZW4gQmluDQo+ICAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKipcZW5kdmVyYmF0aW0NCj4gKi8NCj4gc3RhdGljIHZvaWQg
Zm4odm9pZCApDQo+IHsNCj4gIGludCBhLGIsYzsNCj4gIHByaW50Zigibm93IGNhbGxpbmcgZm4o
KSIpOw0KPiANCj4gfQ0KPiAvKi0tLS0tLS0tLS0tLS0tLXNvdXJjZSBjb2RlLS0tLS0tLS0tLS0t
LWVuZCAqLw0KPiANCg==

[Doxygen-users] Strange titles

[Moshe K. <Kr...@Pa...>]

Hi

Can anyone suggest why most of the HTML output files from Doxygen have the
line:

<title>Initialization</title>

When I perform a search amongst the docs for a particular string, 80% of the
results are named "Initialization". Opening them in an HTML editor reveals
that the line I quoted above has been affixed to them, evidently by Doxygen.

A pointer, perhaps: I do have an HTML document (created as HTML) in the
collection of files which has this title. Would this have an affect on all
the rest?

Any ideas?

[Doxygen-users] Wish for hard spaces

[Peter S. <pet...@hu...>]

Hello all

Some doxygen tags (eg @ref label "text") stop working if they are not
on one line; they must not be word wrapped. So I can't use the word
wrapping feature of my favourite text editor.

One possible solution (apart from making it "wrappable") would be to
allow "hard" spaces (  in HTML) between "@ref" and "label" and
"text". Usually the hard space is character 160 (32 for space + 128), it
is displayed in the western charsets as a space.

Regards, Peter
-- 
    _   _        Peter Steiner <pet...@hu...>
  / /_/ /        Hug-Witschi AG <http://www.hugwi.ch/>
 /  _  /         Electronic Engineering
/_/ /_/  _   _   Industriestrasse 12
   / / / / / /   CH-3178 Boesingen
  / /_/ /_/ /    Tel  +41 31 740 44 44
 /_ _ _ _ _/     Fax  +41 31 740 44 45

[Doxygen-users] Problems in handling C++ 'throw' clauses

[Bohun T. <bh...@dr...>]

SSBmb3VuZCB0aGF0IGRveHlnZW4gaGFzIGEgcHJvYmxlbSBpbiBoYW5kbGluZyBDKysgJ3Rocm93
JyBjbGF1c2VzLiBGb3IgZXhhbXBsZSANCg0KY2xhc3MgeyANCnB1YmxpYzogDQovLyEgdGhyb3dz
IGV4Y2VwdGlvbiANCnZpcnR1YWwgdm9pZCB0ZXN0KCkgdGhvcndzIGV4Y2VwdGlvbjsgDQovLyEg
dGVzdDIgbWVtYmVyIGZ1bmN0aW9uIA0Kdm9pZCB0ZXN0MigpOyANCn0gDQpQcm9ibGVtcyBhcmU6
IA0KMSkgRG94eWdlbiBpZ25vcmVzIGZ1bmN0aW9uIHdoaWNoIGhhcyAndGhyb3cnIGtleSB3b3Jk
LiANCjIpIEFmdGVyIHRoZSAndGhyb3cnIGtleXdvcmQgYWxsIHRoZSBjb21tZW50cyBhcmUgaWdu
b3JlZC4gDQoNClBsZWFzZSBoZWxwIG1lIGhvdyB0byBzb2x2ZSBpdC4gOikgDQpUaGFua3MgaW4g
YWR2YW5jZS4gDQoNCg0K

Re: [Doxygen-users] Pb with dot-generated graphics : the names are outside the boxes

[Stephane R. <ste...@sy...>]

Hi Dimitri,

I found that if I remove the doxfont font from the dot file , the output is
good.
I found also that the doxfont.ttf is not a vaild font under windows (
doubleclick on doxfont.ttf ).

It is possible to set this font in doxygen ?

Thanks,

Stephane
----- Original Message -----
From: "Dimitri van Heesch" <di...@st...>
To: <dox...@li...>
Sent: Thursday, January 24, 2002 3:29 PM
Subject: Re: [Doxygen-users] Pb with dot-generated graphics : the names are
outside the boxes


> On Thu, Jan 24, 2002 at 02:29:02PM -0500, Stephane Routelous wrote:
> > Hi,
> >
> > As you can see here :
http://exotk.sourceforge.net/exotk-doc/inherits.html , I have problems with
Class names which are outside the Boxes ( the boxes are too small, and the
text is not centered ).
> >
> > What can I do ?
>
> This is a bug in dot. I suggest to check whether you have the latest
release
> of graphviz. If so, run doxygen with DOT_CLEANUP set to NO, and send the
> faulty dot graph (and the font file) as a bug report to the graphviz
> developers (see www.graphviz.org). Also mention the platform you are
using.
>
> Regards,
>   Dimitri
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] using more sourceforge features for doxygen project?

[Phil E. <ped...@dm...>]

In the last couple of days I keep running up against more and more
limitations of doxygen.  And of course the best way to solve these problems
is to hack code rather than just complain.  :-)  So I've been poking around
trying to get the CVS version of doxygen to checkout.  I think I finally have
it, but I'm wondering why the sourceforge.net CVS server isn't being used.

I note that the SF.net project does have open forums and a bug-tracking
system set up for doxygen, but they don't seem to get used very much.
Are they the right place to look, or is this mailing list where things
happen, or somewhere else?


Phil

Re: [Doxygen-users] Pb with dot-generated graphics : the names are outside the boxes

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

On Thu, Jan 24, 2002 at 02:29:02PM -0500, Stephane Routelous wrote:
> Hi,
> 
> As you can see here : http://exotk.sourceforge.net/exotk-doc/inherits.html , I have problems with Class names which are outside the Boxes ( the boxes are too small, and the text is not centered ).
> 
> What can I do ?

This is a bug in dot. I suggest to check whether you have the latest release
of graphviz. If so, run doxygen with DOT_CLEANUP set to NO, and send the
faulty dot graph (and the font file) as a bug report to the graphviz
developers (see www.graphviz.org). Also mention the platform you are using.

Regards,
  Dimitri

[Doxygen-users] Pb with dot-generated graphics : the names are outside the boxes

[Stephane R. <ste...@sy...>]

Hi,

As you can see here : =
http://exotk.sourceforge.net/exotk-doc/inherits.html , I have problems =
with Class names which are outside the Boxes ( the boxes are too small, =
and the text is not centered ).

What can I do ?

TIA,

Stephane

[Doxygen-users] Re: Bug: K & R Style functions

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

On Thu, Jan 24, 2002 at 10:04:11AM -0700, David Hite wrote:
> Dimitri,
> 
> Doxygen can't handle (old) K & R C style functions. They are not ANSI
> standard but many compilers will still compile them.
> 
> It's up to you to decide if this is a bug, or just not supported.

This is on the TODO list but will probably not be added (by me at least), 
since there are tools like GNU's protoize/unprotoize that can do the 
translation to ANSI C.

Regards,
  Dimitri

[Doxygen-users] Bug: K & R Style functions

[David H. <hi...@la...>]

Dimitri,

Doxygen can't handle (old) K & R C style functions. They are not ANSI
standard but many compilers will still compile them.

It's up to you to decide if this is a bug, or just not supported.

-Dave-