Could you consider making the output line numbers for <b> and </b> warnings
less ambiguous in your next software release? I've noted the following issues
in the warning messages:
1: missing </b>. The line number is never correct. Most often it is a random
number greater
than the last line of the file. If there are more than one missing </b>
warnings in the file,
then each warning contains a line number greater than the previous one.
2: missing <b>. The line numbers are often correct (indicating where the </b>
was found)
but just as often incorrect.
And could you flag nested <b> blocks with a warning, as in <b>text<b>
<b>text</b>?
For 1: above, it would be nice to issue a message which shows the line number
of the
unmatched <b> tag.
For 2: above, it would be nice to always output the address of the detected
</b>.
And for the nested <b> blocks, it would be nice to output the line number of
each
nested <b> found.
As always, great work.
Thanks
art
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
