Hugh Perkins wrote:
> utf-8 sounds good
I'd say that we just use only utf-8, basically, and have conversions
from whatever wchar_t*/wstring are (are they 16 bit or 32 bit
characters? depends on the platform?) built into the property and
talkative apis (the conversion functions would be in vutil of
utf-8 sounds good fwiw. for swig, you can define your own
functions quite eqsily to handle how conversions take place, so you can
probably just define your own conversion function for strings? You only
have to write the conversion function once, and they're generally quite
short.
On the other han
On Fri, Sep 09, 2005 at 10:16:28AM -0400, Reed Hedges wrote:
> Then property just needs wstring methods I guess.
with conversion into utf8 to store in the std::string.
___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/m
Hey guess what, we need to deal with Unicode strings in Python too! Unicode
strings are a different type than normal strings. Swig easily maps 'some
string'
to char* or std::string, but doesn't seem to want to map u'some string'. You
have to convert it with string.encode("ascii") or somethin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hmm, well I'll have to try it again, then. I don't remember what the
specific problem was, although I seem to recall at the time (this being
over a year ago) Jorrit warning me away from Unicode and CS on Win32.
On Tue, 6 Sep 2005, res wrote:
On
On 06.09.2005 05:41, Peter Amstutz wrote:
> I tried compiling in unicode on Windows once, and it failed miserably
> because Crystal Space can't (or couldn't) handle the
> Unicode/wide-character versions of the win32 API.
Not sure what you mean CS itself interacts with Win32 only at very
few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've spent this weekend moving into my new apartment, and I don't have
internet for my desktop yet (on my laptop I'm "borrowing" the upstairs
neighbor's wireless for the time being). However, when I get a chance I
will set up ter'angreal to compil
On 05.09.2005 03:44, Reed Hedges wrote:
> I made a few changes along those lines and got wxterangreal to build but
> now it crashes in CS, as does wxtest, in csDriverDBReader.
A backtrace may be helpful.
-f.r.
signature.asc
Description: OpenPGP digital signature
___
I guess wxgtk 2.6 in Debian is built in Unicode mode, and while I
noticed some random bits and pieces of TerAngreal with stuff in #ifdef
wxUSE_UNICODE conditionals, and some wxStrings are converted with
wxString::mb_str(), it's generally incomplete.
If build in Unicode mode, wxChar is a wchar_t,
