Name change replacements

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@27090 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2004-05-04 08:27:20 +00:00
parent e119d0498a
commit fc2171bd4c
268 changed files with 1372 additions and 1366 deletions

View File

@@ -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
@@ -49,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.