<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.text.doxygen.general">
    <title>gmane.text.doxygen.general</title>
    <link>http://blog.gmane.org/gmane.text.doxygen.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10306"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10305"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10298"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10290"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10282"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10281"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10279"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10278"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10277"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10275"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10269"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10267"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10265"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10261"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10256"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10253"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10252"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10251"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10250"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.doxygen.general/10248"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10306">
    <title>More documentation on \example?</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10306</link>
    <description>&lt;pre&gt;I'm new to doxygen (everyone has to start sometime, right?) and I've got a
question about the use of the \example tag.

I have a java source file with this in it:
/**
 * \briefDetermine if the API call has been canceled.
 * 
 * \return true if the API call was canceled, false if the API
call was not canceled.
 */
public boolean canceled() {
return isCanceled;
}
/**
 * \example edkresult_canceled_example.js
 * Some info about the canceled example.
 */

The file edkresult_canceled_example.js has an example of using the
"canceled" method:
// edkresult_canceled_example.js
function main() {
     var output = "API Test\n";
     var API = new MyApi();                // instantiate the API
     if (API != null) {                    // if we have a valid API
instance, make our calls
         var version = API.getVersion();   // get the result of the
API call
         output += "The API call " + (version.canceled() : "was" :
"was not") + " canceled.\n";
    }
    return output;                &lt;/pre&gt;</description>
    <dc:creator>Steve Goodrich</dc:creator>
    <dc:date>2012-05-23T20:13:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10305">
    <title>Creating a &lt; at &gt;subpage connection without actuallygenerating a link</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10305</link>
    <description>&lt;pre&gt;
Hello all,

I have a question to the group, related
 to my previous question but this time regarding only &amp;lt; at &amp;gt;subpage. I have 
the same setup I presented in my previous email but I also want the 
included htmls which come from generated pages to be a subpage to this 
main doc page. &amp;lt; at &amp;gt;subpage would work nicely except I don't want the link 
to appear the way all other links appear in the documentation nor do I 
want it to appear where I write the &amp;lt; at &amp;gt;subpage command. Is there any 
option to create the &amp;lt; at &amp;gt;subpage link between two pages but without 
actually having the link appear? What I am using now is a hidden div to 
achieve it. Any other more doxygen-ish way exists?

Here is what I do:

/**
**
** &amp;lt;div style="display:none;"&amp;gt;
** &amp;lt; at &amp;gt;subpage ExampleTopic1PGE
** &amp;lt; at &amp;gt;subpage ExampleTopic2PGE
** &amp;lt;/div&amp;gt;

**&amp;lt;!-- more stuff above --&amp;gt;

** &amp;lt; at &amp;gt;docsubsection{3.1 ExampleTopic_1}
** &amp;lt; at &amp;gt;docsubpage{ExampleTopic1PGE}

** &amp;lt; at &amp;gt;htmlinclude Doxygen_Html/ExampleTopic1PGE.html

**

** &amp;lt; at &amp;gt;docsubsection{3.2 Example Topic 2}
** &amp;lt; at &amp;gt;docsubpage{ExampleTopic2PGE&lt;/pre&gt;</description>
    <dc:creator>Lefteris Karapetsas</dc:creator>
    <dc:date>2012-05-23T03:05:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10298">
    <title>Markup For Tables - No Header Row</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10298</link>
    <description>&lt;pre&gt;
I'd like to use the Markup technique for creating a table but I need a
table without a header (my table is several rows/columns of values and
the header would meaningless).  Looking at the commands it looks like it
insists on treating the first row in a special way.  Is there a way
around this?

&lt;/pre&gt;</description>
    <dc:creator>Jake Colman</dc:creator>
    <dc:date>2012-05-22T12:44:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10290">
    <title>&lt; at &gt;subpage not working properly, if a page and a section of another page have the same name</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10290</link>
    <description>&lt;pre&gt;Hi all.



I have a setup like this:



/**

&amp;lt; at &amp;gt;mainpage Name

&amp;lt; at &amp;gt;subpage Foo

&amp;lt; at &amp;gt;subpage FooBar

*/



/**

&amp;lt; at &amp;gt;page Foo Foo

Some text

&amp;lt; at &amp;gt;subpage Bar

*/



/**

&amp;lt; at &amp;gt;page Bar Bar

Some text

*/



/**

&amp;lt; at &amp;gt;page FooBar

Some text

&amp;lt; at &amp;gt;section Bar

Some more text

*/



If I generate a doxygen html-docs from this setup, then the subpage link on
page Foo links to FooBar’s section Bar instead of to page Bar. However, the
link in the treeview correctly links to page Bar.



Is this a known bug with known workarounds od do I really have to assure,
that all pages, sections, subsections and subsubsections in a project have
unique names (which could be quite problematic when generating a doc from
multiple projects from different devs)?



Thanks,

Stefan.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint secur&lt;/pre&gt;</description>
    <dc:creator>Stefan Ludewig</dc:creator>
    <dc:date>2012-05-21T14:23:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10282">
    <title>Tableofcontents and copydocing a page</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10282</link>
    <description>&lt;pre&gt;
Hello all,

I have two different and quick questions. 

Question 1: Using \tableofcontents I am trying to organize the main documentation page of my library but it seems that the indentation of the list gets destroyed after encountering the first &amp;lt; at &amp;gt;subsubsection. In particular all the &amp;lt; at &amp;gt;sections afterwards go to the &amp;lt; at &amp;gt;subsection level. When I checked the \tableofcontents documentation it mentioned only that it works for up to subsections and no more. So I guess this is why this occurs. How can I document a table of contents for more indentation levels? Anyone else aware of this issue? Any way to solve it? I might be forced to:
a) either do the ToC manually
b) Have all indentation in the page from &amp;lt; at &amp;gt;subsubsection and down with a different custom html tag so that doxygen won't see it and the ToC won't get screwed. Of course that means that the ToC will have only two indentation levels which beats the whole purpose I guess.


