added wxEncodingToCodepage() and implemented it properly (using in32 API instead...

[wxWidgets.git] / docs / wxQt.html

diff --git a/docs/wxQt.html b/docs/wxQt.html
index 9fd51dc7fdc17a4375e7a237c071e78ca57d45c0..87f70136945ac523539faa024d8feb93a8b1fd34 100644 (file)
--- a/docs/wxQt.html
+++ b/docs/wxQt.html
@@ -52,12 +52,15 @@
       Please, join us in this effort and, if you feel that you could
       contribute, join the wxWindows developers mailing list for further
       discussions. Just send a mail containing "<tt>subscribe</tt>" to
-    <tt>wxwin-developers-request@x.dent.med.uni-muenchen.de</tt>
+    <tt>wxwin-developers-request@wx.dent.med.uni-muenchen.de</tt>
     <p>
       You can find some more information about wxWindows at the following places:
 <ul>
 <li>The <a href="http://web.ukonline.co.uk/julian.smart/wxwin/">wxWindows homepage</a>.
 <li>The <a href="http://www.freiburg.linux.de/~wxxt/">wxGTK homepage</a>
+<li>The <a
+         href="http://Ballueder.home.ml.org/wxWindows/wxQt.html">wxQt
+         proposal</a>(this text)
 <li>The <a href="http://Ballueder.home.ml.org/M/">home of <em>M</em></a>, an email client developed using wxGTK, showing several <a href="http://Ballueder.home.ml.org/M/screenshots/">screenshots</a> of how it actually looks like.
 </ul>
 <p>