News for hackers. Stuff that matters.

A comment on Mistaken Identifiers: Gene name errors introduced inadvertently using Excel.

Re:Mistaken Identifiers: Gene name errors introduced inadver... by mjn on Sunday April 21, 2013 @10:14AM (#5584877)
If you're importing from a CSV, there's a workaround that, unlike the Microsoft recommendation linked in this article, doesn't require adding a spurious apostrophe to the front of your data: http://stackoverflow.com/questions/165042/stop-excel-from-au...
[ Parent | on HN ]
Re:Mistaken Identifiers: Gene name errors introduced inadver... by lutusp on Sunday April 21, 2013 @01:18PM (#5585491)
You might have included the workaround that actually works from the linked conversation's many suggestions that don't work -- add a space in front of each field of the original CSV data that you don't want converted. This is more effective and reliable if each CSV data field is quoted, and the space is inside the quotes.
[ Parent | on HN ]