Question 2: I have a &amp;lt; at &amp;gt;page (not the &amp;lt; at &amp;gt;mainpage) which is the biggest documentation page of&lt;/pre&gt;</description>
    <dc:creator>Lefteris Karapetsas</dc:creator>
    <dc:date>2012-05-20T16:23:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10281">
    <title>Opening new tab for svg image through "arrow out"</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10281</link>
    <description>&lt;pre&gt;Dear All,

In the new release there has been a change in respect to handling svg images:

When I click on Windows, using the latest version of Firefox, on the
arrow a new, empty tab is opened, and I get the message:

  Firefox doesn't know how to open this address, as the protocol(d)
isn't associated with any program.

When doing the same in the Internet Explorer a new tab is opened and
the svg image is shown.

(When doing the same in the older version (printer icon) I got similar
messages, but I never used it.)

Any suggestions ?

Albert

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Albert</dc:creator>
    <dc:date>2012-05-20T11:20:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10279">
    <title>Doxygen-1.8.1 in SVN</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10279</link>
    <description>&lt;pre&gt;Hi,

Version 1.8.1 has been released. Here is the changelog since the last SVN 
update:
------------------------------------------------------------------------------
+ BUG: id 674583: Fortran: continuation by ampersand not placed in code output.
+ ADD: A -- will now be rendered as an 'en dash', similar --- will produce an
       mdash.
+ BUG: id 673870: Added C++11 classes when BUILTIN_STL_SUPPORT is enabled.
+ CHG: Added natural scrolling for tablet devices (like the iPad)
       when using the treeview.
+ BUG: id 673983: Using a backslash in a section cause 026E30F to appear in the
       latex TOC.
+ BUG: id 675757: Fixed indenting issue after the end of a markdown code block
       inside a list.
+ BUG: id 523156: Fortran: Prefix of routines got stripped.
+ BUG: id 676294: Fixed LaTeX error when backslash appeared in a hyperlinked
       code fragment.
+ BUG: id 671166: Fortran: Fixed problem causing call/caller graphs not to be
       generated.
+ ADD: id 676116: Use new index style for page index.
+ C&lt;/pre&gt;</description>
    <dc:creator>Dimitri van Heesch</dc:creator>
    <dc:date>2012-05-19T12:22:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10278">
    <title>Hiding the Main Page</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10278</link>
    <description>&lt;pre&gt;I was wondering if there is any way to hide the main page.  I have tried setting the visible property for the mainpage in the DoxygenLayout.xml to no, but the main page navigation tab always shows up.

Thanks in advance for your help,

Deep
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Jasdeep Saini</dc:creator>
    <dc:date>2012-05-19T02:54:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10277">
    <title>Help Linking to External Documentation</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10277</link>
    <description>&lt;pre&gt;
I am trying to figure out how to use Tag Files to link to external
documentation that is available for the third party libraries that I am
using, specifically Qt and Roguewave SourcePro.  For both libraries I
have access to their source code.  Both libraries also provide
beautiful documentation on their respective web sites.  In Roguwave's
case I'm almost certain it was produced by some version of Doxygen.

What is the recommended way to include Roguwave's and Qt's documentation
in to my own documentation so that I process Roguwave and Qt only once?
Do I have to first run Doxygen against the third-party source code?
Doxygen's manual seems to imply that you can link to external
documentation even if you do not have the original source code?  Also,
if I have to process the source code, what is the value of the URL
option to the tag file?

Can someone please point me to the correct approach for getting Roguwave
and Qt to link with my own documentation?

Thanks.

...Jake


&lt;/pre&gt;</description>
    <dc:creator>Jake Colman</dc:creator>
    <dc:date>2012-05-17T12:15:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10275">
    <title>unable to use \triangledown in latex.</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10275</link>
    <description>&lt;pre&gt;Hi,
 I am not able to use the symbol \triangledown which are part of
amssymb package in  latex. Document generation fails. It is possible
to specify which packages to use in doxygen?

Thanks,
Venkatesh

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Venkatesh U</dc:creator>
    <dc:date>2012-05-16T22:46:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10269">
    <title>Cryptic Warning Message</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10269</link>
    <description>&lt;pre&gt;
Normally warnings are generated using the (default) setting "$file:$line:
$text", and this normally gives a message in the format:

C:\display.c:1768: warning: parameters of member print are not (all)
documented

However I'm getting one warning that I can't resolve:

&amp;lt;&amp;lt; at &amp;gt;6&amp;gt;:1: warning: parameters of member &amp;lt; at &amp;gt;6 are not (all) documented

I can't find any way of detecting which line, function, variable etc.. that
is causing the above warning.
Any suggestions?
&lt;/pre&gt;</description>
    <dc:creator>BenG</dc:creator>
    <dc:date>2012-05-11T10:23:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10267">
    <title>Aliases with arguments won't work</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10267</link>
    <description>&lt;pre&gt;
Hello,

I am working with doxygen 1.8 in Windows using the DoxyWizard. No matter how many combinations or solutions I tried I can't seem to make the aliases work with arguments.
According to the manual here http://www.stack.nl/~dimitri/doxygen/custcmd.html  I need to add something like:

ALIASES += l{1}="\ref \1" 

