X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/9715cf42b38d8a85e6124406a73b33f1b84b111a..328a3a009fd86bb7df6efc4e0086074af34846ab:/docs/doxygen/overviews/nonenglish.h

diff --git a/docs/doxygen/overviews/nonenglish.h b/docs/doxygen/overviews/nonenglish.h
index fbbd4143ba..37fc8cae43 100644
--- a/docs/doxygen/overviews/nonenglish.h
+++ b/docs/doxygen/overviews/nonenglish.h
@@ -3,13 +3,24 @@
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // RCS-ID:      $Id$
-// Licence:     wxWindows license
+// Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 
-/*!
+/**
 
 @page overview_nonenglish Writing Non-English Applications
 
+
+@li @ref overview_nonenglish_locales
+@li @ref overview_nonenglish_strings
+@li @ref overview_nonenglish_fontmapping
+@li @ref overview_nonenglish_converting
+@li @ref overview_nonenglish_help
+
+
+<hr>
+
+
 This article describes how to write applications that communicate with the user
 in a language other than English. Unfortunately many languages use different
 charsets under Unix and Windows (and other platforms, to make the situation
@@ -91,9 +102,7 @@ Windows).
 How is this done? When you tell the wxLocale class to load a message catalog
 that contains a correct header, it checks the charset. The catalog is then
 converted to the charset used (see wxLocale::GetSystemEncoding and
-wxLocale::GetSystemEncodingName) by the user's operating system. This is the
-default behaviour of the wxLocale class; you can disable it by @b not passing
-@c wxLOCALE_CONV_ENCODING to wxLocale::Init.
+wxLocale::GetSystemEncodingName) by the user's operating system.
 
 
 @section overview_nonenglish_strings Non-English Strings or 8-bit Characters in Source
@@ -101,7 +110,7 @@ default behaviour of the wxLocale class; you can disable it by @b not passing
 By convention, you should only use characters without diacritics (i.e. 7-bit
 ASCII strings) for msgids in the source code and write them in English.
 
-If you port software to wxWindows, you may be confronted with legacy source
+If you port software to wxWidgets, you may be confronted with legacy source
 code containing non-English string literals. Instead of translating the strings
 in the source code to English and putting the original strings into message
 catalog, you may configure wxWidgets to use non-English msgids and translate to
@@ -112,7 +121,7 @@ English using message catalogs:
 @li Specify the source code language and charset as arguments to
     wxLocale::AddCatalog. For example:
     @code
-    locale.AddCatalog(_T("myapp"), wxLANGUAGE_GERMAN, _T("iso-8859-1"));
+    locale.AddCatalog(wxT("myapp"), wxLANGUAGE_GERMAN, wxT("iso-8859-1"));
     @endcode