Lori,
your wrote on your blog ---- It is confusing why the default column termination symbol for CSV is a semi-colon when a comma is expected ("comma-separated values"). ----
I agree it's confusing but the semi-colon is there by default for a reason: this is the character that Excel expects and we can't deny that most users will use Excel to read back this file.
Hi
Dne Fri, 09 Jul 2010 08:06:06 -0400 Marc Delisle marc@infomarc.info napsal(a):
Lori,
your wrote on your blog
It is confusing why the default column termination symbol for CSV is a semi-colon when a comma is expected ("comma-separated values").
I agree it's confusing but the semi-colon is there by default for a reason: this is the character that Excel expects and we can't deny that most users will use Excel to read back this file.
I though this is reason for having CSV and CSV for Excel. So having CSV by default separated by comma would make sense.
Michal Čihař a écrit :
Hi
Dne Fri, 09 Jul 2010 08:06:06 -0400 Marc Delisle marc@infomarc.info napsal(a):
Lori,
your wrote on your blog
It is confusing why the default column termination symbol for CSV is a semi-colon when a comma is expected ("comma-separated values").
I agree it's confusing but the semi-colon is there by default for a reason: this is the character that Excel expects and we can't deny that most users will use Excel to read back this file.
I though this is reason for having CSV and CSV for Excel. So having CSV by default separated by comma would make sense.
I was using just "CSV" with the default of semi-colon to read back into Excel because I had a doubt with "CSV for MS Excel".
I just tried with "CSV for MS Excel": it generates a file with commas without giving a choice of changing this, and most importantly *it does not work* with MS Excel 2007 on Windows! Not sure about the one on Mac, however
I'm going to have a look and fix this for 3.3.5, at least for Windows. After this fix, yes it would make sense that CSV produce commas :)
Great! I'm glad we could find a solution.
On Mon, Jul 12, 2010 at 4:49 AM, Marc Delisle marc@infomarc.info wrote:
Michal Čihař a écrit :
Hi
Dne Fri, 09 Jul 2010 08:06:06 -0400 Marc Delisle marc@infomarc.info napsal(a):
Lori,
your wrote on your blog
It is confusing why the default column termination symbol for CSV is a semi-colon when a comma is expected ("comma-separated values").
I agree it's confusing but the semi-colon is there by default for a reason: this is the character that Excel expects and we can't deny that most users will use Excel to read back this file.
I though this is reason for having CSV and CSV for Excel. So having CSV by default separated by comma would make sense.
I was using just "CSV" with the default of semi-colon to read back into Excel because I had a doubt with "CSV for MS Excel".
I just tried with "CSV for MS Excel": it generates a file with commas without giving a choice of changing this, and most importantly *it does not work* with MS Excel 2007 on Windows! Not sure about the one on Mac, however
I'm going to have a look and fix this for 3.3.5, at least for Windows. After this fix, yes it would make sense that CSV produce commas :)
-- Marc Delisle http://infomarc.info
This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-
Lori Lee -
Marc Delisle -
Michal Čihař