wxHSCROLL works in GTK2, changed description to indicate no effect only on wxGTK1

[wxWidgets.git] / docs / latex / wx / ti18n.tex

diff --git a/docs/latex/wx/ti18n.tex b/docs/latex/wx/ti18n.tex
index 7cfb9532c76ebfee6be8e241151c74eb675bb13a..aaaf06add4777b8dee78c7278c9af95d79f3371a 100644 (file)
--- a/docs/latex/wx/ti18n.tex
+++ b/docs/latex/wx/ti18n.tex
@@ -4,15 +4,15 @@ Although internationalization of an application (i18n for short) involves far
 more than just translating its text messages to another message -- date, time and
 currency formats need changing too, some languages are written left to right
 and others right to left, character encoding may differ and many other things
-may need changing too -- it is a necessary first step. wxWindows provides
+may need changing too -- it is a necessary first step. wxWidgets provides
 facilities for message translation with its 
 \helpref{wxLocale}{wxlocale} class and is itself fully translated into several
-languages. Please consult wxWindows home page for the most up-to-date
+languages. Please consult wxWidgets home page for the most up-to-date
 translations - and if you translate it into one of the languages not done
 yet, your translations would be gratefully accepted for inclusion into the
 future versions of the library!
 
-The wxWindows approach to i18n closely follows GNU gettext package. wxWindows uses the
+The wxWidgets approach to i18n closely follows GNU gettext package. wxWidgets uses the
 message catalogs which are binary compatible with gettext catalogs and this
 allows to use all of the programs in this package to work with them. But note
 that no additional libraries are needed during the run-time, however, so you
@@ -31,14 +31,16 @@ The program i18n involves several steps:
 
 \begin{enumerate}\itemsep=0pt
 \item Translating the strings in the program text using 
-\helpref{wxGetTranslation}{wxgettranslation} or equivalently the \_() macro.
+\helpref{wxGetTranslation}{wxgettranslation} or equivalently the 
+\helpref{\_()}{underscore} macro.
 \item Extracting the strings to be translated from the program: this uses the
-work done in the previous step because {\it xgettext} program used for string
-extraction may be told (using its -k option) to recognise \_() and
-wxGetTranslation and extract all strings inside the calls to these functions.
-Alternatively, you may use -a option to extract all the strings, but it will
-usually result in many strings being found which don't have to be translated at
-all. This will create a text message catalog - a .po file.
+work done in the previous step because {\tt xgettext} program used for string
+extraction recognises the standard \_() as well as (using its {\tt -k} option)
+our wxGetTranslation and extracts all strings inside the calls to these
+functions. Alternatively, you may use {\tt -a} option to extract all the
+strings, but it will usually result in many strings being found which don't
+have to be translated at all. This will create a text message catalog -- a .po
+file.
 \item Translating the strings extracted in the previous step to other
 language(s). It involves editing the .po file.
 \item Compiling the .po file into .mo file to be used by the program.
@@ -47,7 +49,7 @@ given language: see \helpref{wxLocale}{wxlocale}.
 \end{enumerate}
 
 See also the GNU gettext documentation linked from {\tt docs/html/index.htm} in
-your wxWindows distribution.
+your wxWidgets distribution.
 
 See also \helpref{Writing non-English applications}{nonenglishoverview}.
 It focuses on handling charsets related problems.