Ok, I looked at the code. It actually creates a string object that encapsulates both std::wstring (UCS2) and std::string (UTF8). We don't use the transcode functions -- too many problems some years ago (Xalan 1.0?). All of our wide character data is UCS2, and char is UTF8. There are Microsoft APIs that do that conversion, or you can pretty easily write your own (what I did).
Keith Rogers <[EMAIL PROTECTED]> wrote:
Keith Rogers <[EMAIL PROTECTED]> wrote:
I've got a fair amount of code that uses the XalanDOMString::c_str() to create std::string objects,...
