Ok, thanks to those who addressed my previous questions. I have one more question, this time on the windows side.
Our windows work was done on Windows 2000, and everything worked well. But we received reports from testers that it was not working on Windows 98. In digging through it, I see that the problem lies in Win32LCPTranscoder::transcode(XMLCh *). This code calls wcstombs() once to determine the length of the transcoded string, and again to perform the transcoding. The first call, on our windows 98 environment, returns 0. Consequently, an empty string is returned. I can't fathom why this is failing. I looked at msdn and couldn't find any valid explanation. The toTranscode XMLCh string is valid (I can view it in the debugger as a "unicode string" and it looks correct, and again it works well on win2k). Has anyone run in to this before? Thanks, Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
