\begin{enumerate}\itemsep=0pt
\item Translating the strings in the program text using
\helpref{wxGetTranslation}{wxgettranslation} or equivalently the
-\helpref{\_()}{underscore} and \helpref{ngettext}{ngettext} macros.
+\helpref{\_()}{underscore} macro.
\item Extracting the strings to be translated from the program: this uses the
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)
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
your wxWidgets distribution.