Re: Mac Problems...

2001-05-21 Thread James Berry
Eric, This seems to indicate that neither the Unicode Converter, nor an appropriate Text Encoding Converter, are installed on the machine you're working on. Xerces/mac will not work without a properly installed Mac Unicode converter. There is a bug associated with this...the Mac code ought to pr

Re: Mac Problems...

2001-05-21 Thread Eric Deines
Hi James, I replaced the call to UpgradeScriptInfoToTextEncoding with the code you supplied. When I stepped through it, the if statement failed, so it when to DebugStr(...) with no problem, but then I got the "Illegal instruction exception" at the function call CreateTextToUnicodeInfoByEncodi

Re: Mac Problems...

2001-05-18 Thread James Berry
Title: Re: Mac Problems... Eric, Please try replacing the call to UpgradeScriptInfoToTextEncoding with the following code, and let me know if it helps:    if (UpgradeScriptInfoToTextEncoding != 0) { status = UpgradeScriptInfoToTextEncoding( smSystemScript

Re: Mac Problems...

2001-05-18 Thread Eric Deines
Hi James, It looks like it crashes at UpgradeScriptInfoToTextEncoding. When I step through makeNewLCPTranscoder(), the first line it allows me to stop at is the first "if(status == noErr)", and it crashes before I can even get there. I've tried getting it to be NULL if nothing was found like

Re: Mac Problems...

2001-05-17 Thread James Berry
On 5/16/01 1:22 PM, "Eric Deines" <[EMAIL PROTECTED]> wrote: > First of all, I see there are two different types of builds, Classic and > Carbon. What is the difference between each? (Yes, I am a Windows > programmer new to Mac, no laughing) Erik, I see that I answered your question about

Re: Mac Problems...

2001-05-17 Thread James Berry
Hi Eric, Presumably there's an error coming up during the call MacOSUnicodeConverter::makeNewLCPTranscoder(). I'd step through this in the debugger to see what occurs. I suspect that the problem is that there's no unicode converter installed on your 8.6 system (my recollection is that the unico