*** 22th March 2000: wxWindows 2.1.15 released ***
-Build fix. RPMs no loner require GTK's include files.
+Build fix. RPMs no longer require GTK's include files.
An extra library for the OpenGl class now gets built
*** 19th March 2000: wxWindows 2.1.14 released ***
it normally should be, being succinct, cryptic, or otherwise ambiguous.
Before choosing how to translate the string, she needs to understand
better what the string really means and how tight the translation has
-to be. Most of times, when problems arise, the only way left to make
+to be. Most of the time, when problems arise, the only way left to make
her judgment is looking at the true program sources from where this
string originated, searching for surrounding comments the programmer
might have put in there, and looking around for helping clues of
hints she needs. She will learn quickly to not feel uncomfortable
in program code, paying more attention to programmer's comments,
variable and function names (if he dared choosing them well), and
-overall organization, than to programmation itself.
+overall organization, than to the program code itself.
</P>
<P>
\wxhelpref{wxScrollBar}{wxscrollbar}, \wxhelpref{wxSlider}{wxslider},and \wxhelpref{wxSpinButton}{wxspinbutton}.}
\twocolitem{\wxhelpref{wxSizeEvent}{wxsizeevent}}{The EVT\_SIZE macro is used to handle a window resize.}
\twocolitem{\wxhelpref{wxSplitterEvent}{wxsplitterevent}}{The EVT\_SPLITTER\_SASH\_POS\_CHANGED, EVT\_SPLITTER\_UNSPLIT
-and EVT\_SPLITTER\_DOUBLECLICKED macros are used to handle the various splitter window events.}
+and EVT\_SPLITTER\_DCLICK macros are used to handle the various splitter window events.}
\twocolitem{\wxhelpref{wxSysColourChangedEvent}{wxsyscolourchangedevent}}{The EVT\_SYS\_COLOUR\_CHANGED macro is used to handle
events informing the application that the user has changed the system colours (Windows only).}
\twocolitem{\wxhelpref{wxTreeEvent}{wxtreeevent}}{These macros handle \wxhelpref{wxTreeCtrl}{wxtreectrl} events.}
\twocolitem{{\bf EVT\_SPLITTER\_UNSPLIT(id, func)}}{The splitter has been just
unsplit. Processes a wxEVT\_COMMAND\_SPLITTER\_UNSPLIT event. This event can't
be vetoed.}
-\twocolitem{{\bf EVT\_SPLITTER\_DOUBLECLICKED(id, func)}}{The sash was double
+\twocolitem{{\bf EVT\_SPLITTER\_DCLICK(id, func)}}{The sash was double
clicked. The default behaviour is to unsplit the window when this happens
(unless the minimum pane size has been set to a value greater than zero). This
won't happen if you veto this event. Processes a
Processes a wxEVT\_COMMAND\_SPLITTER\_SASH\_POS\_CHANGED event.}
\twocolitem{{\bf EVT\_SPLITTER\_UNSPLIT(id, func)}}{The splitter has been just
unsplit. Processes a wxEVT\_COMMAND\_SPLITTER\_UNSPLIT event.}
-\twocolitem{{\bf EVT\_SPLITTER\_DOUBLECLICKED(id, func)}}{The sash was double
+\twocolitem{{\bf EVT\_SPLITTER\_DCLICK(id, func)}}{The sash was double
clicked. The default behaviour is to unsplit the window when this happens
(unless the minimum pane size has been set to a value greater than zero).
Processes a wxEVT\_COMMAND\_SPLITTER\_DOUBLECLICKED event.}
\helpref{wxScrollBar}{wxscrollbar}, \helpref{wxSlider}{wxslider},and \helpref{wxSpinButton}{wxspinbutton}.}
\twocolitem{\helpref{wxSizeEvent}{wxsizeevent}}{The EVT\_SIZE macro is used to handle a window resize.}
\twocolitem{\helpref{wxSplitterEvent}{wxsplitterevent}}{The EVT\_SPLITTER\_SASH\_POS\_CHANGED, EVT\_SPLITTER\_UNSPLIT
-and EVT\_SPLITTER\_DOUBLECLICKED macros are used to handle the various splitter window events.}
+and EVT\_SPLITTER\_DCLICK macros are used to handle the various splitter window events.}
\twocolitem{\helpref{wxSysColourChangedEvent}{wxsyscolourchangedevent}}{The EVT\_SYS\_COLOUR\_CHANGED macro is used to handle
events informing the application that the user has changed the system colours (Windows only).}
\twocolitem{\helpref{wxTreeEvent}{wxtreeevent}}{These macros handle \helpref{wxTreeCtrl}{wxtreectrl} events.}
1. GNU gettext package version 0.10.35 or later (NB: earlier versions were
known to have serious bugs)
- a) for Unix systems you can download gettext-0.10.tar.gz from any of GNU
- mirrors (RPMs and DEBs are also available from the usual places)
+ a) for Unix systems you can download gettext-0.10.tar.gz from any GNU
+ mirror (RPMs and DEBs are also available from the usual places)
- b) for Windows you can grab the precompiled binaries from www.wxwindows.org
+ b) for Windows you can download the precompiled binaries from
+ www.wxwindows.org
2. A way to run a program recursively on an entire directory from the command
line:
- a) for Unix systems, this is done in locale/Makefile using standard find
- command and xargs which is installed on almost all modern Unices, if you
- are unhappy enough to not have it you can use -exec option of find
+ a) for Unix systems, this is done in locale/Makefile using the standard find
+ command and xargs which is installed on almost all modern Unices. If you
+ are unlucky enough to not have xargs, you can use the -exec option of find
instead.
b) for Win32 systems this is less trivial: if you have 4DOS/4NT/bash, that's
1. the strings to translate are extracted from the C++ sources using xgettext
program into a wxstd.po file which is a "text message catalog"
-2. this new wxtd.po file (recreated each one some new text messages are added
+2. this new wxstd.po file (recreated each time some new text messages are added
to wxWindows) is merged with existing translations in another .po file (for
example, de.po) and replaces this file (this is done using the program
msgmerge)
4. finally, msgformat must be run to produce a .mo file: "binary message catalog"
-How does it happen in practice? Under Unix there is a Makefile under "locale"
+How does it happen in practice? Under Unix there is a Makefile in the "locale"
directory which will do almost everything (except translations) for you, i.e.
just type "make lang.po" to create or update the message catalog for 'lang'.
Then edit the resulting lang.po and make sure that there are no empty or fuzzy
-translations left (empty translations are the one with msgstr "", fuzzy
+translations left (empty translations are the ones with msgstr "", fuzzy
translations are those which have the word "fuzzy" in a comment just above
them). Then type "make lang.mo" which will create the binary message catalog.
Version: $Id$
$Log$
+Revision 1.2 2002/07/03 15:01:26 VZ
+typos and other doc corrections from Olly Betts (patch 573738)
+
Revision 1.1 2000/03/07 10:53:53 VZ
technote about translations added
create a new .tex file, e.g. myclass.tex, and add it to the
list of classes in classes.tex (in strict alphabetical order).
You may also want to write a separate topic file, e.g. tmyclass.tex,
-and add the entry to topics.tex. Also, if applicable, and an entry
+and add the entry to topics.tex. If applicable, also add an entry
to category.tex.
If compiling a separate manual, copy an existing set of files from the
<h2>
Before you begin</h2>
-This refers to the 2.1.15 wxWindows distribution. It is my account of trying
-to compile the samples so I can use the Borland IDE to edit/compile/debug.
-I have used CBuilder 1.00 (2 patches, nice and fast) CBuilder 3 (slower)
-and CBuilder 4 (only occasionally)
+This refers to the <b>2.1.16</b> and 2.1.15 wxWindows distribution. It
+is my account of trying to compile the samples so I can use the Borland
+IDE to edit/compile/debug. I have used CBuilder 1.00 (2 patches, nice and
+fast), CBuilder 3 (slower), and CBuilder 4 (more recently).
+
<p>Make sure that the wx distribution is extracted to a path with no spaces
in it, and preferably on the root of your drive. Borland's compilers sometimes
have problems with spaces and with the long paths which occur if you try
<p><tt>set wxwin=pathtowx</tt>
<br><tt>set bccdir=pathtobc4</tt>
<br><tt>make -f makefile.b32</tt>
-<p>In my case this I extracted the wx distribution in <b>c:\ </b>and the
-compiler is in <b>w:\borland\cb\bin </b>so this looks:
+<p>In my case this I extracted the wx distribution in <b>c:\</b> and the
+compiler is in <b>w:\borland\cb\bin</b> so this looks:
<p><tt>set wxwin=c:\wx</tt>
<br><tt>set bccdir=w:\borland\cb</tt>
<br><tt>make -f makefile.b32</tt>
<p>If this doesn't <b>compile</b>,
<ul>
<li>
-you've probably got the <b><tt>set wxwin </tt></b>command wrong,</li>
+you've probably got the <b><tt>set wxwin</tt></b> command wrong,</li>
<li>
or the path was not set by the Borland setup</li>
If this doesn't <b>link</b>,
<ul>
<li>
-you've probably got the <b><tt>set bccdir </tt></b>command wrong</li>
+you've probably got the <b><tt>set bccdir</tt></b> command wrong</li>
</ul>
<hr WIDTH="100%">
<h3>
Solution 1</h3>
-<h4>
<a href="http://biolpc22.york.ac.uk/wx/bc/download.html">Download</a> a zip file which contains modified
-cpp, mak and bpr files - it will overwrite your wx distribution cpp files!</h4>
+cpp, mak and bpr files - it will overwrite your wx distribution cpp files!
-<h4>
-Solution 2</h4>
-Creating the files by hand . This is for the calendar sample; you will
+<h3>
+Solution 2</h3>
+Creating the files by hand. This is for the calendar sample; you will
have to change the names for the other samples
<ul>
<li>
Create a calendar.mak file [must have the same name as the cpp file] in
-a plain text editor with <a href="http://biolpc22.york.ac.uk/wx/bc/calendar.mak">this contents</a></li>
+a plain text editor with <a href="http://biolpc22.york.ac.uk/wx/bc/calendar.mak">these contents</a></li>:
</ul>
<tt>#-----------------------------------------------------------------------------</tt>
<br><tt>#this is for Borland CBuilder IDE v1 and 3</tt>
<br>
<ul>
<li>
- modify the .cpp file to include these<a href="http://biolpc22.york.ac.uk/wx/bc/calendar_include.cpp">
-lines </a>near the top</li>
+ modify the .cpp file to include
+<a href="http://biolpc22.york.ac.uk/wx/bc/calendar_include.cpp">these lines</a>
+near the top</li>
</ul>
<tt>#ifdef __BIDE__</tt>
<br><tt>#define _NO_VCL</tt>
<br>
<p>In CBuilder 1 you can use <b>Open Project</b> to open the mak file and
edit/compile/debug.
-<br>In CBuilder 3 and 4, then you can use <b>Open Project </b>and choose
+<p>In CBuilder 3 and 4, then you can use <b>Open Project</b> and choose
the Open Borland CBuilder 1 Project from the drop down file types. The
system will modify the mak file and update it for you.
<p>Now try compiling it in the ide.
<ul>
<li>
-You can set it up for normal and debug modes (change the -v switch in CFLAG1
+You can set it up for normal and debug modes (change the -v switch in CFLAG1
and LFLAG)</li>
<li>
in CBuilder 1.00 with Unix style line endings)</li>
<li>
-If you want to avoid the warnings about hiding virtual methods add <b><tt>-w-hid
-</tt></b>to the CFLAGS1 line</li>
+If you want to avoid the warnings about hiding virtual methods add
+<b><tt>-w-hid</tt></b> to the CFLAG1 line</li>
<li>
the #define WinMain WinMain line allows CBuilder to think it has a non-VCL
-<tt>main </tt>function</li>
+<tt>main</tt> function</li>
<li>
the USEUNIT macros tell CBuilder which other source files to include, without
<ul>
<li>
-download the wxWindows-2.1.15-bcb.zip file,</li>
+download the wxWindows-2.1.16-bcb.zip file,</li>
<li>
extract it</li>
<li>
-use the <b><tt>idetomak</tt></b> (CBuilder 1) or <b><tt>idetobpr</tt></b>
+use the <b><tt>idetomak</tt></b> (CBuilder 1) or <b><tt>idetobpr</tt></b>
(CBuilder 3/4) utility on the <b><tt>.ide</tt></b> file in the samples
-directory. This modifies the cpp source and makes a "suitable" bpr file
+directory. This modifies the cpp source and makes a "suitable" mak or bpr file
(at least in CBuilder 1/3/4).</li>
<li>
-add the location of the wx/include files in the project | options
+add the location of the wx/include files in the project | options
| directory dialog</li>
</ul>
I found in CBuilder 1 that the <tt>idetomak</tt> utility did not manage
<h2>
Error with ODBC32</h2>
Sometimes you get an error saying that there are unresolved externals in
-ODBC. The solution is to run a command prompt in your <b><tt>wx\lib </tt></b>directory
-and use the <b><tt>implib </tt></b>command:
-<p><tt>C:\wx\lib><b>implib odbc32 c:\windows\system\odbc32.dll</b></tt>
+ODBC. The solution is to run a command prompt in your <b><tt>wx\lib</tt></b> directory
+and use the <b><tt>implib</tt></b> command:
+<p><tt>C:\wx\lib><b>implib odbc32 c:\windows\system\odbc32.dll</b></tt>
<p>This creates the necessary library, odbc32.lib
<h2>
Unresolved Problem</h2>
-<tt>In Borland CBuilder 1.00 (with linker service patch) I frequently
+<tt>In Borland CBuilder 1.00 (with linker service patch) I frequently
get an error</tt>
<p><tt>Turbo Incremental Link Version 1.0 Copyright (c) 1997 Borland
International</tt>
<br><tt>Fatal: Access violation. Program terminated.</tt>
<p><tt>** error 2 ** deleting minimal.exe</tt>
<p>I have not been able to track down why sometimes this error occurs and
-other times it is OK
-<br>I have not seen this in Cbuilder 3 or 4
+other times it is OK. I have not seen this in Cbuilder 3 or 4.
<p>
<hr WIDTH="100%">
<p>Page updated on 31 May 2000 by Chris Elliott
projects / wxWidgets.git / commitdiff
