Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

corrected outdated Unicode information

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@17247 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2002-09-18 14:48:56 +00:00
parent 2a32fcda98
commit 32742e5755
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/latex/wx/tstring.tex
View File

@@ -9,8 +9,8 @@ wxString is a class which represents a character string of arbitrary length (lim
arbitrary characters. The ASCII NUL character is allowed, although care should be arbitrary characters. The ASCII NUL character is allowed, although care should be
taken when passing strings containing it to other functions. taken when passing strings containing it to other functions.
wxString works with both ASCII (8 bit characters) as well as UNICODE (16 but wxString works with both ASCII (traditional, 7 or 8 bit, characters) as well as
characters) strings. Unicode (wide characters) strings.
This class has all the standard operations you can expect to find in a string class: This class has all the standard operations you can expect to find in a string class:
dynamic memory management (string extends to accommodate new characters), dynamic memory management (string extends to accommodate new characters),
@@ -48,9 +48,10 @@ very useful but don't exist in most of other string classes: for example,
\helpref{BeforeLast}{wxstringbeforelast}, \helpref{operator<<}{wxstringoperatorout} \helpref{BeforeLast}{wxstringbeforelast}, \helpref{operator<<}{wxstringoperatorout}
or \helpref{Printf}{wxstringprintf}. Of course, all the standard string or \helpref{Printf}{wxstringprintf}. Of course, all the standard string
operations are supported as well. operations are supported as well.
\item {\bf UNICODE} In this release, wxString only supports {\it construction} from \item {\bf Unicode} wxString is Unicode friendly: it allows to easily convert
a UNICODE string, but in the next one it will be capable of also storing its to and from ANSI and Unicode strings in any build mode (see the
internal data in either ASCII or UNICODE format. \helpref{Unicode overview}{unicode} for more details) and maps to either
{\tt string} or {\tt wstring} transparently depending on the current mode.
\item {\bf Used by wxWindows} And, of course, this class is used everywhere \item {\bf Used by wxWindows} And, of course, this class is used everywhere
inside wxWindows so there is no performance loss which would result from inside wxWindows so there is no performance loss which would result from
conversions of objects of any other string class (including std::string) to conversions of objects of any other string class (including std::string) to