X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/526954c5968baa29218c994ec48e476ae2bd4b9f..4e15d1caa03346c126015019c1fdf093033ef40b:/docs/doxygen/overviews/nonenglish.h?ds=inline

diff --git a/docs/doxygen/overviews/nonenglish.h b/docs/doxygen/overviews/nonenglish.h
index 3cd30380e4..dd2e04d70e 100644
--- a/docs/doxygen/overviews/nonenglish.h
+++ b/docs/doxygen/overviews/nonenglish.h
@@ -10,16 +10,7 @@
 
 @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>
-
+@tableofcontents
 
 This article describes how to write applications that communicate with the user
 in a language other than English. Unfortunately many languages use different
@@ -39,6 +30,7 @@ In the following text, wherever @e iso8859-2 and @e windows-1250 are used, any
 encodings are meant and any encodings may be substituted there.
 
 
+
 @section overview_nonenglish_locales Locales
 
 The best way to ensure correctly displayed texts in a GUI across platforms is
@@ -110,7 +102,7 @@ wxLocale::GetSystemEncodingName) by the user's operating system.
 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
@@ -174,4 +166,3 @@ This additional entry tells the HTML help controller what encoding is used in
 contents and index tables.
 
 */
-