change wxTextValidator to use wxArrayString instead of wxStringList

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

diff --git a/docs/latex/wx/ti18n.tex b/docs/latex/wx/ti18n.tex
index 8aaca5348ebc7555123ed21caebec9faaa5a1ca1..d263cee5d1f82d19efefd12ebbc0ae1b86d18561 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
 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
 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!
 
 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
 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


@@ -48,8 +48,33 @@ language(s). It involves editing the .po file.
 given language: see \helpref{wxLocale}{wxlocale}.
 \end{enumerate}
 
 given language: see \helpref{wxLocale}{wxlocale}.
 \end{enumerate}
 

+If you want your app to run under MacOS X with internationlization as
+described above you'll need to make one modification to the Info.plist
+file which describes the contents of the "application bundle". This
+file (an XML text file in UTF-8 format) should have a
+CFBundleDevelopmentRegion entry describing the language of the developer
+- mostly English - and normally MacOS X will query the bundle for the
+presence of certain resource directories to find out which languages
+are supported (e.g. the directory German.lproj for German). 
+Since wxWidgets based applications don't use these directories
+for storing resource information (they store the translation in the
+mo files instead) the application needs to be told explicitly which
+langauges are supported. This is done by adding a CFBundleLocalizations
+entry to Info.plist. This can look like this:
+
+\begin{verbatim}
+       <key>CFBundleDevelopmentRegion</key>
+       <string>English</string>
+       <key>CFBundleLocalizations</key>
+       <array>
+               <string>en</string>
+               <string>de</string>
+               <string>fr</string>
+       </array>
+\end{verbatim}
+

 See also the GNU gettext documentation linked from {\tt docs/html/index.htm} in
 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.
 
 See also \helpref{Writing non-English applications}{nonenglishoverview}.
 It focuses on handling charsets related problems.