removed wxAcceleratorTable copy ctor docs, no port implements it

[wxWidgets.git] / docs / doxygen / overviews / html.h

diff --git a/docs/doxygen/overviews/html.h b/docs/doxygen/overviews/html.h
index 621054c4aea37fe6b0262c6ac950b07b5fca2b53..a96a296d3c723a4281ba3a1c225d07c2ac10cd12 100644 (file)
--- a/docs/doxygen/overviews/html.h
+++ b/docs/doxygen/overviews/html.h
@@ -6,13 +6,13 @@
 // Licence:     wxWindows license
 /////////////////////////////////////////////////////////////////////////////
 
-/*!
+/**
 
- @page overview_html wxHTML overview
+ @page overview_html wxHTML Overview
 
  The wxHTML library provides classes for parsing and displaying HTML.
  It is not intended to be a high-end HTML browser. If you are looking for
- something like that try http://www.mozilla.org.
+ something like that try <http://www.mozilla.org/>.
 
  wxHTML can be used as a generic rich text viewer - for example to display
  a nice About Box (like those of GNOME apps) or to display the result of
@@ -106,7 +106,7 @@
  @section overview_html_printing HTML Printing
 
  The wxHTML library provides printing facilities with several levels of complexity.
- The easiest way to print an HTML document is to use @ref overview_htmleasyprinting. 
+ The easiest way to print an HTML document is to use the wxHtmlEasyPrinting class.
 
  It lets you print HTML documents with only one command and you don't have to worry
  about deriving from the wxPrintout class at all. It is only a simple wrapper around the
@@ -244,8 +244,10 @@
 
  Container is kind of cell that may contain sub-cells. Its size depends
  on number and sizes of its sub-cells (and also depends on width of window).
- See wxHtmlContainerCell, wxHtmlCell::Layout.
- This image shows the cells and containers: @image html contbox.bmp
+ See wxHtmlContainerCell, wxHtmlCell::Layout. This image shows the cells and
+ containers:
+
+ @image html overview_html_contbox.png
 
  @subsection overview_html_cells_conttaghandler Using Containers in Tag Handler
 
@@ -259,8 +261,9 @@
 
  Use wxHtmlWinParser::CloseContainer to close the container. 
  This doesn't create a new container with same depth level but it returns "control"
- to the parent container.
- See explanation: @image html cont.bmp
+ to the parent container. See explanation:
+
+ @image html overview_html_cont.png
 
  There clearly must be same number of calls to OpenContainer as to
  CloseContainer.
@@ -281,7 +284,9 @@
  m_WParser -> OpenContainer();
  @endcode
 
- and here is image of the situation: @image html hello.bmp
+ and here is image of the situation:
+
+ @image html overview_html_hello.png
 
  You can see that there was an opened container before the code was executed.
  We closed it, created our own container, then closed our container and opened