Thread: [Doxygen-users] How to prevent warning: Unsupported xml/html tag <myTagName> found ?
Brought to you by:
dimitri
From: Ed S. <ES...@fe...> - 2011-05-13 17:54:50
|
I am trying to document the xml configuration file syntax. The following documentation text: The system configuration file begins with a root element named <b><configuration></b> which contains a number of child elements as seen in the example below: generates the following warning: pageConfiguration.doc:60: warning: Unsupported xml/html tag <configuration> found What is the best way to let Doxygen know I want "<myTagName>" to be part of the documentation output? Thanks in advance, -Ed |
From: Ed S. <ES...@fe...> - 2011-05-13 18:06:27
|
> >Sorry, found it. Wordy but works. > > \verbatim<myTagName>\endverbatim I still have a few remaining warnings to kill when including a text file containing xml code. Shouldn't the html/xml tags be ignored in an include command? Fiile: pageConfig.doc \include configuration.xml.txt File: configuration.xml/txt <?xml version="1.0" encoding="utf-8"?> <!-- File: configuration.xml --> <configuration> <videoSources> </videoSources> </configuration> I tried a \verabtim and \endverbatim at the top and end of the included file. Any tips or suggestions? Thanks, -Ed > > > > On May 13, 2011, at 12:37 PM, Ed Sutton wrote: > >> I am trying to document the xml configuration file syntax. The following documentation text: >> >> The system configuration file begins with a root element named <b><configuration></b> which contains >> a number of child elements as seen in the example below: >> >> generates the following warning: >> >> pageConfiguration.doc:60: warning: Unsupported xml/html tag <configuration> found >> >> >> What is the best way to let Doxygen know I want "<myTagName>" to be part of the documentation output? >> >> Thanks in advance, >> >> -Ed >> >> >> ------------------------------------------------------------------------------ >> Achieve unprecedented app performance and reliability >> What every C/C++ and Fortran developer should know. >> Learn how Intel has extended the reach of its next-generation tools >> to help boost performance applications - inlcuding clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> Doxygen-users mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-users > > > -Ed > -Ed |
From: Dimitri V. H. <do...@gm...> - 2011-05-13 18:15:09
|
Hi Ed, On May 13, 2011, at 19:37 , Ed Sutton wrote: > I am trying to document the xml configuration file syntax. The following documentation text: > > The system configuration file begins with a root element named <b><configuration></b> which contains > a number of child elements as seen in the example below: > > generates the following warning: > > pageConfiguration.doc:60: warning: Unsupported xml/html tag <configuration> found > > > What is the best way to let Doxygen know I want "<myTagName>" to be part of the documentation output? Just escape the < and > like this \<myTagName\> or if you want the quotes as well then you don't even need to escape, so "<myTagName>" will also work. Regards, Dimitri |
From: Ed S. <ES...@fe...> - 2011-05-13 18:33:27
|
On May 13, 2011, at 1:14 PM, Dimitri Van Heesch wrote: >> What is the best way to let Doxygen know I want "<myTagName>" to be part of the documentation output? > > >Just escape the < and > like this \<myTagName\> or if you want the quotes as well then > you don't even need to escape, so "<myTagName>" will also work. Thank you Dimitri. Escaping is much easier on my typing fingers. :-) However I can not seem to escape warnings when including an xml file. perhaps the TK_EOF warning is the main clue? Document source: ------------------------- Seen in the example below are three collection types: -# \ref workstations -# \ref videoSourcesCollection -# \ref subscriptionPackagesCollection \include configuration.xml.txt <hr><b> \section secpageSequenceDiagramRefs References </b> Include Source: --------------------- <?xml version="1.0" encoding="utf-8"?> <!-- ********************************************************************************************* File: configuration.xml ********************************************************************************************* --> <configuration> <videoSources> <!-- The use of bmp file in the uri is for development purposes only; to display images of arbitray resolutions at a fixed 5 fps. --> <!-- Comment-out <videoSource> <name>SMPTE Color Bars (Still image)</name> <uri>file:///usr/share/fesvideodisplay/vsu/fes-smpte-ColorBars.bmp</uri> </videoSource> --> </videoSources> <!-- ************************************************** --> <!-- subscriptionPackages - collections of videoSources --> <!-- ************************************************** --> <subscriptionPackages> <!-- A subscriptionPackage may be used to define a collection of Subscription's to VideoSource's. --> <subscriptionPackage> <name>Default</name> <subscriptions> <!-- Comment-out colorbars <subscription> <videoSource>SMPTE Color Bars Bitmap (No decode)</videoSource> <active>false</active> </subscription> --> </subscriptions> </subscriptionPackage> </subscriptionPackages> <!-- ***************************************************** --> <!-- applicationSettings - application-specific settings --> <!-- ***************************************************** --> <applicationSettings> <caption>Camera Diagnostics Video Display HCM</caption> <decoder> <!-- For better performance, set to max supported value of 4 on quad or dual-quad Intel CPUs --> <!-- Overall CPU usage is expected to be lower when set to max supported value of 4. --> <maxThreads>4</maxThreads> </decoder> <networking> <!-- Optional (for debug and test, Defaults to ttl=255 --> <multicastTtl>255</multicastTtl> <!-- Optional (for debug and test, Defaults to false --> <multicastLoopEnabled>true</multicastLoopEnabled> </networking> <!-- *************************************************************************************** --> <!-- videoSelectionStatus - Configuration for periodic multicast of video selection status. --> <!-- *************************************************************************************** --> <videoSelectionStatus> <!-- The multicast address and port to send video selection status. --> <uri>udp://239.255.255.61:50174</uri> <!-- Optional, Defaults to true --> <enabled>true</enabled> <!-- Optional, Defaults to using the IP address specified in the FesVideo constructor. <ethernet>bond0</ethernet> --> <!-- Optional, Defaults to 5 seconds --> <updateRateSeconds>1</updateRateSeconds> </videoSelectionStatus> </applicationSettings> </configuration> Resulting Warnings: ---------------------------- /home/esutton/projects/HCM_VideoAPI/libfesvideo/doc-src/api/pageConfiguration.doc:153: warning: unexpected token TK_EOF as the argument of ref Generating docs for page pageSequenceDiagramConnect... Generating docs for page pageExampleConfiguration... /home/esutton/projects/HCM_VideoAPI/libfesvideo/doc-src/api/pageExampleConfiguration.doc:15: warning: Unsupported xml/html tag <subscriptionPackages> found /home/esutton/projects/HCM_VideoAPI/libfesvideo/doc-src/api/pageExampleConfiguration.doc:18: warning: Unsupported xml/html tag <workstations> found /home/esutton/projects/HCM_VideoAPI/libfesvideo/doc-src/api/pageExampleConfiguration.doc:19: warning: Unsupported xml/html tag <videoSources> found /home/esutton/projects/HCM_VideoAPI/libfesvideo/doc-src/api/pageExampleConfiguration.doc:20: warning: Unsupported xml/html tag <subscriptionPackages> found -Ed -Ed > > Regards, > Dimitri > -Ed |
From: dougkramer <dou...@gm...> - 2014-11-06 01:56:24
|
Is there any way to completely turn off the interpretation of <tags> in doc comments? We don't use this feature, and would prefer not to litter the comments with backslashes. -- View this message in context: http://doxygen.10944.n7.nabble.com/How-to-prevent-warning-Unsupported-xml-html-tag-myTagName-found-tp138p6893.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |