Check wxDateTime components validity more rigorously.

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

diff --git a/docs/doxygen/overviews/mbconvclasses.h b/docs/doxygen/overviews/mbconvclasses.h
index 4dbb18b64c29bc580604891118704096157daa68..cd761c61cd41da6c3fb1fb767c807208e7032105 100644 (file)
--- a/docs/doxygen/overviews/mbconvclasses.h
+++ b/docs/doxygen/overviews/mbconvclasses.h
@@ -3,7 +3,7 @@
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // RCS-ID:      $Id$
-// Licence:     wxWindows license
+// Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 
 /**
@@ -51,6 +51,8 @@ unhindered through any traditional transport channels.
 
 @section overview_mbconv_string Background: The wxString Class
 
+@todo rewrite this overview; it's not up2date with wxString changes
+
 If you have compiled wxWidgets in Unicode mode, the wxChar type will become
 identical to wchar_t rather than char, and a wxString stores wxChars. Hence,
 all wxString manipulation in your application will then operate on Unicode