View Single Post
Old 11-27-2014, 03:55 PM   #65
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,820
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Just an observation. The Import List PI has no problems reading the CSV's I save from Excel - as stated in its intro post

Quote:
Import from CSV File - many users have lists of books stored in applications like Excel which can export to CSV, or use websites like Goodreads/Library Thing which also have export to CSV capability.
I use the Import List frequently with CSV's I save from Excel. From that I conclude the UTF-8 requirement is not imposed by the calibre infrastructure.

Rather than installing 200+MB of Open Office, you could try using libiconv - GNU Project(FSF) to convert the CSV saved from Excel to UTF-8 encoding

Or in Excel you could save the table as Unicode Text, open it in Notepad, and in Save As change the encoding to UTF-8. If the Define Genre's PI does not allow you to set the delimiter to Tab, you'll have to replace Tabs with commas. IMO anything that reads a CSV should allow the user to define the delimiter - as the data may contain commas.

BR
BetterRed is offline