I'm putting this here in hopes to stop someone else pulling their hair out like I did (and I'm already bald).

I had been trying to import node data from a tab-delimited CSV file - I was getting either everything importing into a single node (and staying blank) or all nodes were "imported" but all info fields were blank.

Stupid thought process/workflow on this end: I would bring the info into Excel for clean up, and when saving it to a CSV/Tab delimited format, the only encoding option is Unicode... and that's not UTF-8 (I thought it was part of the same encoding family). If you're doing this, one must add an extra step of opening the CSV in Notepad (or other plain text editor) and make sure to save it with UTF encoding.

I know that this is not necessarily a workflow that most people may use, but perhaps there are others who have confused Unicode encoding as also being UTF encoding.

Comments

seattlehimay’s picture

seattlehimay commented

Thank you :) I love simple solutions.

alexmc’s picture

alexmc commented

On unix you might be able to use the iconv program to do something similar which doesn't require using Notepad :-)

rsgracey’s picture

rsgracey commented

I've been using Notepad++ for the UTF-8 conversion. Hateful microsoft....!

razkovnik’s picture

razkovnik commented

Thanks, from me too!

megachriz’s picture

megachriz
Primary language Dutch
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Feeds now has an option to set the encoding on a CSV import: #1428272: Added support of encoding conversions to the CSV Parser. This makes this issue obsolete, I think. Feel free to reopen if you think otherwise.