From: Eric Luo <eric.wenbl@...>
Date: 2006-04-27T17:01:37+09:00
Subject: Re: Q about the FasterCSV

------=_Part_25126_32267844.1146124894795
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I agree!

I'm really missing this feature for my current work!

On 4/27/06, Pe=F1a, Botp <botp@delmonte-phil.com> wrote:
>
> Dave Burt [mailto:dave@burt.id.au] :
>
> # No, it's not a bug. CSV is a simple delimited format. It's
> # delimited by
> # a comma character, not a comma then some arbitrary whitespace. That's
> # how Microsoft's Excel and Access and SQL Server parsers deal
> # with it, too.
>
> Dave, you're a cool rubyist. I think you are cooler than microsoft's.
>
> and mabye, fastercsv can be more "intelligent" than other csv by
>
> 1) ignoring extra spaces in a captured separated value
>
>   eg,
>
>   test, "1" =3D=3D> ["test","1"]
>
>   iow, quotes rule (as in shellwords)
>
> 2) not ignore spaces yet escape the quotes
>
>   eg,
>
>   test, "1" =3D=3D> ["test"," \"1\""]
>   test, "1"111 =3D=3D> ["test"," \"1\"111"]
>
> 3) or maybe, fastercsv can include an option/flag to allow the above
>
>
> Also, it would be nice if fastercsv could show what particular field it
> balked
>
> kind regards -botp
>
>
>
>
>

------=_Part_25126_32267844.1146124894795--