[C++-sig] Re: Some patches to make the "Automatic PyUnicode to 'const char*'" possible, and make __stdcall function bindable

[Lijun Qin]

Hi,

On Windows platform, normally it'll be MBCS, not utf-8, I do not want to
change the default encoding to 'mbcs' because I'm afriad this 'program
global' action could cause confliction with other python extenstion.

Lijun Qin
http://www.solidshare.com

----- Original Message ----- 
From: "David Abrahams" <dave at boost-consulting.com>
To: <c++-sig at python.org>
Cc: <qinlj at solidshare.com>
Sent: Friday, September 12, 2003 10:58 PM
Subject: [C++-sig] Re: Some patches to make the "Automatic PyUnicode to
'const char*'" possible, and make __stdcall function bindable


> "Lijun Qin" <qinlj at solidshare.com> writes:
>
> > Hi,
> >
> > I have some patches to make the "Automatic PyUnicode to 'const char*'"
> > possible (please see
> > http://mail.python.org/pipermail/c++-sig/2003-August/004997.html for
> > details)
>
>
> Hi Lijun,
>
> After having done some research into PyUnicode, I see that it
> contains an internal buffer for the default decoding of its string.
> If you can set the default decoding to utf8 (that's what you're
> using, right?) you may find there's an easier solution to your
> problem.
>
> -- 
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com
>
>
> _______________________________________________
> C++-sig mailing list
> C++-sig at python.org
> http://mail.python.org/mailman/listinfo/c++-sig
>