Re: Bug #722 Updated: setlocale: scanner (scanf?) / printf don't work properly

From: Date: Mon, 15 Nov 1999 09:18:14 +0000
Subject: Re: Bug #722 Updated: setlocale: scanner (scanf?) / printf don't work properly
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-12557@lists.php.net to get a copy of this message
Yes it's in 4.0B2. The output functions echo and print are correctly affected by the locale setting, printf's output is not. The parsing of $v = 3.4; is wrong under a locale setting with dec. sep. = ",". It yields $v = 3 I could not check if PHP's setlocale is propagated back to the apache server as it was in 3.x. That can nicely be seen in the logfile , where months' names are translated into the locale's months' names. Currently we have "Nov" in both German and English. BTW The Perl-Interpreter has the same kind of problems. I think every language should have its own locale processing. Stefan Vogtner Bug Database wrote: > > ID: 722 > Updated by: joey > Reported By: vogtner@soldan.de > Status: Assigned > Bug Type: Misbehaving function > Assigned To: jaakko > Comments: > > 3.0.3?!? Wow! That's when I first started using PHP! Can anyone verify whether this is > still there? > > (I'm not using locales...) > > Full Bug description available at: http://bugs.php.net/?id=722

« previous php.dev (#12557) next »