No real change.

[wxWidgets.git] / docs / tech / tn0002.txt

diff --git a/docs/tech/tn0002.txt b/docs/tech/tn0002.txt
index e508423a1fbbd49b40ce2657281093d162a353f6..29ef40af71a86393ecb8c1e25797d0e1155aca02 100644 (file)
--- 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