[Doxygen-develop] documenting other filetypes

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

hi all,

I would like to start a discussion about ideas of "how to document other file
types".

I have a project where files like a dtd and lots of xml, xsl files are important
for the developer as well. Other projects have config files or scripts.

I helped myself a bit by using a mini perl wrapper which at least reformats the
xml-comments so thatthey look like /** ... */ comments. This way we can document
the files them selfts and reference them.
For the dtd I have tried a hack to even convert the content to enums, structs
and functions. This work a little, but is ugly as the documentation (see
http://141.57.8.37/ensonic/gitk-docs/group__gitkcoredtd.html) is showing the in
this representation then.

Dimitri, how much separarated is the parser for c-style files. The goal is that
one could add a nother class and register the class together with
  * extension (that causes the class to bee invoked)
  * symbol-list it generated (e.g. entities, elements and attributes for a dtd)
Obviously there are many problems on the way to this functionallity, so lets
collect them and provide solutions, step-by-step.

Dimitri, it would be very kind, if you could tell us, wheter you would like to
support other file types in the future or if not.

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