Fixed typos in the docs
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_2_BRANCH@6892 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -6,7 +6,7 @@
|
||||
%% Created: 03.11.99
|
||||
%% RCS-ID: $Id$
|
||||
%% Copyright: (c) Vadim Zeitlin
|
||||
%% Licence: wxWindows licence
|
||||
%% License: wxWindows license
|
||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||
|
||||
\section{Font encoding overview}\label{wxfontencodingoverview}
|
||||
@@ -16,7 +16,7 @@ By encoding we mean here the mapping between the character codes and the
|
||||
letters. Probably the most well-known encoding is (7 bit) ASCII one which is
|
||||
used almost universally now to represent the letters of the English alphabet
|
||||
and some other common characters. However, it is not enough to represent the
|
||||
letters of foreign alphabetes and here other encodings come into play. Please
|
||||
letters of foreign alphabets and here other encodings come into play. Please
|
||||
note that we will only discuss 8-bit fonts here and not
|
||||
\helpref{Unicode}{unicode}.
|
||||
|
||||
@@ -38,27 +38,28 @@ wxFONTENCODING\_SYSTEM, but may be changed to make all the fonts created later
|
||||
to use it (by default).}
|
||||
\twocolitem{wxFONTENCODING\_ISO8859\_1..15}{ISO8859 family encodings which are
|
||||
usually used by all non-Microsoft operating systems}
|
||||
\twocolitem{wxFONTENCODING\_KOI8}{Standard cyrillic encoding for the Internet
|
||||
\twocolitem{wxFONTENCODING\_KOI8}{Standard Cyrillic encoding for the Internet
|
||||
(but see also wxFONTENCODING\_ISO8859\_5 and wxFONTENCODING\_CP1251)}
|
||||
\twocolitem{wxFONTENCODING\_CP1250}{Microsoft analogue of ISO8859-2}
|
||||
\twocolitem{wxFONTENCODING\_CP1251}{Microsoft analogue of ISO8859-5}
|
||||
\twocolitem{wxFONTENCODING\_CP1252}{Microsoft analogue of ISO8859-1}
|
||||
\end{twocollist}
|
||||
|
||||
As you may see, Microsofts encoding partly mirror the standard ISO8859 ones,
|
||||
As you may see, Microsoft's encoding partly mirror the standard ISO8859 ones,
|
||||
but there are (minor) differences even between ISO8859-1 (Latin1, ISO encoding
|
||||
for Western Europe) and CP1251 (WinLatin1, standard code page for English
|
||||
versions of Windows) and there are more of them for other encodings.
|
||||
|
||||
The situation is particularly complicated with cyrillic encodings for which
|
||||
The situation is particularly complicated with Cyrillic encodings for which
|
||||
(more than) three incompatible encodings exist: KOI8 (the old standard, widely
|
||||
used on the Internet), ISO8859-5 (ISO standard for cyrillic) and CP1251
|
||||
used on the Internet), ISO8859-5 (ISO standard for Cyrillic) and CP1251
|
||||
(WinCyrillic).
|
||||
|
||||
This abundance of (incompatible) encodigns should make it clear that using
|
||||
This abundance of (incompatible) encoding:w
|
||||
s should make it clear that using
|
||||
encodings is less easy than it might seem. The problems arise both from the
|
||||
fact that the standard encodigns for the given language (say Russian, which is
|
||||
written in cyrillic) are different on different platforms and because the
|
||||
fact that the standard encodings for the given language (say Russian, which is
|
||||
written in Cyrillic) are different on differe nt platforms and because the
|
||||
fonts in the given encoding might just not be installed (this is especially a
|
||||
problem with Unix, or, in general, not Win32, systems).
|
||||
|
||||
|
Reference in New Issue
Block a user