AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

wxLocale-related corrections to the docs

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@14620 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Václav Slavík 2002-03-15 23:29:22 +00:00
parent f35992b0f5
commit ae71a6e890
2 changed files with 10 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/latex/wx/locale.tex
View File

@ -513,10 +513,10 @@ language (see \helpref{GetSystemLanguage}{wxlocalegetsystemlanguage}).}
for the given locale containing the translations of standard wxWindows messages for the given locale containing the translations of standard wxWindows messages
automatically.} automatically.}
\twocolitem{\windowstyle{wxLOCALE\_CONV\_ENCODING}}{Automatically convert message \twocolitem{\windowstyle{wxLOCALE\_CONV\_ENCODING}}{Automatically convert message
catalogs to platform's native encoding. Note that it will do only basic catalogs to platform's default encoding. Note that it will do only basic
conversion between well-known pair like iso8859-1 and windows-1252 or conversion between well-known pair like iso8859-1 and windows-1252 or
iso8859-2 and windows-1250. See \helpref{Writing non-English applications}{nonenglishoverview} for detailed iso8859-2 and windows-1250. See \helpref{Writing non-English applications}{nonenglishoverview} for detailed
description of this behaviour.} description of this behaviour. Note that this flag is meaningless in Unicode build.}
\end{twocollist} \end{twocollist}
} }

23
docs/latex/wx/tnoneng.tex
View File

@ -44,7 +44,7 @@ msgstr ""
"Content-Transfer-Encoding: ENCODING\n" "Content-Transfer-Encoding: ENCODING\n"
\end{verbatim} \end{verbatim}
Notice this particular line: Note this particular line:
\begin{verbatim} \begin{verbatim}
"Content-Type: text/plain; charset=CHARSET\n" "Content-Type: text/plain; charset=CHARSET\n"
@ -80,20 +80,13 @@ wxWindows is able to use this catalog under any supported platform
Windows). Windows).
How is this done? When you tell the wxLocale class to load a message catalog that How is this done? When you tell the wxLocale class to load a message catalog that
contains correct header, it checks the charset. If the contains correct header, it checks the charset. The catalog is then converted
charset is "alien" on the platform the program is currently running (e.g. to the charset used (see
any of ISO encodings under Windows or CP12XX under Unix) it uses \helpref{wxLocale::GetSystemEncoding}{wxlocalegetsystemencoding} and
\helpref{wxEncodingConverter::GetPlatformEquivalents}{wxencodingconvertergetplatformequivalents} \helpref{wxLocale::GetSystemEncodingName}{wxlocalegetsystemencodingname}) by
to obtain an encoding that is more common on this platform and converts user's operating system. This is default behaviour of the
the message catalog to this encoding. Note that it does {\bf not} check \helpref{wxLocale}{wxlocale} class; you can disable it by {\bf not} passing
for presence of fonts in the "platform" encoding! It only assumes that it is {\tt wxLOCALE\_CONV\_ENCODING} to \helpref{wxLocale::Init}{wxlocaleinit}.
always better to have strings in platform native encoding than in an encoding
that is rarely (if ever) used.
The behaviour described above is disabled by default.
You must set {\it bConvertEncoding} to TRUE in
\helpref{wxLocale constructor}{wxlocaledefctor} in order to enable
runtime encoding conversion.
\wxheading{Font mapping} \wxheading{Font mapping}