I do so and then I try to refer to it by putting \l something in my code.
The result is always : 
warning: Found unknown command `\l'

If I add it from inside doxywizard I just write 
 l{1}=\ref \1 
If I add it directly to the configuration file I write as was from the example above with ALIASES+= . No matter what I do I get the same result. It is not working for me. Can anyone help me?
I have been trying to figure this out since yesterday and I have no idea what the problem might be.

Thanks!
       ------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscap&lt;/pre&gt;</description>
    <dc:creator>Lefteris Karapetsas</dc:creator>
    <dc:date>2012-05-11T08:04:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10265">
    <title>tree like display of pages</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10265</link>
    <description>&lt;pre&gt;Hi Dimitri,

The groups html page generated has a tree like display where nested groups are shown via collapsing of tree node.

Can the same (tree like view) be implemented for pages and sub-pages.

Thanks &amp;amp; Regards,
Harpreet Singh


________________________________

NOTE: This message and its attachments are intended only for the individual or 
entity to which it is addressed and may contain confidential information or 
forward-looking statements regarding product development.  Forward-looking 
statements are subject to change at Atrenta's sole discretion and Atrenta will have 
no liability for the delay or failure to deliver any product or feature mentioned in 
such forward-looking statements.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest &lt;/pre&gt;</description>
    <dc:creator>Harpreet Singh Anand</dc:creator>
    <dc:date>2012-05-10T19:40:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10261">
    <title>including file in unsupported language</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10261</link>
    <description>&lt;pre&gt;A project I work on consists of many C and header files, and a single
file in a language X that is not supported by Doxygen, to which in the
example below I give the name "fireworks.x".

There is a requirement to include all source code in the documentation
(which is in HTML format). In order to do that I added the comment
block below to one of the C files:

/**
&amp;lt; at &amp;gt;page page99 fireworks.x

The file fireworks.x is listed below. For safety reasons it should be
used only with permission from local authorities. Warning: fire risk!

&amp;lt; at &amp;gt;verbinclude  fireworks.x
*/

The above works well. "fireworks.x" appears prominently in the
navigation tree at left, as well as a title at the top of the page.
However it would be best if I could somehow have that file not as a
loose page but rather listed in the File List in the navigation tree
at left. Is there a way to do that?

---

I use FILE_VERSION_FILTER to have Doxygen fetch file versions from the
SCM. This works for C and header files, but not for "fireworks.x". Is
there a wa&lt;/pre&gt;</description>
    <dc:creator>Piscium</dc:creator>
    <dc:date>2012-05-09T23:40:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10256">
    <title>Linking to "un-doxygened" documentation</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10256</link>
    <description>&lt;pre&gt;Hi everyone,
 
I haven't found anything about this in the manual, so here we go...
 
We have a lot of Javadoc links to stuff inside e.g. the JDK itself. Naturally, the JDK's official reference documentation isn't generated via doxygen, but by javadoc (as is the case for a lot of pure Java open source libraries). Is there a way to generate links via doxygen to pure Javadoc documentation? If not, is anybody working on this?
 
Obviously, I could download the sources to all the libraries we're using and run doxygen on them, but that would seem like redoing a job that's already been done.
 
So is there a way to achieve this?

Mit freundlichen Grüßen / Kind Regards

Raimund Klein

EDV / Software Entwickler

 

BERENBERG BANK

Joh. Berenberg, Gossler &amp;amp; Co. KG

Neuer Jungfernstieg 20

20354 Hamburg

 

Telefon +49 40 350 60-8129

Telefax +49 40 350 60-955

E-Mail raimund.klein&amp;lt; at &amp;gt;berenberg.de

www.berenberg.de &amp;lt;outbind://75/www.berenberg.de&amp;gt; 

 

Sitz: Hamburg - Amtsgericht Hamburg HRA 42659

 

Diese Nachricht einsc&lt;/pre&gt;</description>
    <dc:creator>Klein, Raimund</dc:creator>
    <dc:date>2012-05-09T07:44:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10253">
    <title>Internal anchors for methods</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10253</link>
    <description>&lt;pre&gt;Hello,

Can someone familiar with doxygen internals tell me how the internal 
page links that go from method summary to method documentation are 
generated?

They appear to use some kind of digest for an alphanumeric ID in the form:

documentation/class.html#aab5c01f99f53235d4cee8a3bc6374e99

I have users asking me if these links will stay the same over time, but 
this will only be true if the link IDs are generated based on the method 
name rather than a seed at the start of the page.

Much obliged,

Kieron

&lt;/pre&gt;</description>
    <dc:creator>Kieron Taylor</dc:creator>
    <dc:date>2012-05-08T14:06:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10252">
    <title>Callgraph not getting generated</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10252</link>
    <description>&lt;pre&gt;
I am using doxygen version 1.8.0 on windows-Xp and somehow it's not been able
to generate function call graph for my small c code. Path for dot is set
properly. I do not see any error in output log as well.

Can somebody suggest something to resolve the issue?

Regards,
Raj
&lt;/pre&gt;</description>
    <dc:creator>Raj_freescale</dc:creator>
    <dc:date>2012-05-08T07:14:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10251">
    <title>How to get a list of the classes that inherit aclass?</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10251</link>
    <description>&lt;pre&gt;
Hello,

I was wondering if there is any method, using doxygen, that would allow us to get a list of all the children of a certain class. In my case since I use C, I deal with structs a few of which have inheritance-like relationships. To accomplish that I use the doxygen &amp;lt; at &amp;gt;extends command. But now I have found myself wanting to document something like below. Assume we have a parent foo and a child foo. Some of the parent foo's functions are usable with both parent and child but some are not. I needed a way to document this. So far I am hand-coding everything but there has to be another better way.


NOW--&amp;gt;

//! &amp;lt; at &amp;gt;memberof ParentFoo


//! Can be safely used by ChildFoo1, ChildFoo2, e.t.c.


foo_func()

DESIRED --&amp;gt;
//! &amp;lt; at &amp;gt;memberof ParentFoo
//! &amp;lt; at &amp;gt;childrencanuse ParentFoo
foo_func()

I hope I can convey the meaning of what I am looking to accomplish here. Any help would be deeply appreciated. I mean .dot does that somehow when it generates the diagrams. Getting just a list of the children should be possible. Thanks&lt;/pre&gt;</description>
    <dc:creator>Lefteris Karapetsas</dc:creator>
    <dc:date>2012-05-07T10:20:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10250">
    <title>Navigation from documentation included via a tagfile back to top level</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10250</link>
    <description>&lt;pre&gt;I attempted to split up a few projects using tag files and it mostly worked.   I set ALLEXTERNALS to yes, and if I click on a class in a class list that was included via another project's tag file the browser is correctly taken to the documentation for that class.  However, the class documentation is shown within that project's doxygen site and not that of the top level project.  What I mean by that is if I click on "Main Page" while viewing the class's documentation, I'm taken to the main page for the subproject and not the top level project.  Furthermore, the only way I could find to get back to the top level project was to use the back button.  Is there a way to navigate back to the top level project from documentation parsed out of a tag file?

Secondly, is there some way to have the input files for a tag included in the main file list?  Similar to what ALLEXTERNALS does for classes.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive&lt;/pre&gt;</description>
    <dc:creator>Davidson, Josh</dc:creator>
    <dc:date>2012-05-07T05:21:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10248">
    <title>Bug in endFile (Latest version 1.8.0-SVN-20120429)</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10248</link>
    <description>&lt;pre&gt;Hello,

I'm a little lazy to register in order to file a bug properly.

If GENERATE_TREEVIEW is enabled (html option) all files of the data 
structures documentation in Latex output ends with "&amp;lt;/div&amp;gt;&amp;lt;\!-- 
doc-content --&amp;gt;".
I've been looking a little in the code but can't find this bug's origin :-/

Regards,
André

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>André Glória</dc:creator>
    <dc:date>2012-05-04T17:39:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.doxygen.general/10246">
    <title>How to process documentation for multiple librariesor components?</title>
    <link>http://comments.gmane.org/gmane.text.doxygen.general/10246</link>
    <description>&lt;pre&gt;Our code base contains 3 main components of code, each essentially its own
separate product. However, they are interconnected in that they depend on
each other (library A may use objects from library B).

Currently we run doxygen once to generate documentation for all 3
components, but this is very time consuming and also creates some issues.
For example, each of the 3 components defines its own &amp;lt; at &amp;gt;mainpage
documentation, so this creates some weird issues with what is supposed to
display on the main page.

Can someone recommend a better setup for this? Can I process documentation
on each of the 3 separately and have object references between components
somehow still linkable by doxygen? Is there a better way to organize
component &amp;lt; at &amp;gt;mainpage documentation, so each gets its own page or something?

Thanks in advance!
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has &lt;/pre&gt;</description>
    <dc:creator>Robert Dailey</dc:creator>
    <dc:date>2012-05-04T14:51:32</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.doxygen.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.doxygen.general</link>
  </textinput>
</rdf:RDF>

