# Re: Q about the FasterCSV

**URL:** <https://www.ruby-forum.com/t/re-q-about-the-fastercsv/94302>\
**Category:** Ruby\
**Created:** [April 28, 2006, 6:36am UTC](https://www.ruby-forum.com/t/re-q-about-the-fastercsv/94302 "2006-04-28T06:36:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PeSSSSaS\_Botp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/ecd19e/32.png) [@PeSSSSaS\_Botp](https://www.ruby-forum.com/u/PeSSSSaS_Botp)\
**Post date:** [April 28, 2006, 6:36am UTC](https://www.ruby-forum.com/t/re-q-about-the-fastercsv/94302/1 "2006-04-28T06:36:56Z")

</div>

James Edward G. II [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] :

# What’s the correct way to handle:

# 

# one, “two”

# 

# ? Is the second field two or “two” or “two”. I have no

imho, the latter. computer just reads what is in between. no bias. no  
loss of any data. (though “correct” may not be a good term here since  
the input is not defined for strictly normal csvs)

btw, we also have semicolon and tab separated values here. same behavior  
except it’s just semicolons or tabs that delimits. It would be nice if  
fastercsv can handle varying delimiters as well. just a thought. maybe,  
we can name it faster-delimiter 🙂

# idea. I do know that it is invalid CSV though. 😉

you’ve been really been helpful. thank you for your time.

kind regards -botp

---

<div class="post-metadata">

**Author:** ![PeSSSSaS\_Botp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/ecd19e/32.png) [@PeSSSSaS\_Botp](https://www.ruby-forum.com/u/PeSSSSaS_Botp)\
**Post date:** [April 28, 2006, 7:25am UTC](https://www.ruby-forum.com/t/re-q-about-the-fastercsv/94302/2 "2006-04-28T07:25:14Z")

</div>

On 4/28/06, Peña, Botp [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> btw, we also have semicolon and tab separated values here. same behavior except it’s just semicolons or tabs that delimits. It would be nice if fastercsv can handle varying delimiters as well. just a thought. maybe, we can name it faster-delimiter 🙂

I think both CSV and FasterCSV can do this. Same rules apply though,  
just different delimiters.

In FasterCSV, it looks like this:

irb(main):007:0\> FasterCSV.parse(“a\tb\tc\n”, :col\_sep =\> “\t”)  
=\> [[“a”, “b”, “c”]]

In CSV, this:

irb(main):010:0\> CSV.parse(“a\tb\tc”, “\t”)  
=\> [[“a”, “b”, “c”]]