+<hr>
+<center>
+<font size=+2><i><b><a name="howtohelp">How to help</a></b></i></font>
+</center>
+<hr>
+
+<p>
+wxWindows uses the standard GNU gettext tools for i18n so if you are already
+familiar with them you shouldn't have any problems with working on wxWindows
+translations. Here are the the steps you should follow:
+<ol>
+ <li>Get the latest version of the file <tt>locale/wxstd.po</tt> from the
+ wxWindows source tree: if you're using <a href="cvs.htm">cvs</a>
+ or the <a href="http://wxwindows.sf.net/snapshots/">daily snapshots</a>,
+ you should already have it. Otherwise you can always
+ retrieve it directly from the cvs repository via the Web interface
+ <a href="http://cvs.wxwindows.org/viewcvs.cgi/wxWindows/locale/wxstd.po">here</a>.
+
+ <li>Rename it to <tt>XY.po</tt> where <tt>"XY"</tt> is the 2 letter
+ <a href="http://lcweb.loc.gov/standards/iso639-2/englangn.html">ISO 639-1 language code</a>
+ for your language.
+
+ <li>Translate the strings in this file using either your favourite text
+ editor or a specialized tool such as Vaclav Slavik's excellent
+ <a href="http://poedit.sourceforge.net/" target=_top>poEdit</a>
+ utility.
+
+ <li>Verify that your translations can at least be compiled (even if they
+ are yet incomplete) by running <tt>msgfmt -v XY.po</tt> command:
+ please note that you <i>must</i> use the <tt>-v</tt> option. In
+ particular, please fill the header fields because msgfmt doesn't
+ accept the default values for them.
+
+ <li>Send the finished translation to
+ <a href="mailto:vadim@wxwindows.org">Vadim Zeitlin</a> and it will be
+ added to the next wxWindows release or snapshot.
+</ol>
+
+<p>
+In addition, please consider subscribing to the very low volume
+<a href="http://lists.wxwindows.org/mailman/listinfo/wx-translators">
+wxWindows translators</a> mailing list on which the news especially important
+for the translators are announced.
+
+<p>
+Thank you in advance for your help!
+