Lines Matching refs:and
23 using at least 16 (and possibly 32) bits for encoding each character. This
25 multilingual plane) and possible $2^{32}$ of them instead of the usual 256 and
32 incompatible encodings for the same language, locale chaos and so on), many
36 Writing internationalized programs is much easier with Unicode and, as the
37 support for it improves, it should become more and more so. Moreover, in the
43 \subsection{Unicode and ANSI modes}\label{unicodeandansi}
58 and {\tt \_\_TIME\_\_})
66 Also, the string and character constants should be encoded using wide
69 (and C++) way: just put the letter {\tt 'L'} after any string constant and it
85 and {\tt \_\_TTIME\_\_} which behave exactly as the standard ones except that
86 they produce ANSI strings in ANSI build and Unicode ones in the Unicode build.
89 in both ANSI and Unicode modes could look like:
123 at all. Instead, we define some types and macros which behave differently in
124 the Unicode and ANSI builds and allow us to avoid using conditional
136 mode and prefixes {\tt 'L'} to its argument in the Unicode mode.
139 {\tt char}, avoid using C style strings and use {\tt wxString} instead and
155 \subsection{Unicode and the outside world}\label{unicodeoutsidewxw}
158 and macros, but it has been also mentioned that it isn't quite enough.
162 Unicode or ANSI strings and which thus makes it unnecessary to ever perform
184 For more information about converters and Unicode see
192 Unicode mode. This currently works for wxMSW, wxGTK, wxMac and wxX11. If you
196 This will allow your program to perform conversions between Unicode strings and
198 and construct wxString objects from Unicode strings (presumably read