From: Vadim Zeitlin Date: Wed, 3 Jul 2002 15:01:26 +0000 (+0000) Subject: typos and other doc corrections from Olly Betts (patch 573738) X-Git-Url: https://git.saurik.com/wxWidgets.git/commitdiff_plain/552861bf308cf2fd12f786a5443d379b55f63d81 typos and other doc corrections from Olly Betts (patch 573738) git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@16016 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- diff --git a/docs/gtk/changes.txt b/docs/gtk/changes.txt index 677fda1299..5866bf65b0 100644 --- a/docs/gtk/changes.txt +++ b/docs/gtk/changes.txt @@ -282,7 +282,7 @@ MANY bugfixes. *** 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 *** diff --git a/docs/html/gettext/gettext_4.html b/docs/html/gettext/gettext_4.html index f91b6bd17c..72b1a78791 100644 --- a/docs/html/gettext/gettext_4.html +++ b/docs/html/gettext/gettext_4.html @@ -207,7 +207,7 @@ often faced with an original string which is not as informative as 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 @@ -223,7 +223,7 @@ It is most probable that she will still be able to find some of the 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.

diff --git a/docs/latex/book/chap_basic_events.tex b/docs/latex/book/chap_basic_events.tex index dfa56b2b77..bcb9587faf 100644 --- a/docs/latex/book/chap_basic_events.tex +++ b/docs/latex/book/chap_basic_events.tex @@ -342,7 +342,7 @@ mouse events or all mouse events.} \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.} diff --git a/docs/latex/wx/splitevt.tex b/docs/latex/wx/splitevt.tex index a3ba5731f0..7cf2b96e93 100644 --- a/docs/latex/wx/splitevt.tex +++ b/docs/latex/wx/splitevt.tex @@ -38,7 +38,7 @@ 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. 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 diff --git a/docs/latex/wx/splitter.tex b/docs/latex/wx/splitter.tex index 5defafa745..b37d1b73eb 100644 --- a/docs/latex/wx/splitter.tex +++ b/docs/latex/wx/splitter.tex @@ -55,7 +55,7 @@ it is set, or to prevent the change from taking place. 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.} diff --git a/docs/latex/wx/tevent.tex b/docs/latex/wx/tevent.tex index ed4760d0fc..f58d767d67 100644 --- a/docs/latex/wx/tevent.tex +++ b/docs/latex/wx/tevent.tex @@ -363,7 +363,7 @@ mouse events or all mouse events.} \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.} diff --git a/docs/tech/tn0002.txt b/docs/tech/tn0002.txt index e508423a1f..29ef40af71 100644 --- a/docs/tech/tn0002.txt +++ b/docs/tech/tn0002.txt @@ -8,17 +8,18 @@ First of all, here is what you will need: 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 @@ -35,7 +36,7 @@ gettext documentation for more details). It happens in several steps: 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) @@ -45,11 +46,11 @@ gettext documentation for more details). It happens in several steps: 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. @@ -62,6 +63,9 @@ Author: VZ 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 diff --git a/docs/tech/tn0003.txt b/docs/tech/tn0003.txt index 738a1b7d46..7a79f3859b 100644 --- a/docs/tech/tn0003.txt +++ b/docs/tech/tn0003.txt @@ -14,7 +14,7 @@ If adding to the existing manual in docs/latex/wx, you need to 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 diff --git a/docs/tech/tn0004.htm b/docs/tech/tn0004.htm index d3cd6d6f4d..ea58c4fd56 100644 --- a/docs/tech/tn0004.htm +++ b/docs/tech/tn0004.htm @@ -15,10 +15,11 @@ This document is available online @@ -56,18 +57,17 @@ To make the samples

Solution 1

-

Download a zip file which contains modified -cpp, mak and bpr files - it will overwrite your wx distribution cpp files!

+cpp, mak and bpr files - it will overwrite your wx distribution cpp files! -

-Solution 2

-Creating the files by hand . This is for the calendar sample; you will +

+Solution 2

+Creating the files by hand. This is for the calendar sample; you will have to change the names for the other samples #-----------------------------------------------------------------------------
#this is for Borland CBuilder IDE v1 and 3 @@ -112,8 +112,9 @@ jpeg.lib for image samples
  #ifdef __BIDE__
#define _NO_VCL @@ -126,7 +127,7 @@ if you have more than one .cpp file
 

In CBuilder 1 you can use Open Project to open the mak file and edit/compile/debug. -
In CBuilder 3 and 4, then you can use Open Project and choose +

In CBuilder 3 and 4, then you can use Open Project 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.

Now try compiling it in the ide. @@ -135,7 +136,7 @@ Hints: