Re: [Pharo-users] NeoNumberParser and localization

> On 05 Jul 2016, at 16:40, Peter Uhnák wrote: > > I know that only NeoCSV uses it — that's how I ran into this problem. I was > processing some (czech) CSV files which used the decimal comma separator… > however the numbers were silently truncated, which wasn't nice to say

Re: [Pharo-users] NeoNumberParser and localization

I know that only NeoCSV uses it — that's how I ran into this problem. I was processing some (czech) CSV files which used the decimal comma separator… however the numbers were silently truncated, which wasn't nice to say the least — I really don't understand why the default behavior is to silently

Re: [Pharo-users] NeoNumberParser and localization

Peter, NeoNumberParser is a simple number (integer/float) parser that is part of NeoCSV (it was based on the JSON number parsing code). It was added because I wanted a number parser that makes little demands on the stream it parses from (just 1 character peek ahead, no arbitrary backtracking,

[Pharo-users] NeoNumberParser and localization

Hi, is there any plan for NeoNumberParser do add localization support? e.g. NeoNumberParser new thousandsSeparator: $,; "common in us data" parse: '12,230' => 12230 NeoNumberParser new decimalSeparator: $,; "common in eu data" parse: '12,230' => 12.230 Thanks, Peter