Re: locales support in sscanf. Bug 35364

[Pascal Dupuis]

2012/12/19 Andreas Weber <address@hidden>:

> I live also in germany and I know the problems with decimal separators
> but when I have to convert CSV Data I write a little awk, sed or tr
> script for this purpose.
>
> I really don't want to complicate things in octave and until now there
> is only locale support in sscanf. And I don't think anyone want to make
> all string to number and vice versa using the locales.
>
> So please consider to remove the changeset which introduced locales.
>

I have to disagree with you. I work in France, all main software are
in French. I produce dozens of data file each day, and I absolutelly
need to import directly those CSV file in Octave. The processing is
recursive, I try to process files only once, so I have to check is,
for a given name, some other name with some extension exist. In
Octave, this is solved in a ten of lines. Moreover, there are
sometimes number inside strings separator which must not be converted.
So 'a little awk, sed or tr script' is too simplistic to cope with
generic data files.

The last version I did produce had provisions to entirelly disable
locales support during the "configure" phase. Let solve the annoying
behaviour, but I need locales support in sscanf.

Regards

Pascal