Hi,

when given an input file containing non-latin characters (like German umlauts or French accents), the "special character" and everything following is concatenated.

Examples: "König" becomes "K"; "Maria Pütz" becomes "Maria P", "Marita Bäuerlein" becomes "Marita B", "Renate Schäfer" becomes "Renate Sch", etc.

That applies as well for imports into the node title field as for imports into the node's body.

Also, "Node import" seems not to support node references, neither given a string nor a node ID (just a qucik observeration, I'll have to verify this and will file another issue if applicable).

Thanks & greetings, -asb

Comments

dergachev’s picture

dergachev commented

Check that your encoding is actually unicode! I exported a french CSV from Excel 2007, and had the same problem as you.
To fix it, I opened the file in Textpad (a nice little Windows text editor), and re-saved it, making sure to tell TextPad to use UTF-8 encoding.
This fixed the problem.

asb’s picture

asb commented

> Check that your encoding is actually unicode!

Yes, the texts encoding is definitely "Unicode" (UTF-8).

Greetings, -asb

giorgio79’s picture

giorgio79 commented

Thanks for this, I experienced the same issue, and changing the encoding of my csv file to UTF8 helped me greatly.

Cheers,
G

dergachev’s picture

dergachev commented

:) pleasure to have helped

wflorian’s picture

wflorian commented

Does anybody know a programm, wich can export csv files with UTF8 encoding? microsoft excel does not work...

Solved with OpenOffice!

Robrecht Jacques’s picture

Robrecht Jacques commented
Status: Active » Fixed

You *must* have a UTF8 encoded file if you use these accents.

Is this still an issue in node_import-5.x-1.7 ? There were some problems with CSV files that have been fixed.
Setting it as fixed. If it is not, reopen the issue and attach a sample CSV file that fails.

And indeed, Excel does not seem to save to CSV files correctly.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.