[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSString-stringWithCString: can't handle umlaute

From: Martin Kuball
Subject: Re: NSString-stringWithCString: can't handle umlaute
Date: Tue, 27 Apr 2004 19:35:45 +0200
User-agent: KMail/1.6.2

Thanks for the answer.

OK, here is some info about my system. I'm running debian Linux 
unstable (i386 architecture). My locales are set to de_DE.UTF-8.
I'm using gdb 6.1. What I did was to set a breakpoint on the line
        NSString *test = [NSString stringWithCString: cstr];
Once there I typed s and return. Then gdb took a deep breath and 
eventually answered with:
        0x40155530 in GSScanDouble ()
        from /usr/lib/GNUstep/System/Library/Libraries/

OK, stupid me. After installing the debug version of the foundation 
lib debugging goes much better. Point is gnustep is right and I'm not 
using utf8 encoding despite my locale says so. F*g kde editor! I 
guess I still have some way to go to make my system utf-8 clean.


Am Tuesday 27 April 2004 13:52 schrieb Richard Frith-Macdonald:
> On 26 Apr 2004, at 20:45, Martin Kuball wrote:
> > Hi!
> >
> > the following code
> >
> >     const char* cstr = "zurück";
> >     NSString *test = [NSString stringWithCString: cstr];
> >
> > results in test = nil with gnustep-base 1.9.9. Note that there is
> > no other hint that something went wrong. The character 'ü' has
> > the numeric value 252.
> What character set is your system set up to use?  Most likely
> problem is that it is
> one where 252 is not a legal character.  The proper behavior of an
> initialiser
> which fails is to return nil.
> > Using gdb when trying to step into the method call I end up in a
> > function GSScanDouble. I will try to investigate further but any
> > help is welcome.
> I can't see how you could get to GSScanDouble within
> stringWithCString: Did you try setting a breakpoint in the method
> instead?
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]