Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error reading input file #2

Open
schoettl opened this issue Sep 27, 2019 · 4 comments
Open

Error reading input file #2

schoettl opened this issue Sep 27, 2019 · 4 comments

Comments

@schoettl
Copy link

When I open a csv file (comma- or semicolon-separated, UTF-8 or ASCII), I only get the error "error in reading input file". No useful debug messages are printed on the terminal.

Also, the command line version does not work as it should:

python3 -m csv2vcf file.csv

shows the UI in the same way as without the filename. It would be better if it just converts file.csv to file.vcf.

@sepandhaghighi
Copy link
Contributor

@schoettl Hi
Thanks for your comment ;-)
Would you please give us more information about your .csv file?

@schoettl
Copy link
Author

Hi, this is my csv file:

name,home,work,mobile,combined
Essen,,08000 1234560,,08000 1234560

I noticed that the error does not appear when I omit the header line.

However, without the header line, it shows "0 VCF File Generated In 00 days, 00 hour, ..." and the target folder is empty.

Also, after both message dialogs, the program cannot be closed and crashes after I press ctrl-c and switch window. I cannot close a window because the window disappears when I click "OK" in the dialog.

You should really consider implementing my suggestions because there seem to be no competing command line conversion tools except csv2vcf which is python2 and cannot handle different phone number types. But the field assignments are easily configurable.

@schoettl
Copy link
Author

Right! I forgot to use your specified input format. I used to have it but then I had to change the format to use the other converter tool.

@sepandhaghighi
Copy link
Contributor

@schoettl Thanks again for your comments and suggestions ;-)
We didn't update this tool for about 2 year, but now I have a plan to release a new version in next few months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants