This commit was manufactured by cvs2svn to create tag 'wxPy_2_3_3_1'.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/tags/wxPy_2_3_3_1@17271 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/latex/wx/tstring.tex

@@ -9,8 +9,8 @@ wxString is a class which represents a character string of arbitrary length (lim
 arbitrary characters. The ASCII NUL character is allowed, although care should be
 taken when passing strings containing it to other functions.
 
-wxString works with both ASCII (8 bit characters) as well as UNICODE (16 but
-characters) strings.
+wxString works with both ASCII (traditional, 7 or 8 bit, characters) as well as
+Unicode (wide characters) strings.
 
 This class has all the standard operations you can expect to find in a string class:
 dynamic memory management (string extends to accommodate new characters),
@@ -48,9 +48,10 @@ very useful but don't exist in most of other string classes: for example,
 \helpref{BeforeLast}{wxstringbeforelast}, \helpref{operator<<}{wxstringoperatorout} 
 or \helpref{Printf}{wxstringprintf}. Of course, all the standard string
 operations are supported as well.
-\item {\bf UNICODE} In this release, wxString only supports {\it construction} from
-a UNICODE string, but in the next one it will be capable of also storing its
-internal data in either ASCII or UNICODE format.
+\item {\bf Unicode} wxString is Unicode friendly: it allows to easily convert
+to and from ANSI and Unicode strings in any build mode (see the 
+\helpref{Unicode overview}{unicode} for more details) and maps to either
+{\tt string} or {\tt wstring} transparently depending on the current mode.
 \item {\bf Used by wxWindows} And, of course, this class is used everywhere
 inside wxWindows so there is no performance loss which would result from
 conversions of objects of any other string class (including std::string) to

docs/latex/wx/wizard.tex

@@ -134,9 +134,9 @@ also \helpref{GetBitmap}{wxwizardpagegetbitmap}.}
 \docparam{pos}{The position of the dialog, it will be centered on the screen
 by default.}
 
-\membersection{wxWizard::Fit}\label{wxwizardfit}
+\membersection{wxWizard::FitToPage}\label{wxwizardfittopage}
 
-\func{void}{Fit}{\param{const wxWizardPage* }{firstPage}}
+\func{void}{FittoPage}{\param{const wxWizardPage* }{firstPage}}
 
 Sets the page size to be big enough for all the pages accessible via the
 given {\it firstPage}, i.e. this page, its next page and so on.

docs/tech/tn0006.txt

@@ -0,0 +1,41 @@
+How to make RPMs of the wxWindows sources
+=========================================
+
+This is just a short description. It is assumed that you know what you are
+doing. I do not take any responsibility for damaged systems, use at your own
+risk!
+
+	1. Extract the archive in a temporary directory. Since you are
+	   reading this text, you already have done this.
+	2. Copy the .spec file to
+		(rpm-dir)/SPECS
+	3. Copy the .tgz file to
+		(rpm-dir)/SOURCES
+	4. Start the RPM manager with
+		rpm -bb (rpm-dir)/SPECS/(.spec-file)
+	   or with
+		rpm -ba (rpm-dir)/SPECS/(.spec-file)
+	   (the latter also builds the .src.rpm-file)
+	5. You now have a nice set of RPMs in (rpm-dir)/RPMS
+
+Example
+=======
+
+Here's how to install e.g. wxMotif 2.1.14:
+
+	cp wxMotif.spec /usr/src/packages/SPECS
+	cp wxMotif-2.1.14.tgz /usr/src/packages/SOURCES
+	rpm -bb /usr/src/packages/SPECS/wxMotif.spec
+
+Install the resulting packages with
+
+	rpm --install /usr/src/packages/RPMS/i386/wxMotif-2.1.14-0.i386.rpm
+	rpm --install /usr/src/packages/RPMS/i386/wxMotif-devel-2.1.14-0.i386.rpm
+	rpm --install /usr/src/packages/RPMS/i386/wxMotif-gl-2.1.14-0.i386.rpm
+
+
+
+That's all. You should now have a working wxWindows library.
+
+Regards,
+	Robert Fendt