Some doc corrections

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_2_BRANCH@7247 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2000-04-23 15:53:30 +00:00
parent 4f0a1b07e6
commit 3049cbeb6a
9 changed files with 130 additions and 120 deletions

View File

@@ -21,7 +21,7 @@ in use.
\subsection{Background: The need for conversion}
As programs are becoming more and more globalized, and user exchange documents
As programs are becoming more and more globalized, and users exchange documents
across country boundaries as never before, applications increasingly need to
take into account all the different character sets in use around the world. It
is no longer enough to just depend on the default byte-sized character set that
@@ -33,7 +33,7 @@ it would resolve the character set problems once and for all.
But it hasn't happened yet, and the migration towards Unicode has created new
challenges, resulting in "compatibility encodings" such as UTF-8. A large
amount of systems out there still depends on the old 8-bit encodings, hampered
number of systems out there still depends on the old 8-bit encodings, hampered
by the huge amounts of legacy code still widely deployed. Even sending
Unicode data from one Unicode-aware system to another may need encoding to an
8-bit multibyte encoding (UTF-7 or UTF-8 is typically used for this purpose), to
@@ -51,7 +51,7 @@ literals).
But often, your environment doesn't want Unicode strings. You could be sending
data over a network, or processing a text file for some other application. You
need a way to quickly convert your easily-handled Unicode data to and from a
traditional 8-bit-encoding. And this is what the wxMBConv classes does.
traditional 8-bit-encoding. And this is what the wxMBConv classes do.
\subsection{wxMBConv classes}