CSV rendering bug in GitHub Web App

[I’d raise a bug but this seems to be the option I have, hope is correct tag for the Web App]

I have a CSV file that uses ; as is common in EU countries that use , as the currency separator. As far as I understand the CSV ‘specification’ that allows , to be used in cells.

However that seems to be breaking the GitHub pretty rendering of the CSV.

We can make this file beautiful and searchable if this error is corrected: It looks like row 56 should actually have 1 column, instead of 2. in line 55. 

For these lines

54;arms;kädet;Terveys kehonosat
55;armwrestle_,_to;kädenvääntö;Vapaa-aika pelit

Is this a CSV parsing bug.? A result of not having a real CSV standard? A localisation assumption bug? Or something else?

Can I work around it?
A hack is probably to convert the CSV to , separated and quoting strings with ,s but would rather keep as supplied to me by a contributor.



1 Like

This is the only solution.

The reason why only that line is showing error is because it have ,
If none of your data had , then you will see the correct error message:

We can make this file beautiful and searchable if this error is corrected: No commas found in this CSV file in line 0.

1 Like

Shame as ; is a valid separator in many places CSV get used.

But again, there’s no real CSV standard so we can’t complain. Sign.

I already filed a Feature Request in 2019 for this issue…
[Feature Request] Support semicolons in CSV rendering for display

1 Like

I don’t see anything wrong in only accepting , as delimiter as name says Comma Separated Values.